Giovanni Campagna 59f1e531f9 ClutterEvent: add API to query the full keyboard state when the event was generated ... When talking to other applications or serializing the modifier state (and in particular when implementing a wayland compositor), the effective modifier state alone is not sufficient, one needs to know the base, latched and locked modifiers. Previously one could do with backend specific functionality such as clutter_device_manager_evdev_get_xkb_state(), but the problem is that the internal data structures are updated as soon as the events are fetched from the upstream source, but the events are reported to the application some time later, and thus the two can get out of sync. This way, on the other hand, the information is cached in the event, and provided to the application with the value that was current when the event was generated. https://bugzilla.gnome.org/show_bug.cgi?id=706494		2013-09-09 13:18:23 +02:00
..
clutter-device-manager-evdev.c	ClutterEvent: add API to query the full keyboard state when the event was generated	2013-09-09 13:18:23 +02:00
clutter-device-manager-evdev.h	evdev: Merge clutter-event-evdev.[ch] into the device manager	2010-11-30 14:40:38 +00:00
clutter-evdev.h	evdev: add callback to constrain the pointer position	2013-09-09 12:00:52 +02:00
clutter-input-device-evdev.c	evdev: remove dead code	2013-08-13 09:41:45 +02:00
clutter-input-device-evdev.h	evdev: remove dead code	2013-08-13 09:41:45 +02:00
clutter-xkb-utils.c	ClutterEvent: add API to query the full keyboard state when the event was generated	2013-09-09 13:18:23 +02:00
clutter-xkb-utils.h	ClutterEvent: add API to query the full keyboard state when the event was generated	2013-09-09 13:18:23 +02:00