diff options
| author | Peter Hutterer <peter.hutterer@who-t.net> | 2011-08-24 09:07:15 +1000 |
|---|---|---|
| committer | Chase Douglas <chase.douglas@canonical.com> | 2011-08-23 17:57:53 -0700 |
| commit | ae6ba6b37e47134914b8fedb6524372f0a8119c0 (patch) | |
| tree | 7567fce70cb6b9726d5def288148d3adc108526a | |
| parent | 544ce0cee3cc146ed1df06ed5762d21ecdfe9e8a (diff) | |
Coordinates are always absolute, no need to re-state it
Coordinates in DeviceEvents are always absolute, regardless of the axis
mode. The same is true for touch events, stating it again here just adds to
the confusion.
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.txt | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/specs/XI2proto.txt b/specs/XI2proto.txt index eb6bce6..ee8ca49 100644 --- a/specs/XI2proto.txt +++ b/specs/XI2proto.txt @@ -759,8 +759,7 @@ client. If no min and max information is available, both must be 0. A list of properties to denote extra information about the device. Devices with a TouchClass emit touch events with the same axes as pointer -events. However, the X and Y axes of touch events are always provided in -absolute mode co-ordinates. +events. [[requests-selectevents]] ┌─── |