|Reported by:||Antoine Martin||Owned by:||Antoine Martin|
|Keywords:||win32 osx shadow||Cc:|
Description (last modified by )
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 ticket: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.
Change History (6)
comment:1 Changed 11 months ago by
|Status:||new → assigned|
comment:4 Changed 7 months ago by
|Summary:||win32 and osx shadow servers untranslated keyboard → untranslated keyboard|