[PATCH] mi: ensure chained button mappings from SD -> MD (#19282)

[Thomas Jaeger]

> that's not good. I think there's historical reason to do so, but by now the
> drivers should just let button mapping to the DIX (unless they need something
> really special). xsetwacom would be better off using libXi's
> XSetDeviceButtonMapping.

I've got a problem now, though.  Apparently some wacom devices have
various types of scroll wheels, and they are all mapped to button 4/5.
I initially thought (because of a comment in ProcSetPointerMapping) that
the restriction that no two physical buttons can be mapped to the same
logical button was lifted for extended devices, but looking at the spec,
this is not the case.  The other thing is that the wacom driver allows
for buttons to mapped to a double click, which once again needs a
duplicate assignment.  On older X servers, the situation is even worse
because any XSetPointerMapping() call will override our settings.

Because of all this, I'm inclined to just leave the device button map
alone and handle all the remapping in the driver (see the attached patch).

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Don-t-touch-the-button-map.patch
Type: text/x-patch
Size: 2473 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg/attachments/20090109/87a2af68/attachment.bin>