Thomas Adam <tho...@fvwm.org> writes: > On Sun, Jun 30, 2013 at 05:42:51PM +0100, Dominik Vogt wrote: >> Recently I find it annoying that hotkeys in menus can only be >> simple characters because of the menu item syntax, e.g. >> >> + &FvwmConsole ToggleFvwmConsole >> ^^^ >> >> I'd like to extend the hotkey logic so that it also works with >> moulti character key names like "f1" and possibly sequences like >> "ctrl-shift-space". The code to allow this whoould be mostly >> there already, so the question of syntax remains. >> >> One option would be to somehow extend the existing syntax to allow >> longer key sequences, e.g. >> >> + FvwmConsole &(f1) ... >> >> (resulting in "FvwmConsole _f1_"), which might break existing >> menus. ANother option might be to add a separate hotkey menu >> command, e.g. >> >> + FvwmConsole (f1) ... >> AddMenuItemHotKey f1 >> >> The hotkey would be merged into the previously defined menu item. >> I cannot say that either option looks good to me. Can anybody >> think of a cleaner or more natural way to define hotkeys, possibly >> recuycling the syntax of the "Key" command? > > Another idea might be to simply allow keys when a menu is open to act like > a typeahead search; the more keys you press, the closer to match you get, > and at each stage, matched items are highlighted in the menu, etc.
Aggh. no! Actually lots of my menus are heavily short-cutted. I'd don't think I'd get very far in a search term before one the options would be selected. Even a menu without short cuts accepts vi-keys for cursor movement. -- Dan Espen
