multi-touch-dev team mailing list archive

[Chase Douglas <chase.douglas@xxxxxxxxxxxxx>]

On 02/22/2011 09:14 PM, Stephen M. Webb wrote:
> A discussion of the expected behaviour of one-touch gestures came up
> earlier today in a telephone conversation.  The Unity developers
> expressed concern that would be unable to implement single-touch hover
> behaviour because single touches are interpreted by a lower layer as
> mouse pointer actions are are not delivered as gestures even when
> requested.

I'm having a hard time understanding the issue; I think I need more
details :). Are we talking about a touchscreen or a trackpad? What do
you mean by single-touch hover behaviour? We don't have any devices that
actually support touch hover events.

In 10.10 and soon to be 11.04, utouch sits in the server before any
pointer events are generated. When gestures are found, no pointer events
are delivered.

When we get a client-side version of the utouch stack working, we will
still be grabbing touch events before they are converted into pointer
events for touchscreens. The pointer will actually move with the first
touch on the screen, but X motion and button events will not be sent if
a gesture is found. Touchpads are more nuanced, and I don't really want
to get into it unless it's germane to the discussion.

So, does any of this clear things up, or have I gone on a tangent? :)

> This issue was also raised today by the community in bug #723304
> <https://bugs.launchpad.net/utouch-geis/+bug/723304>.

That looks to me like a plain bug. How is it an architectural issue?

Thanks,

-- Chase