On Mon, 14 Feb 2011 19:01:21 +0200, Dotan Cohen wrote:
> On Mon, Feb 14, 2011 at 18:42, Camaleón wrote:
>> Xinput or Imwheel? But it seems to me a bit overwhelming as both look
>> like tools for directly setting up the mouse by mapping buttons with
>> actions :-?
>>
>>
> 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 :-?
I wonder if there is any driver you need to load to tell the X server
about this. AFAIK, "evdev" should automatically manage this.
>> BTW, what is the brand and model of your device and how it is being
>> detected by Xorg? ("grep -i mouse /var/log/Xorg.0.log" will give you
>> some hints).
>>
>>
> Interesting, this is the mouse:
> [ 9522.797] (II) MLK OX-1100 wireless Laser Mouse: Found 9 mouse
> buttons
Weird... Google finds no single reference for that device. Is there any
additonal information about the mouse at the Xorg log?
> 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.
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.02.14.18.14...@gmail.com
