Bug#547131: xserver-xorg-input-mouse: The ButtonMapping option does not work any more.

[Christophe Lohr <Christophe.Lohr@telecom-bretagne.eu>]

Julien Cristau a écrit :
> Peter Hutterer's blog
> (http://who-t.blogspot.com/2009/06/button-mapping-in-x.html) has a
> pretty good explanation of how button mapping works.  Hope this helps.
>   

This document is interesting, however I do not understand differencies
between solution for setting up a mapping at the "device level":
- in xorg.conf: Section "InputDevice" / Option "ButtonMapping" "3 2 1" +
Section "ServerLayout" / Option "AutoAddDevices" "false"
- with: xinput set-button-map <my_mouse> 3 2 1
- with: hal-set-property --udi <my_mouse> --key
input.x11_options.ButtonMapping --string '3 2 1'

Does it really occures at the same level?

For instance, if I configure the mapping into the xorg.conf, then
'xinput get-button-map' does not show the mapping.
If I configure the mapping into hal, then xinput get-button-map show the
mapping.

Another experiment while "transporting" the pointer from another X11
server via the x2x tool: this pointer is not affected by a mapping
configured within xorg.conf (of the "to session"), but buttons of this
x2x pointer are switched if I buttons of the usb mouse blugged on the
"to" session are swiched by xinput.

So, it's a little bit confusing.

Regards.
Christophe.