diff options
| author | Peter Hutterer <peter.hutterer@who-t.net> | 2009-10-15 11:13:47 +1000 |
|---|---|---|
| committer | Peter Hutterer <peter.hutterer@who-t.net> | 2009-10-15 11:36:49 +1000 |
| commit | 1d86f5dec16beaf9391f320d7702cc59e9486bf4 (patch) | |
| tree | 3c08d7a6e09207b9cc30aac3d2fbf190b1451e5f /man/evdev.man | |
| parent | fbd86e2530f3f69f397d3bae9ad87cf8e2d14221 (diff) | |
Convert IgnoreAbsolute/RelativeAxes options into trinary state.
The Xen Virtual Pointer device exports both absolute and relative axes from
the kernel device. Which coordinates are used is a run-time decision and
depends on the host-specific configuration.
0a3657d2ee62f4086e9687218cb33835ba61a0b3 broke these devices, and they are
now unusable out-of-the-box as there is no configuration to cover them.
This patch converts the IgnoreAbsoluteAxes and the IgnoreRelativeAxes
configuration options into a trinary state.
1. If unset, configure the device as normal by trying to guess the right
axis setup.
2. If set to true, ignore the specific axis type completely (except for
wheel events).
3. If set to false, explicitly 'unignore' the axis type, alwas configuring
it if it is present on the device. This setting introduces seemingly
buggy behaviour (see Bug 21832)
1. and 2. replicate the current driver behaviour.
The result of 3. is that is that if a device has absolute axes and the
options set to false, both axes will be initialized (absolute last to get
clipping right). This requires axis labelling priorty to switch from
relative first to absolute first.
Relative events are forwarded into the server through the absolute axes,
the server scales this into the device absolute range and everyone is happy.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Diffstat (limited to 'man/evdev.man')
| -rw-r--r-- | man/evdev.man | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/man/evdev.man b/man/evdev.man index e322eb6..9dd7a77 100644 --- a/man/evdev.man +++ b/man/evdev.man @@ -138,13 +138,18 @@ Invert the given axis. Default: off. Property: "Evdev Axis Inversion". .BI "Option \*qIgnoreRelativeAxes\*q \*q" Bool \*q .TP 7 .BI "Option \*qIgnoreAbsoluteAxes\*q \*q" Bool \*q -Ignore the specified type of axis. Default: off. The X server cannot deal +Ignore the specified type of axis. Default: unset. The X server cannot deal with devices that have both relative and absolute axes. Evdev tries to guess wich axes to ignore given the device type and disables absolute axes for mice and relative axes for tablets, touchscreens and touchpad. These options allow to forcibly disable an axis type. Mouse wheel axes are exempt and will work even if relative axes are ignored. No property, this configuration must be set in the configuration. +.br +If either option is set to False, the driver will not ignore the specified +axes regardless of the presence of other axes. This may trigger buggy +behavior and events from this axis are always forwarded. Users are +discouraged from setting this option. .TP 7 .BI "Option \*qReopenAttempts\*q \*q" integer \*q Number of reopen attempts after a read error occurs on the device (e.g. after |