You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the plugin is activated, Tab switches between the two drop-down menus that choose the source and target keymaps. But Tab is a potential short-cut key too! I think it is more important to make Tab something that you can translate instead of something that navigates between plugin GUI elements. Thoughts/comments?
/mark
The text was updated successfully, but these errors were encountered:
This is probably because ShortcutTranslatorDialog extends DialogWrapper (from Intellij platform). It inherits the default intellij dialog behaviour. If I remember correctly, it was the easiest way to provide the plugin with consistent IntelliJ L&F (centering the dialog, giving it the correct size, registering default event handlers).
I'm guessing that Tab is not used a lot as a hotkey other than cycling through tabs & other UI elements, or indenting in the editor. This in combination with the fact that the intellij keymaps for competing editors are not complete anyway, makes the effort too big (for me) to change the way ShortcutTranslatorDialog is created without losing other Intellij behaviour.
When the plugin is activated, Tab switches between the two drop-down menus that choose the source and target keymaps. But Tab is a potential short-cut key too! I think it is more important to make Tab something that you can translate instead of something that navigates between plugin GUI elements. Thoughts/comments?
/mark
The text was updated successfully, but these errors were encountered: