diff options
author | Peter Hutterer <peter.hutterer@who-t.net> | 2012-01-03 09:26:22 +1000 |
---|---|---|
committer | Peter Hutterer <peter.hutterer@who-t.net> | 2012-01-03 13:21:55 +1000 |
commit | 997ae0343730c66d581fd147741cbe27fbe55af2 (patch) | |
tree | d130f636224332b24b0396382e3c3b248851b9f2 /XI2.h | |
parent | 5ee845c1bf457159a034111c3d0df584aa600cd6 (diff) |
Set a flag on the pointer-emulating touch event
Toolkits need to know which touch event emulated a pointer event and which
ones do not. To quote Carlos Garnacho:
GTK+ does client-side windows by default (GdkWindows without a backing X
window), for this to work the toplevel window in the client needs to
select for more events that it wouldn't normally select for in order to
cater for the event masks in such child "windows". This means that
ideally GTK+ should set the touch events mask in the toplevel, and then
find out whether the "window" would receive pointer or touch events for
the sequence emulating the pointer, and perform the emulation itself.
Reported-by: Carlos Garnacho <carlosg@gnome.org>
Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Diffstat (limited to 'XI2.h')
-rw-r--r-- | XI2.h | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -158,6 +158,7 @@ #define XIPointerEmulated (1 << 16) /* Device event flags (touch events only) */ #define XITouchPendingEnd (1 << 16) +#define XITouchEmulatingPointer (1 << 17) /* Touch modes */ #define XIDirectTouch 1 |