Changes between Version 8 and Version 9 of Keyboard
- Timestamp:
- 12/11/13 10:13:33 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Keyboard
v8 v9 1 {{{#!div class="box" 1 2 = Keyboard = 2 3 … … 6 7 [[BR]] 7 8 We currently use the core {{{X11}}} api, but we should be moving to {{{Xkb}}}, or maybe the [http://fk01.fooishbar.org/?p=39 xkbcommon] wrapper (#371). 9 }}} 8 10 9 11 12 {{{#!div class="box" 10 13 == Solved Bugs == 11 14 * When connecting over high latency links, use the {{{--no-keyboard-sync}}} option to prevent keys from repeating. This switch may cause other problems though. 12 15 * US layout and most common layouts should work ok. 13 16 * If starting xpra from an environment which has non-standard input methods, this can interfere, see #286 17 }}} 14 18 15 19 20 {{{#!div class="box" 16 21 == Unsolvable Bugs == 17 22 On Posix systems, if your distribution does not provide {{{setxkbmap -query}}} then you should really upgrade it, there are bugs which are simply unfixable when one uses outdated software. 23 }}} 18 24 19 25 26 {{{#!div class="box" 20 27 == Pending Bugs == 21 28 * Supporting multiple layouts and switching layouts reliably and/or manually: #230, #166, #86 22 29 * Keyboard sync may end up pressing the wrong key: #222 23 30 * Input grabs: #139 31 }}} 24 32 25 33 34 {{{#!div class="box" 26 35 == Reporting Bugs == 27 36 First, please check the bugs above to see if any match your problem or seems related. … … 38 47 * the [https://www.xpra.org/trac/wiki/Debugging#ViaLogging XPRA_KEYBOARD_DEBUG] environment variable can increase logging verbosity (quite a bit with a value of "{{{1}}}" and a lot more with a value of "{{{2}}}") 39 48 * using the test script [https://www.xpra.org/trac/browser/trunk/src/xpra/gtk_view_keyboard.py gtk_view_keyboard.py] (named {{{GTK_Keyboard_Test.exe}}} on MS Windows) can also be useful sometimes 49 }}}