Jonas Ådahl 615b0f46ae evdev: Keep track of the pointer coordinate ourself ... When multiple relative motion events are received and queued, we can't base the relative => absolute motion conversion off of the stage pointer position, since that is only updated when the queue is processed at the beginning of each frame. The effect of trying to use the stage pointer position was that subsequent motion events were effectively dropped. To improve things, switch to keeping track of the pointer position ourselves in the evdev backend and adding to that. This has the side effect of making the internal function _clutter_input_device_set_coords not effect the internal coordinate state of the evdev stage, but AFAICS there is nothing depending on that so that should be fine. https://bugzilla.gnome.org/show_bug.cgi?id=746328		2015-03-18 22:45:38 +08:00
..
clutter-device-manager-evdev.c	evdev: Keep track of the pointer coordinate ourself	2015-03-18 22:45:38 +08:00
clutter-device-manager-evdev.h
clutter-evdev.h	docs: Minimal fixes for the API reference	2015-03-03 15:53:04 +00:00
clutter-input-device-evdev.c	evdev: Set vendor/product IDs on input devices	2015-01-09 17:01:22 +01:00
clutter-input-device-evdev.h	evdev: Used floating point instead of fixed point numbers	2014-06-10 10:39:42 +01:00
clutter-xkb-utils.c
clutter-xkb-utils.h