Comment 6 for bug 325581

Revision history for this message
Douglas Henke (henke-insync) wrote :

Here are the comments that I meant to apply to the above patch; they somehow didn't "take":

Okay, got it. The attached patch makes my Kensington pocket mouse work again, and doesn't break any of the other input devices I have sitting around. (Caveat: I have no touchscreens.)

The basic ideas are:
   1) If a device says it has relative axes, then any claim that it also has absolute axes is a lie.

   2) A device can only be one of touchscreen, mouse or keyboard. If it looks like several, then
       take the first thing from that list it claims to be.

Bear in mind I haven't ever seen the usbhid, hald or evdev code before a couple days ago, so please apply vigorous quality control before pushing this into anything that'll be used by somebody's grandmother!