-
-
Notifications
You must be signed in to change notification settings - Fork 171
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
untranslated keyboard #1172
Labels
Milestone
Comments
Initial support in r13328: I can attach an X11 client to an X11 server with Still TODO:
|
Rather than extending the key packet with yet more data, we could use #1942 (new packet format). |
This was referenced Jan 22, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Follow up from #1099.
We should just pass the raw scancode to the server when we know it will be able to handle it. ie: win32 client with win32 server.
Also, expand r12399 to support more characters - generate the list? (deal non ascii characters too)
Think about better handling for keyboard layout mismatch between client and server, see #1099#comment:10. We could keep multiple translation tables for each layout in use, then use the correct translation for the currently active keyboard layout.
See #1027, #817.
The text was updated successfully, but these errors were encountered: