- Messages
- 1,403
- Reactions
- 5,786
- Points
- 173
- Website
- github.com
- acidbubblesanon
- Patreon
- acidbubbles
I'm currently writing a pretty powerful plugin for advanced keyboard shortcuts, but I have a small issue that should be fairly easy to solve in VaM. There's a lot of keys that are "hardcoded" in VaM, and therefore there's no way for me to "overwrite" them. That means arrow keys, F1, Tab and the letters W, S, A, D, M, F, R, E, P, N, U, T ,H and C are unavailable for key bindings. That's quite a lot, and greatly reduces the interest of having custom shortcuts. Also, VaM ignores the LeftControl key during ProcessKeyBindings, which means I cannot make shortcuts for those even with Alt or Ctrl (e.g. CTRL+S works but also moves the camera backwards ?
)
As a quick workaround, could there be a bool in SuperController.singleton like enableKeyboardShortcuts that I could set to false? I could then proceed with re-creating those myself in my own shortcuts plugin.
The plugin would allow for advanced use cases like assigning shortcuts to actions for the currently selected atom's plugins, and having scene-specific shortcuts as well as global shortcuts.
A better option would be to have a setting for each key (kind of a built-in key binding in VaM) that I could disable per-shortcut, but just a single bool (that would behave like LookInputModule.singleton.inputFieldActive) would reduce the time investment for you.
Thank you for your consideration! ❤

As a quick workaround, could there be a bool in SuperController.singleton like enableKeyboardShortcuts that I could set to false? I could then proceed with re-creating those myself in my own shortcuts plugin.
The plugin would allow for advanced use cases like assigning shortcuts to actions for the currently selected atom's plugins, and having scene-specific shortcuts as well as global shortcuts.
A better option would be to have a setting for each key (kind of a built-in key binding in VaM) that I could disable per-shortcut, but just a single bool (that would behave like LookInputModule.singleton.inputFieldActive) would reduce the time investment for you.
Thank you for your consideration! ❤