[PATCH libinput] touchpad: fix double/multitap timeouts

[Bill Spitzak]

On 05/01/2015 03:23 PM, Peter Hutterer wrote:
> On 2/05/2015 04:21 , Bill Spitzak wrote:
>> Are you saying the first event is delayed until it knows whether it is
>> double-tap or not? That is not going to work, it will introduce a huge
>> annoying latency to interaction.
>>
>> I suspect I am misunderstanding this and an event is sent, but want to
>> make sure.
>
> There's an svg diagram showing the state machine in the doc directory.
> It shows when events are sent. Short answer: the press event is sent
> very early, the release event may be delayed.
>
> And to pre-empt the next comment: feel free to come up with a better
> solution that doesn't have said "annoying latency" but still allows for
> tap-and-drag. If you do, please let us know in (pseudo)code rather than
> general comments.

I feel like delaying the release event may work ok. Clients that don't 
want latency would react to the press event. And if clients knew that 
releasing everything meant they were not going to get anything other 
than basic press events next it might be helpful.