Convert from keysym to scancode key handling #13
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
looks good, thank you! i will test it asap. |
|
btw related #7 |
|
Ah nice, didn't spot that one. How would one do keyboard layout configuration after that kind of change? |
|
I realized that this isn't ideal for a few reasons:
I will need to do tests with a proper keyboard for the former and some more hacking for the latter. |
wasamasa
force-pushed
the
qwerty-layout
branch
from
1788bb6
to
9210a70
Compare
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The graphical shell has rather weird keyboard handling, on a QWERTY-US layout I cannot even type
(+ 1 1). I've switched the responsible code from keysyms to scancodes to enforce a consistent QWERTY-US layout, but can change it to the presumably customized QWERTZ-DE layout if you wish.