It would be great if there was a way to customize hotkeys. Here's how I see it: * Have a about:hotkeys panel, with all actions listed, and already mapped shortcuts shown. * Whether these should be modifiable or not is up to the dev community, ideally they'd be. * When clicking on a hotkey field, ...
I’d go a step further and say that applications shouldn’t implement keyboard shortcuts at all. Ideally there’d be an integration with the OS where the application exposes the available commands and the default key binding.
That way the OS can provide consistent key bindings across all applications, so if you switch Ctrl+C to Meta+C, it just works, and opens up a lot of possibilities for weird accessibility setups, and also opens up room for changes to the keyboards.
It’s weird enough as it is if you use dvorak or more regional ones like bépo, and it’s not even a different physical keyboard it’s just a key layout. We have touchscreens and virtual keyboards, adding a Ctrl and Alt key to a virtual keyboard takes space and it’s kinda ridiculous when we could have a nice customization shortcuts ribbon so you have copy/paste and stuff handy. There’s also voice inputs.
Input needs to be decoupled from the concept of a keyboard. Steam Input is a good step towards that for games specifically, but it would be amazing as a general system so you can comfortably use Firefox from a game controller and whatnot.
The way you describe it is quite genius as it’d allow the OS to automatically remap shortcuts to stay on the same physical keys when the layout is something other than qwerty by simply mapping the keys twice.
I’d like to expand your idea with virtual shortcuts for common operations. Instead of declaring C to mean copy, the applications would assign the copy operation to the “common copy key” which would then be controlled by the OS.
It’d likely be C by default but the user would be able to change it in one common place for all applications.
What I meant is those virtual shortcuts are all you get, at all. The application declares the shortcuts with an optional suggested key binding for it, but it’s up to the OS to ultimately handle the keys and tell the application which shortcut is called for.
That’s exactly what Steam Input does: the game specifies actions like “player movement”, “jump”, “fire”, “look” and Steam just sends those values to the game. The game doesn’t have to implement mouse, keyboard or controller inputs at all, Steam does it all for you. In return, the game can run with controllers we’ll make 10 years from now, and the player can finally just map every single button to their liking, universally. It’s so much easier to deal with when thinking of “Ok, so A is jump” rather than “So I want to press A to jump which is X in the game”.
Applications shouldn’t have to care about how you input stuff, it’s ugly and complex, leave it to the operating environment to figure that out for you.
I was being unclear; I meant the optional suggested keybinding would be bound to virtual keys for common actions.
The goal of that is to rebind common actions globally. Without this, you’d have to change each application’s individual “copy” action to your preferred shortcut. You’d do so in the OS rather than the app but you’d still have to do it for each app individually.
Alternatively, there could be a set of pre-defined common actions that applications would simply use rather than defining their own action. I think that’s what you mean.
MacOS does this. Basically any action present on an app’s global menu can have a key bound to it in system settings.
Not every app exposes its menu to the system however.
Yeah, I’ve thought that in addition to regular keystrokes operating systems should provide logical events. If I press Ctrl+c don’t send Ctrl+c to the application, send Copy (Maybe also with the original keystroke in case it needs to be interpreted “raw” like when using remote desktop software). We sort of have this for keyboard, there are special keys like Mute and Web Browser, but I think we should extend this system for common actions that are basically universal.
I’d go a step further and say that applications shouldn’t implement keyboard shortcuts at all. Ideally there’d be an integration with the OS where the application exposes the available commands and the default key binding.
That way the OS can provide consistent key bindings across all applications, so if you switch Ctrl+C to Meta+C, it just works, and opens up a lot of possibilities for weird accessibility setups, and also opens up room for changes to the keyboards.
It’s weird enough as it is if you use dvorak or more regional ones like bépo, and it’s not even a different physical keyboard it’s just a key layout. We have touchscreens and virtual keyboards, adding a Ctrl and Alt key to a virtual keyboard takes space and it’s kinda ridiculous when we could have a nice customization shortcuts ribbon so you have copy/paste and stuff handy. There’s also voice inputs.
Input needs to be decoupled from the concept of a keyboard. Steam Input is a good step towards that for games specifically, but it would be amazing as a general system so you can comfortably use Firefox from a game controller and whatnot.
The way you describe it is quite genius as it’d allow the OS to automatically remap shortcuts to stay on the same physical keys when the layout is something other than qwerty by simply mapping the keys twice.
I’d like to expand your idea with virtual shortcuts for common operations. Instead of declaring
Cto mean copy, the applications would assign the copy operation to the “common copy key” which would then be controlled by the OS.It’d likely be
Cby default but the user would be able to change it in one common place for all applications.What I meant is those virtual shortcuts are all you get, at all. The application declares the shortcuts with an optional suggested key binding for it, but it’s up to the OS to ultimately handle the keys and tell the application which shortcut is called for.
That’s exactly what Steam Input does: the game specifies actions like “player movement”, “jump”, “fire”, “look” and Steam just sends those values to the game. The game doesn’t have to implement mouse, keyboard or controller inputs at all, Steam does it all for you. In return, the game can run with controllers we’ll make 10 years from now, and the player can finally just map every single button to their liking, universally. It’s so much easier to deal with when thinking of “Ok, so A is jump” rather than “So I want to press A to jump which is X in the game”.
Applications shouldn’t have to care about how you input stuff, it’s ugly and complex, leave it to the operating environment to figure that out for you.
I was being unclear; I meant the optional suggested keybinding would be bound to virtual keys for common actions.
The goal of that is to rebind common actions globally. Without this, you’d have to change each application’s individual “copy” action to your preferred shortcut. You’d do so in the OS rather than the app but you’d still have to do it for each app individually.
Alternatively, there could be a set of pre-defined common actions that applications would simply use rather than defining their own action. I think that’s what you mean.
MacOS does this. Basically any action present on an app’s global menu can have a key bound to it in system settings.
Not every app exposes its menu to the system however.
Yeah, I’ve thought that in addition to regular keystrokes operating systems should provide logical events. If I press
Ctrl+cdon’t sendCtrl+cto the application, sendCopy(Maybe also with the original keystroke in case it needs to be interpreted “raw” like when using remote desktop software). We sort of have this for keyboard, there are special keys likeMuteandWeb Browser, but I think we should extend this system for common actions that are basically universal.