I think the best approach would be to write the menu's such that they don't have too many options in the first place. Of course if a user defines an inset or something else with lots of options, that should be their problem. One problem however is spelling suggestions, since these are generated dynamically, perhaps they could be in a submenu labelled "Spelling suggestions" or something. As for combining context menus in the case of insets, I think a better approach would be to put the inset as a sub-menu of the main context menu (with a helpful label like "Inset Options" not a generic "More..."). Of course, this is more work than the current approach of automatically making a "More..." submenu, but I think considering each case separately would make LyX more user friendly. Personally, I haven't found any of the context menus to be particularly long in the first place, except the one for the menu bar (which lists every toolbar) or when there are lots of spelling suggestions. So only handling cases once someone's actually noticed the problem might be a good compromise between quality and developer time.
— Isaac Oscar Gariano ________________________________ From: lyx-devel <lyx-devel-boun...@lists.lyx.org> on behalf of Jürgen Spitzmüller <jspi...@gmail.com> Sent: Thursday, 2 November 2023 3:51 AM To: lyx-devel@lists.lyx.org <lyx-devel@lists.lyx.org> Subject: Re: Is hiding stuff behind the "more" sub-context menu intentional? Am Mittwoch, dem 01.11.2023 um 15:05 +0100 schrieb Jürgen Spitzmüller: > Am Mittwoch, dem 01.11.2023 um 12:50 +0100 schrieb Jürgen > Spitzmüller: > > Note, however, that this will result in shortcut conflicts with > > items > > moved from sub- to main menu, so this effectively causes string > > changes. Since string freeze that is lurking around the corner for > > some time now, I am not sure if this is good to go in. > > FYI these are the string changed involved. Haven't checked yet all > collapsibles, though, so I might have missed some. Actually given all the things that need to be considered to get this right, I propose to: * revert https://www.lyx.org/trac/changeset/6c4afc1ccb9030/lyxgit which will get back the context menu behavior of LyX 2.3 for 2.4 * Do everything else carefully in the next (2.5.x) cycle. -- Jürgen -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
-- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
