#1373 closed defect (fixed)
shared mode keyboard conflicts
| Reported by: | Antoine Martin | Owned by: | alas |
|---|---|---|---|
| Priority: | major | Milestone: | 2.0 |
| Component: | server | Version: | trunk |
| Keywords: | Cc: |
Description
Follow up from ticket:41#comment:39.
Each new client connection overwrites the keymap.
We need to keep track of who owns the keyboard (separate from "ui-driver"?) and either:
- change the keymap on the fly when a new user interacts with the session - hard, may not work well as setting the keymap is partly asynchronous
- translate keyboard events for the "other" clients
Change History (4)
comment:1 Changed 5 years ago by
| Owner: | changed from Antoine Martin to alas |
|---|
comment:2 Changed 5 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Tested (trunk Fedora 25 server, and Fedora 25 and Win8.1 clients) and it seems to behave, at least with my two identically-layed-out ENG-US keyboards. Closing
comment:4 Changed 12 months ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1373
Note: See
TracTickets for help on using
tickets.
copyleft 2010 - 2021
Done in r15110.
We can now connect multiple clients with completely different keymaps (different OS, different layout, etc) and each client should still be able to use most of their keys..
The first client to connect will still "own" the keymap, which means that we won't be adding new layouts from the secondary clients.
How to test:
Both clients should be able to use the keyboard and have the correct keys appear in applications (ie: xterm).
Note: this ticket is not meant to give 100% coverage of keyboard input when sharing is enabled (which may not be achievable anyway), just to make it a lot more usable than before.