diff options
author | Peter Hutterer <peter.hutterer@who-t.net> | 2012-01-26 13:56:38 +1000 |
---|---|---|
committer | Peter Hutterer <peter.hutterer@who-t.net> | 2012-02-02 17:39:39 +1000 |
commit | 217afacda01b082f39fb6816e62ec20e4791857f (patch) | |
tree | 26046bd097b85e148a54d8df82fab86d559559e0 /configure.ac | |
parent | fc9372868bb772f38a6b17299ef26e3dc9c2ff87 (diff) | |
download | xorg-proto-inputproto-217afacda01b082f39fb6816e62ec20e4791857f.tar.gz |
specs: explain touch behaviour for dependent devices
Dependent devices don't send touch events until the interaction is a true
touch interaction (i.e. doesn't just serve to move the pointer). Once that
happens, all touchpoints send touch events exclusively. Pointer movement
restarts once we're down to one touch that controls the pointer again.
For clients listening to touch events in addition to pointer events, this
also means that a two-finger tap looks identical to holding one finger down
and tapping with a second-finger. Both actions will result in short
TouchBegin/TouchEnd sequences for both fingers.
The above is the default behaviour we expect from touchpads, the protocol is
more generically worded to leave more room for drivers to decide when a
touch only controls the pointer and when it doesn't.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Reviewed-by: Chase Douglas <chase.douglas@canonical.com>
Diffstat (limited to 'configure.ac')
0 files changed, 0 insertions, 0 deletions