xpra icon
Bug tracker and wiki

Opened 4 years ago

Last modified 7 hours ago

#1172 assigned enhancement

untranslated keyboard

Reported by: Antoine Martin Owned by: Antoine Martin
Priority: major Milestone: 4.0
Component: platforms Version: trunk
Keywords: win32 osx shadow Cc:

Description (last modified by Antoine Martin)

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 (7)

comment:1 Changed 4 years ago by Antoine Martin

Status: newassigned

See also #1062.

Version 0, edited 4 years ago by Antoine Martin (next)

comment:2 Changed 4 years ago by Antoine Martin

Description: modified (diff)

comment:3 Changed 4 years ago by Antoine Martin

Milestone: 0.181.0

Milestone renamed

comment:4 Changed 3 years ago by Antoine Martin

Summary: win32 and osx shadow servers untranslated keyboarduntranslated keyboard

Initial support in r13328: I can attach an X11 client to an X11 server with --keyboard-layout=fr --keyboard-raw=yes and get a 'fr' layout even though my local keymap is set to 'gb'. The raw keycodes are used unmodified by the server.

Still TODO:

  • extend this to shadow servers (win32 and osx)
  • maybe support X11 server layout changes: re-detect updated settings
  • maybe have an "auto" mode for enabling this when both ends are compatible? (ie: win32 shadow server with win32 client, X11 client with X11 server)
  • maybe disable or remove the tray menu for cases where it won't be applicable

comment:5 Changed 16 months ago by Antoine Martin

Milestone: 1.02.5

Rather than extending the key packet with yet more data, we could use #1942 (new packet format).

comment:6 Changed 6 months ago by Antoine Martin

Milestone: 2.54.0

comment:7 Changed 7 hours ago by totaamwin32

See also #2560, #2561.

Note: See TracTickets for help on using tickets.