[opensuse] Configuring a four-button trackball
I have a new Kensington "Expert Mouse" trackball -- four buttons and a scroll ring. openSuSE v11.3 detects the device, and the two upper buttons appear to be configured with actions (but I haven't yet figured out exactly what they are doing). I would like to configure the device. I have searched the net for information on how to do this, but have not foud anything helpful because, among other things, configuration is different in v11.3 from earlier versions. Here is the content of Xorg.0.log related to the mouse: {{{{{ $ grep -i mouse /var/log/Xorg.0.log [ 12.497] (==) intel(0): Silken mouse enabled [ 12.694] (II) config/udev: Adding input device Kensington Kensington Expert Mouse (/dev/input/event3) [ 12.694] (**) Kensington Kensington Expert Mouse: Applying InputClass "evdev pointer catchall" [ 12.694] (**) Kensington Kensington Expert Mouse: always reports core events [ 12.694] (**) Kensington Kensington Expert Mouse: Device: "/dev/input/event3" [ 12.697] (II) Kensington Kensington Expert Mouse: Found 8 mouse buttons [ 12.697] (II) Kensington Kensington Expert Mouse: Found scroll wheel(s) [ 12.697] (II) Kensington Kensington Expert Mouse: Found relative axes [ 12.697] (II) Kensington Kensington Expert Mouse: Found x and y relative axes [ 12.697] (II) Kensington Kensington Expert Mouse: Configuring as mouse [ 12.697] (**) Kensington Kensington Expert Mouse: YAxisMapping: buttons 4 and 5 [ 12.697] (**) Kensington Kensington Expert Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 [ 12.697] (II) XINPUT: Adding extended input device "Kensington Kensington Expert Mouse" (type: MOUSE) [ 12.697] (**) Kensington Kensington Expert Mouse: (accel) keeping acceleration scheme 1 [ 12.697] (**) Kensington Kensington Expert Mouse: (accel) acceleration profile 0 [ 12.697] (**) Kensington Kensington Expert Mouse: (accel) acceleration factor: 2.000 [ 12.697] (**) Kensington Kensington Expert Mouse: (accel) acceleration threshold: 4 [ 12.697] (II) Kensington Kensington Expert Mouse: initialized for relative axes. [ 12.697] (II) config/udev: Adding input device Kensington Kensington Expert Mouse (/dev/input/mouse0) $ }}}}} Being a log, of course, it doesn't tell me how to change anything. Nor do I know which button has what number. I see that, although oS has found the scroll ring, it claims to be configuring a button to emulate it. Whatever the buttons are doing has no noticable connection with such emulation. Can someone tell me where to find the needed information? -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 14 Oct 2010, Stan Goodman wrote: ...
Nor do I know which button has what number.
I see that, although oS has found the scroll ring, it claims to be configuring a button to emulate it. Whatever the buttons are doing has no noticable connection with such emulation.
Can someone tell me where to find the needed information?
If you run xev from a terminal window you can discover what events each control generates -- " '... but there is so much else behind what I say. It makes itself known to me so slowly, so incompletely! ...' " -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dylan said the following on 10/14/2010 05:57 AM:
On Thursday 14 Oct 2010, Stan Goodman wrote: ...
Nor do I know which button has what number.
I see that, although oS has found the scroll ring, it claims to be configuring a button to emulate it. Whatever the buttons are doing has no noticable connection with such emulation.
Can someone tell me where to find the needed information?
If you run xev from a terminal window you can discover what events each control generates
And how about mapping buttons to actions? I have a logitech mouse that has in effect 10 buttons acording to xev :-) Beside the scrool wheel thre are two buttons. One give #4 when pressed and #11 when released The other #5 and #12 How would I map those? -- "The abundant life does not come to those who have had a lot of obstacles removed from their path by others. It develops from within and is rooted in strong mental and moral fiber." -- William Mather Lewis -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 14 October 2010 13:29:47 Anton Aylward wrote:
And how about mapping buttons to actions?
I have a logitech mouse that has in effect 10 buttons acording to xev :-)
Beside the scrool wheel thre are two buttons. One give #4 when pressed and #11 when released The other #5 and #12
How would I map those?
Use xinput set-button-map (see manpage) to discover the correct button mapping, then make the mapping permanent using a Section matching your mosue with MatchVendor, MatchProduct lines and an "Option "ButtonMapping" "1 3 2 4 6 5"" in /etc/X11/xorg.conf/d/11-mouse.conf. Then report a bug vs our XOrg with the addendum so everyone else profits. HTH Will -- Will Stephenson, openSUSE Team SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Will Stephenson said the following on 10/14/2010 07:57 AM:
On Thursday 14 October 2010 13:29:47 Anton Aylward wrote:
And how about mapping buttons to actions?
I have a logitech mouse that has in effect 10 buttons acording to xev :-)
Beside the scrool wheel thre are two buttons. One give #4 when pressed and #11 when released The other #5 and #12
How would I map those?
Use xinput set-button-map (see manpage) to discover the correct button mapping, then make the mapping permanent using a Section matching your mosue with MatchVendor, MatchProduct lines and an "Option "ButtonMapping" "1 3 2 4 6 5"" in /etc/X11/xorg.conf/d/11-mouse.conf. Then report a bug vs our XOrg with the addendum so everyone else profits.
Ah. No, that's not what I meant by Map" xinput "maps" physical button events to logical button events. What was 8 is now 5 ... and so on. What I meant was more like In thunderbird, the front thumb key brings up the message-level menu ... In firefox .... In OpenOffice ... and so on. Presumably there is some consistency like page up/down ... -- If you are using Windows 2000, there is no chance that DES is your weak link. The only justification for using 3DES is that it is cheap. -- William Hugh Murray, CISSP -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 13:29:47 on Thursday Thursday 14 October 2010, Anton Aylward
Dylan said the following on 10/14/2010 05:57 AM:
On Thursday 14 Oct 2010, Stan Goodman wrote: ...
Nor do I know which button has what number.
I see that, although oS has found the scroll ring, it claims to be configuring a button to emulate it. Whatever the buttons are doing has no noticable connection with such emulation.
Can someone tell me where to find the needed information?
If you run xev from a terminal window you can discover what events each control generates
And how about mapping buttons to actions?
I have a logitech mouse that has in effect 10 buttons acording to xev :-)
Beside the scrool wheel thre are two buttons. One give #4 when pressed and #11 when released The other #5 and #12
How would I map those?
I have no idea. As you can see from my note of a few minutes ago, I have found what appears to be the right configuration file, but I don't know enough to use it, even when I compare my trackball with the others for which Sections exist. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 11:57:26 on Thursday Thursday 14 October 2010, Dylan
On Thursday 14 Oct 2010, Stan Goodman wrote: ...
Nor do
I know which button has what number.
I see that, although oS has found the scroll ring, it claims to be configuring a button to emulate it. Whatever the buttons are doing has no noticable connection with such emulation.
Can someone tell me where to find the needed information?
If you run xev from a terminal window you can discover what events each control generates
I see that, for example, button 4 is said to emulate the scroll ring, but I already knew that. Since none of the buttons produce such an action, I still don't know which is button 4. In any case, what I want is a way to configure the two upper buttons, which this display doesn't touch on. Formerly ("Way back in naught eight"), a device like a mouse would have been configured in xorg.conf, and that is why the web is chock-a-block with references to that file for configuration. But there is no such file in v11.3. But a few minutes ago, I found its successor: /etc/X11/xorg.conf.d/11-mouse.conf; this is what it contains: {{{{{ Section "InputClass" # 046d:c50e # 046d:c501 Identifier "Logitech Trackball" MatchVendor "Logitech, Inc." MatchProduct "MX-1000 Cordless Mouse Receiver|Cordless Mouse Receiver" MatchIsPointer "on" Driver "evdev" Option "Buttons" "8" Option "EmulateWheel" "on" Option "EmulateWheelButton" "8" Option "YAxisMapping" "4 5" Option "XAxisMapping" "6 7" EndSection Section "InputClass" # 046d:c521 Identifier "Logitech Multibutton Mouse" MatchVendor "Logitech, Inc." MatchProduct "MX620 Laser Cordless Mouse" MatchIsPointer "on" Driver "evdev" Option "HWHEELRelativeAxisButtons" "7 6" EndSection Section "InputClass" # 045e:0095 Identifier "Microsoft IntelliMouse Explorer" MatchVendor "Microsoft Corp." MatchProduct "IntelliMouse Explorer 4.0 (IntelliPoint)" MatchIsPointer "on" Driver "evdev" Option "HWHEELRelativeAxisButtons" "7 6" EndSection Section "InputClass" # 0210:0003 Identifier "0210:0003" MatchVendor "0210" MatchProduct "0003" MatchIsPointer "on" Driver "evdev" Option "EmulateWheel" "on" Option "EmulateWheelButton" "2" EndSection Section "InputClass" # 0002:000a Identifier "0002:000a" MatchVendor "0002" MatchProduct "000a" MatchIsPointer "on" Driver "evdev" Option "EmulateWheel" "on" Option "EmulateWheelButton" "2" EndSection Section "InputClass" # 04b3:300f Identifier "IBM 300f" MatchVendor "IBM Corp." MatchProduct "300f" MatchIsPointer "on" Driver "evdev" Option "EmulateWheel" "on" Option "EmulateWheelButton" "2" EndSection Section "InputClass" # Novell Bug #597214 Identifier "IBM TPPS/2 TrackPoint" MatchProduct "TPPS/2 IBM TrackPoint" MatchIsPointer "on" Driver "evdev" Option "EmulateWheel" "on" Option "EmulateWheelButton" "2" Option "YAxisMapping" "4 5" Option "XAxisMapping" "6 7" Option "Emulate3Buttons" "on" Option "EmulateWheelTimeout" "200" EndSection Section "InputClass" # 03f0:1126 Identifier "HP 1126" MatchVendor "Hewlett-Packard" MatchProduct "1126" MatchIsPointer "on" Driver "evdev" Option "MinX" "0" Option "MaxX" "3000" Option "MinY" "0" Option "MaxY" "3000" EndSection }}}}} There are sections for several varieties of mice (mouses?), but none for Kensington Expert Mouse, which is probably the reason that neither of the upper buttons emulates the scroll ring as it is reputed to do. I am assuming that this file is the place to work on configuration/mapping, but it seems to be very variable, with different sections even employing different terminology. I also deduce that Button 4 is not one of the upper ones but one of the basic two. And it is not easy to understand the meaning of some of the various options and other elements. Kensington Support is of no help, being devotees of "The One OS". If someone has made a Section for this trackball, or even for an older Expert Mouse model, I would very much like to compare notes, which potentially would save me a lot of cut and try experimentation and a lot of time. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Anton Aylward -
Dylan -
Stan Goodman -
Will Stephenson