Skip to content

Make nested context menus optional for each category of options #106

@Thomas-D-C

Description

@Thomas-D-C

Background

I usually need only case changing options and nothing else.
So I don't use nested context menus, as this would only increase the time required to access them.

I sometimes need code case changing options, but very rarely.
So I check them in settings, then uncheck them once I'm finished, because otherwise it would create a menu that's too long with too many useless items. (But it's a bit tedious.)

Proposed solution

IMHO, the best solution for me would be to have a nested context menu for code case changing options, but to keep case changing options at the first level.

Additional context

Do you think there is a way to do that?

Sure, we could allow the user to set a nested context menu for each category of options. This could work good in combination with #30.

Originally posted by @tdulcet in #44

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions