| |||||||||||||
The life story of the XInput multitouch extensionThe life story of the XInput multitouch extensionPosted Mar 8, 2012 10:28 UTC (Thu) by daniels (subscriber, #16193)In reply to: The life story of the XInput multitouch extension by russell Parent article: The life story of the XInput multitouch extension
By and large, they don't need the clever bits, as global gesture recognition is performed within the display server (same model as Wayland), and everything else just goes to the relevant app. The only reason X needed to be so clever is because our model is completely different to everyone else, so things were a lot more complex, and we had no relevant prior art to lean on.
(Log in to post comments)
The life story of the XInput multitouch extension Posted Mar 8, 2012 21:39 UTC (Thu) by bronson (subscriber, #4806) [Link]
Any idea of whether Wayland is doing multitouch correctly? From your experience with X I'd imagine you'd be among the best to recognize good technique vs. bad.
The ability to leave one finger on the touchpad is a good example: it's non-obvious at first and rather important. I'm really glad you guys took the extra time to get that right.
The life story of the XInput multitouch extension Posted Mar 9, 2012 11:16 UTC (Fri) by Aissen (subscriber, #59976) [Link]
From what Keith Packard and Peter Hutterer told me at FOSDEM, Wayland will try to use the same API and semantics as in XI 2.2.
Except for grabs, which are considered a "necessary evil", and might not be available to apps (only the compositor). I'd love to hear more from a wayland developer though.
|
|||||||||||||