Re: Logitech MX 700 Setup

From: Steffen Kluge (kluge_at_dotnet.org)
Date: 08/18/03 

Date: Mon, 18 Aug 2003 15:05:16 GMT

According to Trevor MacPhail <trevor.macphail.lists@shaw.ca>:
>Using xev doesnt turn up anything for the application switcher button and

In a different thread I read the other day that X11 only knows 5
buttons by default. This was substantiated by #define's in header
file /usr/X11R6/include/X11/X.h, near line 260-ish.

Those #define's aren't referenced in any other header file. I
don't know whether they have any bearing at all.

It certainly seems to be the case that X11 supports more than 5
buttons. For a test, I just stole my wife's Logitech MouseMan
Optical Dual-sensor. It has a wheel and one extra button on the
side. The following configuration made xev recognise all button
clicks and wheel movements as separate events:

  Section "InputDevice"
          Identifier "Mouse0"
          Driver "mouse"
          Option "Device" "/dev/mouse"
          Option "Protocol" "ExplorerPS/2"
          Option "Buttons" "6"
          Option "ZAxisMapping" "5 6"
  EndSection

This config had xev report the wheel scrolling forward as button
5, backward as button 6 and the side button as button 4. In
xterm, the side button was scrolling pages up and forward wheel
scroll caused scrolling down. For some reason, ZAxisMapping wants
to be set to the last two buttons. Setting it to "4 5" made the
6th button disappear. So I used "5 6" and said:

$ xmodmap -e "pointer = 1 2 3 6 4 5"

This made scrolling the wheel forward/backward appear as buttons
4 and 5 (as expected by most apps) and made scrolling in xterm
work as expected. The side button was recognised as button 6.
Now, all you need is a window manager with the smarts to bind
actions to button 6 events.

BTW, the mouse was connected via USB, and /dev/mouse was a link
to /dev/input/mice.

What does your XF86Config mouse section look like?

>turns up the cruise buttons being the same as scroll up/down. In windows
>the cruise buttons can be configured to act differently than the scroll
>wheel.

Try this again once you got xev to report all buttons as separate
events.

My son will be getting an MX700 shortly, maybe I can steal it for
a while and give it a bit of a play-around. I'm pretty sure one
can get all those buttons to work. On the other hand, I was
always a bit suspicious about mice covered in buttons - one has
to be careful when grabbing the mouse... :)

Cheers
Steffen.

Relevant Pages

  • RE: Trackball, extra buttons, and X - Ive lost something
    ... scrolling without annoying popup menus. ... > should keep your wheel working. ... > Fvwm 2.4.19 built with imlib support from the ports. ... > To unsubscribe, send any mail to ...
    (freebsd-questions)
  • Re: Trackball, extra buttons, and X - Ive lost something
    ... But I kept the ZAxisMapping at 6 and 7. ... scrolling without annoying popup menus. ... I'll try switching the ZAxisMapping and the xmodmap to see if I can ... > The only problem is that it has 5 buttons including the button wheel. ...
    (freebsd-questions)
  • Trackball, extra buttons, and X - Ive lost something
    ... Microsoft thumbball thingys. ... The only problem is that it has 5 buttons including the button wheel. ... I get the Fvwm Builtin menu. ... Now I can't seem to get scrolling back. ...
    (freebsd-questions)
  • Re: mouse wheel problems
    ... problem is that scrolling with the wheel is causing strange behavior. ... My issue is with a Belkin KVM and Ubuntu Dapper or FC5. ...
    (Fedora)
  • Re: Xorg and mice
    ... (I'm not interested in using xmodmap ... I tried xev, but it did nothing at all. ... pressing the wheel to the right does not. ...
    (freebsd-questions)