forked from AuroraMiddleware/gtk
5b118a9fd7
Weston numbers its touch sequences ids starting from 0, thus simply setting the GtkEvents touch.sequence to the touch id value typically causes gdk_event_get_event_sequence to return NULL. Unfortunately this confuses other parts of GDK. As both weston & mutter keep the sequence id between 0..max_dev_touches -1 simply use + 1 to keep the id > 0. While this isn't entirely correct (compositor could send -1 as the touch id), this keeps the touch id in gtk tied to the touch id from weston which is useful for debugging. A more thorough solution could be done when it turns out this is an issue in practise https://bugzilla.gnome.org/show_bug.cgi?id=731371 |
||
|---|---|---|
| .. | ||
| protocol | ||
| gdkapplaunchcontext-wayland.c | ||
| gdkcursor-wayland.c | ||
| gdkdevice-wayland.c | ||
| gdkdisplay-wayland.c | ||
| gdkdisplay-wayland.h | ||
| gdkdnd-wayland.c | ||
| gdkeventsource.c | ||
| gdkkeys-wayland.c | ||
| gdkprivate-wayland.h | ||
| gdkscreen-wayland.c | ||
| gdkselection-wayland.c | ||
| gdkwayland.h | ||
| gdkwaylanddevice.h | ||
| gdkwaylanddisplay.h | ||
| gdkwaylandselection.h | ||
| gdkwaylandwindow.h | ||
| gdkwindow-wayland.c | ||
| Makefile.am | ||
| wm-button-layout-translation.c | ||
| wm-button-layout-translation.h | ||