summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Hutterer <peter.hutterer@who-t.net>2011-09-14 05:46:43 +1000
committerChase Douglas <chase.douglas@canonical.com>2011-09-13 15:29:28 -0500
commit05fc509fdca8d8b414a20f1359b9cb80caf5240a (patch)
tree0d425a4901086e77e9488a45e2eb0648ce9fceaf
parent94fecdf129d8ab5bece049a26eed03d24affb549 (diff)
specs: if a sequence ends, all clients get TouchPendingEnd
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Chase Douglas <chase.douglas@canonical.com> Signed-off-by: Chase Douglas <chase.douglas@canonical.com>
-rw-r--r--specs/XI2proto.txt10
1 files changed, 5 insertions, 5 deletions
diff --git a/specs/XI2proto.txt b/specs/XI2proto.txt
index 2bc9d30..6a5345c 100644
--- a/specs/XI2proto.txt
+++ b/specs/XI2proto.txt
@@ -374,11 +374,11 @@ TouchEnd events, and the touch sequence is exclusively delivered to the
owner from that point on.
If the touch sequence physically ends while the owner of the touch sequence
-has not yet accepted or rejected ownership, the client receives a
-TouchUpdate event with the TouchPendingEnd flag set, but must still accept
-or reject the sequence nonetheless. If the owner rejects the touch sequence,
-the server will still attempt to exhaust all other passive grabs and/or
-event selections looking for a final owner.
+has not yet accepted or rejected ownership, all clients receive a
+TouchUpdate event with the TouchPendingEnd flag set. The owner must still
+accept or reject the sequence nonetheless. If the owner rejects the touch
+sequence, the server will still attempt to exhaust all other passive grabs
+and/or event selections looking for a final owner.
Clients may opt for touch events to be delivered before they become the
owner of the touch sequence. In this case, the logical state of the device (as