1be019852f
The core pointer concept doesn't really exist anymore in an XI2 world, so the clutter API is a bit of a mismatch with what X provides. Using XIGetClientPointer doesn't really help, as far as i can tell the semantics of XIGetClientPointer are essentially: Whatever the X server picked when it had to reply with device-dependant data to a query without a device specifier. Not very useful... To make matters worse, whether XIGetClientPointer returns a valid pointer depends on whether there has been a query that forced it to pick one in the first place, making the whole thing pretty non-deterministic. This patch changes things around such that instead of using XIGetClientPointer to determine the core pointer, we simply pick the first master pointer device. In practise this will essentially always be the X virtual core pointer. https://bugzilla.gnome.org/show_bug.cgi?id=729462 |
||
---|---|---|
.. | ||
xsettings | ||
clutter-backend-x11.c | ||
clutter-backend-x11.h | ||
clutter-device-manager-core-x11.c | ||
clutter-device-manager-core-x11.h | ||
clutter-device-manager-xi2.c | ||
clutter-device-manager-xi2.h | ||
clutter-event-x11.c | ||
clutter-glx-texture-pixmap.c | ||
clutter-glx-texture-pixmap.h | ||
clutter-glx.h | ||
clutter-input-device-core-x11.c | ||
clutter-input-device-core-x11.h | ||
clutter-input-device-xi2.c | ||
clutter-input-device-xi2.h | ||
clutter-keymap-x11.c | ||
clutter-keymap-x11.h | ||
clutter-settings-x11.h | ||
clutter-stage-x11.c | ||
clutter-stage-x11.h | ||
clutter-x11-texture-pixmap.c | ||
clutter-x11-texture-pixmap.h | ||
clutter-x11.h |