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

gtk+ (bugzilla.gnome.org) bugzilla at gnome.org
Mon Jun 9 07:45:45 PDT 2014


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

Carlos Garnacho <carlosg> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #278104|none                        |reviewed
             status|                            |

--- Comment #3 from Carlos Garnacho <carlosg at gnome.org> 2014-06-09 14:45:41 UTC ---
(From update of attachment 278104)
Thanks Sjoerd for the patch! having slot id=0 is indeed possible on wayland...
I would however find more convenient to have the event sequence tied somehow to
the slot ID (say id+1), that'd be helpful for debugging situations above GDK,
although eventually there should maybe be a
gdk_wayland_event_sequence_get_slot().

The way weston/mutter make use of mtdev should ensure slot is kept between
0..max_dev_touches-1, if a compositor for some reason implements this as a
counter, it could overflow to 0 at some point, but it wouldn't be worse than
X11 in that regard...

-- 
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.


More information about the Wayland-bugs mailing list