#149 closed defect (fixed)
use XkbKeycodeToKeysym instead of XKeycodeToKeysym (deprecation)
Reported by: | Antoine Martin | Owned by: | Antoine Martin |
---|---|---|---|
Priority: | trivial | Milestone: | 0.8 |
Component: | core | Version: | trunk |
Keywords: | keyboard | Cc: |
Description (last modified by )
We get these warnings:
/usr/include/gtk-2.0/gtk/gtkitemfactory.h:47:1: warning: function declaration isn't a prototype [-Wstrict-prototypes] bindings.c: In function '__pyx_f_8wimpiggy_8lowlevel_8bindings_KeysymToKeycodes': bindings.c:10353:7: warning: 'XKeycodeToKeysym' is deprecated (declared at /usr/include/X11/Xlib.h:1695) [-Wdeprecated-declarations] bindings.c: In function '__pyx_f_8wimpiggy_8lowlevel_8bindings__get_modifier_mappings': bindings.c:11494:9: warning: 'XKeycodeToKeysym' is deprecated (declared at /usr/include/X11/Xlib.h:1695) [-Wdeprecated-declarations] bindings.c: In function '__pyx_pf_8wimpiggy_8lowlevel_8bindings_68get_keycodes_down': bindings.c:12712:5: warning: 'XKeycodeToKeysym' is deprecated (declared at /usr/include/X11/Xlib.h:1695) [-Wdeprecated-declarations]
See freedesktop.org bug 5349 and freedesktop.org bug 25732
Together with the fix in 108#comment:12, this should fix most keyboard related issues?
Change History (6)
comment:1 Changed 9 years ago by
Description: | modified (diff) |
---|---|
Status: | new → accepted |
comment:3 Changed 9 years ago by
Description: | modified (diff) |
---|
comment:4 Changed 8 years ago by
Milestone: | 0.4 → 0.8 |
---|
comment:6 Changed 6 weeks ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/149
Note: See
TracTickets for help on using
tickets.
We may have to use more than just
XkbKeycodeToKeysym
... there's a whole new API to use inXkb
, with very little in terms of "howto" documentation.Maybe we can get away with just figuring out "group" and "level"?
This ought to allow us to fix the following bugs:
And maybe also: