[PATCH 2/2] input: Warn if the touch point up and down events get out of sync

Daniel Stone daniel at fooishbar.org
Fri Sep 27 14:38:13 PDT 2013


On 24 September 2013 15:05, Bill Spitzak <spitzak at gmail.com> wrote:
> I really really think this idea should be changed.

With almost zero consideration to the downsides.

> Clients should just be
> prepared for excess up and down events, and excess focus in/out. Avoiding
> them becomes nearly impossible as you are probably noticing, and pretty much
> means the compositor must maintain the state of *EVERY* button for *EVERY*
> client.

Yes.  If your starting point is that the thing directing your input
events and focus shouldn't have to know where to direct its input
events or focus, then we disagree on something I consider axiomatic.

A more useful starting point might be a prototype of a system where
the compositor didn't track of this, which actually functioned in any
meaningful way in the real world.


More information about the wayland-devel mailing list