HotkeyManager that I originally implemented used (and still uses) an AWTEventListener to follow various key events and trigger registered actions. This way has some major flaws and doesn't work too well with the existing Swing implementation of hotkey handling through component input map and action map.
I'm planning to change HotkeyManager to work with the standard component input and action maps, but make it less painful for the actual user than the original way.
Some of the issues that might also be resolved once implemented:
Rework for HotkeyData to be KeyStorke decorator
Show hotkey label without actual registration in HotkeyManager [ #177 ]
Keyboard shortcuts (mnemonics) of a button not visible in tooltip [ #167 ]
File Chooser: keyboard navigation [ #163 ]
I will post more details on the rework once I get to implement it.
mgarin
commented
4 years ago
HotkeyManagerthat I originally implemented used (and still uses) anAWTEventListenerto follow various key events and trigger registered actions. This way has some major flaws and doesn't work too well with the existing Swing implementation of hotkey handling through component input map and action map.I'm planning to change
HotkeyManagerto work with the standard component input and action maps, but make it less painful for the actual user than the original way.Some of the issues that might also be resolved once implemented:
HotkeyDatato beKeyStorkedecoratorI will post more details on the rework once I get to implement it.