base icon indicating copy to clipboard operation
base copied to clipboard

movement key bindings in editing mode

Open asmanel opened this issue 7 years ago • 4 comments

In the setting menus, keys for different actions can be set. Default values are for QWERTY keyboards. When the used keyboard isn't of this kind, you easily can change it (I use an AZERTY Keyboard)

The problem with the movement keys (and maybe some other keys) is they are used in edit mode but their settings (via the menus) don't affect this mode.

To fix it, I needed to type this in the console : /editbind Z forward /editbind Q left

asmanel avatar Jan 23 '18 23:01 asmanel

Keyboard layouts other than en-US are not very well supported in the game, although I hope these issues can be resolved before the 2.0 release.

Another bug is when you start the game in one keyboard (in my case, Canadian French) and then switch over to en-US while the game is running, any key that differs between fr-CA and en-US stop working.

The problem I see right now is that we can't implement EVERY single keyboard layout, but I'd be surprised if SDL2 didn't include some functionality to deal with other keyboards, via a translator (press Z - game understand W. In the settings menu, show the key bound to moving forward, game sees W, UI displays Z)

acerspyro avatar Jan 23 '18 23:01 acerspyro

This just needs us to allow defining the buttons for all bind types from the UI. It isn't about "handling" the keyboard, but allowing the user to properly define their own layout if it doesn't match QWERTY or they don't like the default layout.

qreeves avatar Jan 24 '18 02:01 qreeves

@qreeves Redefining the entire layout just because your keyboard doesn't match gets tedious pretty fast.

The keys are all in the same place and are probably mapped to the same key ID internally, this is what we (or SDL2) have to translate.

My bug still stands, however.

acerspyro avatar Jan 24 '18 03:01 acerspyro

The original issue here was resolved with #868 since edit keybinds were added to the binds UI.

There may yet be a need for a keyboard translation setup. Perhaps a hardcoded set of keys to re-assign for each layout that is not PC104? This would at least allow setting each layout to a proper "default" setting.

no-lex avatar Feb 26 '19 17:02 no-lex