Common Keybindings Menu #897
DarkLiKally
started this conversation in
Blish HUD Core Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
It would be really useful to have a centralized Keybindings menu item in the main blish hud window, where all modules can register their hotkeys.
This would make it easier to manage hotkeys and to detect conflicts, we could highlight double assignments and the user has to check if that's correct. Also it can offer a easy place to quickly enable / disable keybindings at users will without searching through different menus of modules. For example now modules use different approaches to create settings menus (own window, module page, window that opens from module page, tab in main window, ...) If you need to quickly find and disable a keybinding because it interferes with your controls while doing content, it might be annoying to search for it, leading to just disabling the module.
Also we could provide in-game-keybinds section (or just special marked keybinds) that relate to the ingame key bindings, like the skills or dodge and so on. This way those default keys could be consumed by many modules but the user only has to configure these ones one time.
Modules could still offer changing keybinds in their own UI if required or better for usability, but those should also be linked to a registered keybinding so that it also appears in the global list.
Creating keybindings should also be possible at runtime and not just setup time, to also support modules that need to assign hotkeys to dynamically created objects inside the module (like chat message shortcuts or emote modules).
Support older module versions created before this possible feature:
Idea 1: The keybindings would have to receive a name and a description maybe, those should be generated somehow at registering modules, and just number them maybe in order they're created, like "Module A Keybinding 1" and show them this way in the global menu.
Idea 2: When a keybind has not received a name by the developer, consider it legacy and not include it in the global keybindings panel. Or maybe show it in a legacy section somehow.
Beta Was this translation helpful? Give feedback.
All reactions