[Wayland-bugs] [Bug 728426] New: Implement the wl_touch interface

gtk+ (bugzilla.gnome.org) bugzilla at gnome.org
Thu Apr 17 08:01:37 PDT 2014


https://bugzilla.gnome.org/show_bug.cgi?id=728426
  gtk+ | Backend: Wayland | unspecified

           Summary: Implement the wl_touch interface
    Classification: Platform
           Product: gtk+
           Version: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: Backend: Wayland
        AssignedTo: gtk-bugs at gtk.org
        ReportedBy: carlosg at gnome.org
         QAContact: gtk-bugs at gtk.org
                CC: rob at robster.org.uk, wayland-bugs at lists.freedesktop.org
     GNOME version: ---


For input, the wayland backend solely implements the wl_pointer and wl_keyboard
interfaces, which leaves touch events unhandled. I'm attaching 2 patches that:
1) decouples core devices from the seat capabilities by adding slave devices in
between, this is certainly closer to what x11 does, (plus GTK+ quite expects
core devices to always come in pointer/keyboard pairs)
2) Implements wl_touch, translating events into GdkEventTouch events. 

One aspect I'm a bit dubious about is pointer emulation, on x11 the first touch
gets to emulate pointer events, but on the wayland protocol pointer and touch
are completely decoupled, I've replicated that behavior in GDK, having the
pointer moving and emitting events independently brings some confusion. It
should be better I guess when everything gets GDK_TOUCH_MASK, either directly
or indirectly.

Probably for the longer term it would be better to stick to the facts here, and
just have all touch events as !emulating_pointer on wayland.

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