[PATCH inputproto 2/2] Add touch classes and events, bump to 2.1

Denis Dzyubenko shadone at gmail.com
Thu Dec 23 05:28:51 PST 2010


On 23 December 2010 12:44, Daniel Stone <daniel at fooishbar.org> wrote:
> 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?

ah I see, I haven't read the new spec about TouchPendingFinish hence
my confusion.

I was talking about a different concept - cancelling a touch sequence
when for example an input device changes - for example when the user
presses a key on the keyboard or window is hidden etc. As far as I
know iOS have that feature - touch is cancelled when hardware key to
switch to another app is pressed. But most importantly javascript
touch api have TouchCancel with similar semantics. In Qt we were
thinking to add TouchCancel event as well - in our case I was thinking
to send TouchCancel whenever we get SlaveSwitch event while the user
is touching the screen.

I guess I need to read the whole thread first, as right now I don't
see a need for TouchPendingFinish.

Best regards,

More information about the xorg-devel mailing list