From 5c897995ccb102b38c562920174fc552631c9c5c Mon Sep 17 00:00:00 2001 From: Michael Witten Date: Tue, 4 Aug 2009 03:11:49 -0500 Subject: [PATCH] evdev.c: Fix/improve discrimination of rel/abs axes The relevant comment from evdev.c: We don't allow relative and absolute axes on the same device. The reason is that some devices (MS Optical Desktop 2000) register both rel and abs axes for x/y. The abs axes register min/max; this min/max then also applies to the relative device (the mouse) and caps it at 0..255 for both axes. So, unless you have a small screen, you won't be enjoying it much; consequently, absolute axes are generally ignored. However, currenly only a device with absolute axes can be registered as a touch{pad,screen}. Thus, given such a device, absolute axes are used and relative axes are ignored. Signed-off-by: Michael Witten --- src/evdev.c | 38 ++++++++++++++++++++++++++++---------- 1 files changed, 28 insertions(+), 10 deletions(-) diff --git a/src/evdev.c b/src/evdev.c index e4e6d72..0d3cf76 100644 --- a/src/evdev.c +++ b/src/evdev.c @@ -1427,16 +1427,32 @@ EvdevInit(DeviceIntPtr device) EvdevAddKeyClass(device); if (pEvdev->flags & EVDEV_BUTTON_EVENTS) EvdevAddButtonClass(device); - /* We don't allow relative and absolute axes on the same device. Reason - Reason being that some devices (MS Optical Desktop 2000) register both - rel and abs axes for x/y. - The abs axes register min/max, this min/max then also applies to the - relative device (the mouse) and caps it at 0..255 for both axis. - So unless you have a small screen, you won't be enjoying it much. - - FIXME: somebody volunteer to fix this. + + /* We don't allow relative and absolute axes on the same device. The + * reason is that some devices (MS Optical Desktop 2000) register both + * rel and abs axes for x/y. + * + * The abs axes register min/max; this min/max then also applies to the + * relative device (the mouse) and caps it at 0..255 for both axes. + * So, unless you have a small screen, you won't be enjoying it much; + * consequently, absolute axes are generally ignored. + * + * However, currenly only a device with absolute axes can be registered + * as a touch{pad,screen}. Thus, given such a device, absolute axes are + * used and relative axes are ignored. */ - if (pEvdev->flags & EVDEV_RELATIVE_EVENTS) { + + if (pEvdev->flags & (EVDEV_TOUCHPAD | EVDEV_TOUCHSCREEN)) + { + xf86Msg(X_INFO,"%s: touchpads and touchscreens ignore relative " + "axes.\n", device->name); + + pEvdev->flags &= ~EVDEV_RELATIVE_EVENTS; + + /* Initialization code is below */ + + } else if (pEvdev->flags & EVDEV_RELATIVE_EVENTS) { + if (EvdevAddRelClass(device) == Success) { if (pEvdev->flags & EVDEV_ABSOLUTE_EVENTS) @@ -1445,10 +1461,12 @@ EvdevInit(DeviceIntPtr device) pEvdev->flags &= ~EVDEV_ABSOLUTE_EVENTS; } else pEvdev->flags &= ~EVDEV_RELATIVE_EVENTS; + } if (pEvdev->flags & EVDEV_ABSOLUTE_EVENTS) - EvdevAddAbsClass(device); + if (EvdevAddAbsClass(device) != Success) + return !Success; #ifdef HAVE_PROPERTIES /* We drop the return value, the only time we ever want the handlers to -- 1.6.2.2.479.g2aec