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
I have a keyboard with a non-US layout, and I would like to use some of the keys with non-english characters on it for custom keybinds. However, since I also often switch between US and native keyboard layout (Estonian), I would like to create these bindings in such a way that they map the specific key, rather than the character.
Currently this can be done for some keys, eg. RBracket and LBracket, which show up in the verbose log as key: Some(LBracket) , however, many keys show up as key: Some(Unknown) and as such I assume they cannot be used in keybinds.
Is there some way to map actions to these keys based on their keycode/scancode. If not, could this feature be added?
The text was updated successfully, but these errors were encountered:
FeldrinH
changed the title
Create bindings based on keycodes for non-US keyboards
Create keybinds based on keycodes for non-US keyboards
May 9, 2021
Hmm I see. So the keys you're pressing are not recognized by GLFW, which means they are probably not part of the US layout. You get a keycode though? I guess it's possible technically to bind a command to a keycode, it would require a change to the keybinding functionality.
I have a keyboard with a non-US layout, and I would like to use some of the keys with non-english characters on it for custom keybinds. However, since I also often switch between US and native keyboard layout (Estonian), I would like to create these bindings in such a way that they map the specific key, rather than the character.
Currently this can be done for some keys, eg. RBracket and LBracket, which show up in the verbose log as
key: Some(LBracket)
, however, many keys show up askey: Some(Unknown)
and as such I assume they cannot be used in keybinds.Is there some way to map actions to these keys based on their keycode/scancode. If not, could this feature be added?
The text was updated successfully, but these errors were encountered: