Re: Need scancode for mouse buttons
On Mon, Feb 14, 2011 at 20:14, Camaleón <noelamac@gmail.com> wrote:
>> Yes, both these tools need the scancodes or keycodes already, as they
>> rely on "button events". I don't yet have "button events" for this
>> device.
>
> Maybe I'm getting this wrong but I think you first need to instruct xorg
> about the real available buttons before you can get any response from the
> dead ones :-?
>
Yes, exactly, that's why I asked about scancodes in the OP. The
hardware must be sending some signal, if the buttons are to work at
all in Windows. I need to intercept that signal, i.e., the scancode.
> I wonder if there is any driver you need to load to tell the X server
> about this. AFAIK, "evdev" should automatically manage this.
>
Possibly, but I'm willing to go below the driver and work with the
actual hardware scancode. I've had to do this for my keyboard as well,
it's no big deal so long as the scancode is available.
> Weird... Google finds no single reference for that device. Is there any
> additonal information about the mouse at the Xorg log?
>
Sure:
✈ganymede:~$ grep -i mouse /var/log/Xorg.0.log
[ 15.197] (==) RADEON(0): Silken mouse enabled
[ 15.289] (II) Microsoft Natural® Ergonomic Keyboard 4000: Found 1
mouse buttons
[ 15.289] (II) Microsoft Natural® Ergonomic Keyboard 4000:
Configuring as mouse
[ 15.292] (II) config/udev: Adding input device MLK OX-1100
wireless Laser Mouse (/dev/input/event2)
[ 15.292] (**) MLK OX-1100 wireless Laser Mouse: Applying
InputClass "evdev pointer catchall"
[ 15.292] (**) MLK OX-1100 wireless Laser Mouse: Applying
InputClass "evdev keyboard catchall"
[ 15.292] (**) MLK OX-1100 wireless Laser Mouse: always reports core events
[ 15.292] (**) MLK OX-1100 wireless Laser Mouse: Device: "/dev/input/event2"
[ 15.300] (II) MLK OX-1100 wireless Laser Mouse: Found 9 mouse buttons
[ 15.300] (II) MLK OX-1100 wireless Laser Mouse: Found scroll wheel(s)
[ 15.300] (II) MLK OX-1100 wireless Laser Mouse: Found relative axes
[ 15.300] (II) MLK OX-1100 wireless Laser Mouse: Found x and y relative axes
[ 15.300] (II) MLK OX-1100 wireless Laser Mouse: Found absolute axes
[ 15.300] (II) MLK OX-1100 wireless Laser Mouse: Found keys
[ 15.300] (II) MLK OX-1100 wireless Laser Mouse: Configuring as mouse
[ 15.300] (II) MLK OX-1100 wireless Laser Mouse: Configuring as keyboard
[ 15.300] (**) MLK OX-1100 wireless Laser Mouse: YAxisMapping:
buttons 4 and 5
[ 15.300] (**) MLK OX-1100 wireless Laser Mouse:
EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout:
200
[ 15.300] (II) XINPUT: Adding extended input device "MLK OX-1100
wireless Laser Mouse" (type: KEYBOARD)
[ 15.301] (II) MLK OX-1100 wireless Laser Mouse: initialized for
relative axes.
[ 15.301] (WW) MLK OX-1100 wireless Laser Mouse: ignoring absolute axes.
[ 15.301] (II) config/udev: Adding input device MLK OX-1100
wireless Laser Mouse (/dev/input/mouse0)
>> However, 10 of the 12 buttons work, not just the 9 that it found. I've
>> tried to google a picture of the mouse, I see no info on Teac mice even
>> on the Teac website. The buttons are "zoom" buttons that I suppose are
>> activated by a Windows driver on the OS that the package states that it
>> "supports".
>
> Hum... by Googling around I've found some references to "xinput" but
> again, not sure if that utility could help here as I guess the first to
> achieve is a proper detection of the mouse buttons that are available:
> while the system cannot see the buttons it cannot map them to desired
> actions.
>
Yup.
--
Dotan Cohen
http://gibberish.co.il
http://what-is-what.com
Reply to: