[PATCH inputproto 2/2] Add touch classes and events, bump to 2.1
daniel at fooishbar.org
Thu Dec 23 03:44:23 PST 2010
On Thu, Dec 23, 2010 at 12:33:42PM +0100, Denis Dzyubenko wrote:
> On 23 December 2010 01:04, Peter Hutterer <peter.hutterer at who-t.net> wrote:
> >> The idea behind TouchEnd is that it's the final event clients receive,
> >> and that they can clean up all state for that touch as soon as they get
> >> it. So, TouchPendingFinish arrives in a TouchMotion event with zero
> >> valuators.
> > ah, I didn't notice that when reading the spec. this needs to be explicitly
> > stated somewhere. (bikeshed: TouchPendingFinish → TouchTerminated?)
> > is it worth adding another event type for TouchEnd (physical end) and
> > TouchTerminated (for actual end)?
> I second this. Haven't thought about it that much, but saw the same
> concept in some other api implementation - having TouchCancel event
> would be pretty convenient.
It's not really cancelled though.
The finger has been lifted, so the touch has _physically_ finished, but
the point of the event is to let you know that, while this has happened,
you may still become the owner of this touch sequence in the future.
Do you have a pointer to the other API?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 198 bytes
Desc: Digital signature
More information about the xorg-devel