diff options
| author | Peter Hutterer <peter.hutterer@who-t.net> | 2011-11-08 15:36:02 +1000 |
|---|---|---|
| committer | Peter Hutterer <peter.hutterer@who-t.net> | 2011-11-08 15:36:02 +1000 |
| commit | 279524b089c7b42871ee072cfc03a1fad7421b7b (patch) | |
| tree | 33238cd8d52db5bca2cffa6625aa722acd5ab70f | |
| parent | 9f2b1a33063b139756e08951affe802e8af39a76 (diff) | |
specs: scroll events have no specific event type, state so.
This wasn't clear enough in the current spec.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
| -rw-r--r-- | specs/XI2proto.txt | 15 |
1 files changed, 8 insertions, 7 deletions
diff --git a/specs/XI2proto.txt b/specs/XI2proto.txt index b6707b3..2a25c4e 100644 --- a/specs/XI2proto.txt +++ b/specs/XI2proto.txt @@ -128,13 +128,14 @@ simply dragging your finger along a designated strip along the side of the touchpad. Newer X servers may provide scrolling information through valuators to -provide scroll events with more precision than the button events. Valuators -for axes sending scrolling information must have one ScrollClass for each -scrolling axis. - -If scrolling valuators are present on a device, the server must provide -two-way emulation between these valuators and the legacy button events for -each delta unit of scrolling. +provide clients with more precision than the legacy button events. This +scrolling information is part of the valuator data in device events. +Scrolling events do not have a specific event type. + +Valuators for axes sending scrolling information must have one +ScrollClass for each scrolling axis. If scrolling valuators are present on a +device, the server must provide two-way emulation between these valuators +and the legacy button events for each delta unit of scrolling. One unit of scrolling in either direction is considered to be equivalent to one button event, e.g. for a unit size of 1.0, -2.0 on an valuator type |