Rusty, Is there a particular reason for adding another request that's basically identical to "move"? Couldn't we just bump the protocol version and allow the clients to respond to touch events with a move request? The compositor could sort out what kind of event it is based on the serial. --Jason Ekstrand On Aug 14, 2013 12:51 PM, "Rusty Lynch" <<a href="mailto:rusty.lynch@intel.com">rusty.lynch@intel.com</a>> wrote: > > From d1d0df0688650ea23a1c5c788f7d7bbf3e7e034c Mon Sep 17 00:00:00 2001 > From: Rusty Lynch <<a href="mailto:rusty.lynch@intel.com">rusty.lynch@intel.com</a>> > Date: Wed, 14 Aug 2013 08:06:39 -0700 > Subject: [PATCH] Add protocol support for wl_shell_surface_touch_move > > --- > protocol/wayland.xml | 12 ++++++++++++ > 1 file changed, 12 insertions(+) > > diff --git a/protocol/wayland.xml b/protocol/wayland.xml > index d7bbbb9..b106dcf 100644 > --- a/protocol/wayland.xml > +++ b/protocol/wayland.xml > @@ -916,6 +916,18 @@ > <arg name="class_" type="string"/> > </request> > > + <request name="touch_move"> > + <description summary="start an interactive touch based move"> > + Start a touch-driven move of the surface. > + > + This request must be used in response to a touch down event. > + The server may ignore move requests depending on the state of > + the surface (e.g. fullscreen or maximized). > + </description> > + <arg name="seat" type="object" interface="wl_seat" summary="the wl_seat associated with the touch"/> > + <arg name="serial" type="uint" summary="serial of the implicit grab on the touch"/> > + </request> > + > <event name="ping"> > <description summary="ping client"> > Ping a client to check if it is receiving events and sending > -- > 1.8.3.1 > > > > _______________________________________________ > wayland-devel mailing list > <a href="mailto:wayland-devel@lists.freedesktop.org">wayland-devel@lists.freedesktop.org</a> > <a href="http://lists.freedesktop.org/mailman/listinfo/wayland-devel">http://lists.freedesktop.org/mailman/listinfo/wayland-devel</a>