[Wayland-bugs] [Bug 731371] Gtk gets confused by wayland touch events

[gtk+ (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=731371
  gtk+ | Backend: Wayland | 3.13.x

Sjoerd Simons <sjoerd> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED

--- Comment #5 from Sjoerd Simons <sjoerd at luon.net> 2014-06-12 10:36:19 UTC ---
committed:

commit 5b118a9fd768f752f3e770d7734596e239de942d
Author: Sjoerd Simons <sjoerd.simons at collabora.co.uk>
Date:   Sun Jun 8 17:21:14 2014 +0200

    wayland: Ensure the touch sequence pointer value is non-null

    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

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.