Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improving Scan Code and General Keyboard Layout Handling #732

Closed
Osspial opened this issue Dec 1, 2018 · 1 comment
Closed

Improving Scan Code and General Keyboard Layout Handling #732

Osspial opened this issue Dec 1, 2018 · 1 comment
Labels
C - needs discussion Direction must be ironed out S - api Design and usability S - platform parity Unintended platform differences

Comments

@Osspial
Copy link
Contributor

Osspial commented Dec 1, 2018

Right now, we don't provide any way to convert ScanCodes to or from VirtualKeyCodes. Providing that is useful for storing layout-independent keymaps, but displaying the actual key to the user in a GUI.

What's more, because we're (usually) reporting the raw scan code provided by the OS there seems to be some inconsistency what key corresponds to what on different platforms. From my testing on Windows and Linux the letter/punctuation keys, number keys, function keys, and escape, space, shift, enter, tab, backspace, and caps keys are all identical across both platforms, but various other keys (such as arrow keys) weren't consistent. That makes it impossible to use scan codes to portably store keyboard layouts.

@Imberflur
Copy link
Contributor

#2678 seems related

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C - needs discussion Direction must be ironed out S - api Design and usability S - platform parity Unintended platform differences
Development

No branches or pull requests

4 participants