Is hiding stuff behind the "more" sub-context menu intentional?

Jürgen Spitzmüller jspitzm at gmail.com
Thu Nov 2 08:40:51 UTC 2023


Am Donnerstag, dem 02.11.2023 um 03:33 +0000 schrieb Isaac Oscar
Gariano:
> 
> 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.

We can't just remove functionality to keep the menus small. I also
think well-structured menu hierarchies are the way to go. But this is
definitely beyond 2.4.0, so let's postpone this discussion and rather
try to get 2.4.0 out of the door, at long last.

-- 
Jürgen


More information about the lyx-devel mailing list