[PATCH inputproto 2/2] Add touch classes and events, bump to 2.1
shadone at gmail.com
Thu Dec 23 03:33:42 PST 2010
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
> 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.
More information about the xorg-devel