Keyboard Shortcuts for new top-level menu items

[craigo-]

Notepad3 (64-bit) v5.19.316.1659 XpErImEnTaL

I noticed that the new menu items Language and Themes do not have keyboard shortcuts. Is there a reason for this? If not, might I suggest Alt+L and Alt+T respectively?

[RaiKoHoff]

Unfortunately, both "Hotkeys" are in use:

• Alt+L : File -> Launch -> Open with...
• Alt-T : toggles Settings -> Window -> Always On Top
  🤔

[craigo-]

Hmmm. Tricky. On the one hand, I feel like the top-level menu items in any Windows application should have their respective keyboard shortcuts reserved. On the other, I know that Notepad3 has a past and current need for a lot of keyboard shortcuts (and I'm reluctant to mess with them too much, in case it annoys the user base)!

I toyed with the idea of using letters other than the first for the new top-level menus. You could use Alt+A for the "Language" menu, but there are no available options for the "Themes" menu (Alt+h, e, m, s are all in use).

How does the Notepad3 community feel about this?

Alt+L: Language menu
Alt+T: Themes menu
Ctrl+Alt+L: Open with...
Ctrl+Alt+Shift+T: Always On Top

Of course, this is all in the context of an experimental build. Should the Themes menu not go ahead, a simple solution would be to bind Alt+A to the "Language" menu and leave everything else alone.

[RaiKoHoff]

@craigo- : your suggestion is worth to think about - unfortunately, this question here is closely related to another question for @hpwamr :
What about other languages, which currently don't care about the "Alt+<Key>" Menu popup Accelerator-Key collisions.
So, for en-US and en-GB we can keep the combinations and think about @craigo-'s proposal,
for all other languages, we have to disable the "Alt+<Key>" for the menu items, which cause a collision 🤔

[hpwamr]

The rearranging the Language and Themes menus is done.

Feel free to test the RC2 version: "Notepad3Portable_5.19.601.1002_RC2" or higher.
See "Notepad3 beta-channel access #1129" or download it from here Notepad3Portable

As far as I am concerned, this issue may be closed.... 🤔