You are not logged in.
Pages: 1
Hi guys,
I'm trying to get my mx1000 to work properly. while doing this Im using the xev to number my keys. I got keynumbers from 1 .. 7 but it's a 12 button mouse. three of the buttons have the same number which I guess there's nothing to do about?
What I'm missing is an output from my tilt-wheel. xev do not react on this, how come?
The relevant part of xorg.conf
Section "InputDevice"
Identifier "Logitech MX1000"
Driver "mouse"
Option "Buttons" "12"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
Option "ButtonMapping" "1 2 3 6 7"
Option "Resolution" "800"
EndSection
Offline
I'm root. if you see me smile, you'd better have a backup!!
Offline
Thanks, but when I run the xev I get the following. Note that on button 11-14 I get two clicks most of the time.
Mouse Button xev Button Number Current Fn Desired Fn
----------------------------------------------------------------------------
Left Click 1 Left Click Left Click
Scroll Wheel Center Click 2 Center Click Center Click
Right Click 3 Right Click Right Click
Scroll Fwd Roll 4 Scroll Fwd Scroll Fwd
Scroll Back Roll 5 Scroll Back Scroll Back
Back Thumb Button 8 None Browser Back
Forward Thumb Button 9 None Browser Fwd
Center Thumb Button 10 None None
Scroll Fwd Button 11 & 4 Scroll Fwd None
Scroll Back Button 12 & 5 Scroll Back None
Left Horizontal Scroll 13 & 7 Browser Back Left Scroll
Right Horizontal Scroll 14 & 6 Browser Fwd Right Scroll
Can I avoid this in any wau?
Offline
Allright,
I've done the following to fix this, but it doesn't work completely as it should:
First I redefine most of the buttons;
#! /bin/sh
xmodmap -e "pointer = 1 2 3 4 5 10 11 12 13 14 15 16 17 18 19 20 6 7 8 9"
/usr/bin/xbindkeys
this leaves the scrolling and clicking as it were and lets me redefine the rest of the buttons. Notice, I can't use button 6 and 7 since these are for browsing in firefox. 8 and 9 are just for convenience since I would like to define the buttons from ten and up
.xbindkeysrc:
"/usr/bin/xvkbd -xsendevent -text "\[Alt_L]\[Left]""
m:0x0 + b:12
"/usr/bin/xvkbd -xsendevent -text "\[Alt_L]\[Right]""
m:0x0 + b:13
"/usr/bin/xvkbd -xsendevent -text "\[Up]""
m:0x0 + b:15
"/usr/bin/xvkbd -xsendevent -text "\[Down]""
m:0x0 + b:16
#pushing buttons 13 and 14 gives two events But dont work properly
"/usr/bin/xvkbd -xsendevent -text "\[Left]""
m:0x0 + b:11
"/usr/bin/xvkbd -xsendevent -text "\[Left]""
m:0x0 + b:17
"/usr/bin/xvkbd -xsendevent -text "\[Right]""
m:0x0 + b:10
"/usr/bin/xvkbd -xsendevent -text "\[Right]""
m:0x0 + b:18
The two events start by a single button 18 or 17 and if I hold the button I get a continuous signal of tens and elevens respectively.
The problem is that the computer takes the tens and elevens as left clicks. So for example, if I zoom in on a picture and try to scroll horizontally this makes me zoom in and out lots of times.
The function is not that neccesary, so I might find some other thing to use it for, but feel free to guess
Offline
I don't have time right now to fully comment on your posts, especially in regard to the deviations you have taken from the Wiki article, but I will comment on the "extra" clicks you are encountering.
I believe the clicks are normal, though irritating or potentially problematic, for the MX1000. They have to do with whether or not cruise control is enabled or disabled (enabled: buttons generate multiple button events; disabled: buttons generate single-button events as one might expect). The Wiki article does not mention this, perhaps because it went unnoticed in xev and / or perhaps because the author was using applications where the extra button events were not generating any unwanted activity.
As you have noted, the extra events may become problematic when using certain applications. For example, with FireFox, I believe, the extra clicks do not generate any response, while Mozilla interprets the extra clicks as "Left" button events. The latter can be annoying at minimum.
It may be possible to suppress the ButtonPress event of any key desired by using this code in your '~/.xbindkeysrc' file:
"NoCommand"
m:0x10 + b:11
"NoCommand"
m:0x10 + b:12
Change the button numbers in the code as it fits your situation.
Offline
When I try to map buttons of my MX1000 I get the following error
[zbyszek@barca ~]$ xev | grep -i button
bash: xev: command not found
Anyone know what package I'm missing? My system is x86_64 KDE 4.3.0.
"... being a Linux user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed."
MSI Raider GE78HX 13VI-032PL
Offline
Seems no one has ever had similar problem...
"... being a Linux user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed."
MSI Raider GE78HX 13VI-032PL
Offline
Seems no one has ever had similar problem...
Probably cause they all had installed the package xorg-utils.
Scientia et sapientia patrimonium humanitatis sunt.
Offline
At last! Thanks
"... being a Linux user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed."
MSI Raider GE78HX 13VI-032PL
Offline
Try: "grep -i "mouse" /var/log/Xorg.0.log" to find exactly how the Xserver is seeing the mouse. My MX-700 wireless is at a different location; the following is from my M-500 corded mouse running through a PS2 adapter. Tilt maps to buttons 6 and 7 on this mouse. The forward and backward buttons map to buttons 8 and 9.
Xorg ignores my mouse settings in xorg.conf because I didn't set the option "AllowEmptyInput" to "False" but the tilt wheel works. You can see from the sixth line that PolicyKit (if you're using HAL) can affect your mouse too.
(**) |-->Input Device "Mouse0"
(**) Option "AllowMouseOpenFail" "true"
(WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
(WW) Disabling Mouse0
(==) NVIDIA(0): Silken mouse enabled
(II) config/hal: Adding input device ImExPS/2 Logitech Explorer Mouse
(**) ImExPS/2 Logitech Explorer Mouse: always reports core events
(**) ImExPS/2 Logitech Explorer Mouse: Device: "/dev/input/event6"
(II) ImExPS/2 Logitech Explorer Mouse: Found 9 mouse buttons
(II) ImExPS/2 Logitech Explorer Mouse: Found x and y relative axes
(II) ImExPS/2 Logitech Explorer Mouse: Found scroll wheel(s)
(II) ImExPS/2 Logitech Explorer Mouse: Configuring as mouse
(**) ImExPS/2 Logitech Explorer Mouse: YAxisMapping: buttons 4 and 5
(**) ImExPS/2 Logitech Explorer Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "ImExPS/2 Logitech Explorer Mouse" (type: MOUSE)
(**) ImExPS/2 Logitech Explorer Mouse: (accel) keeping acceleration scheme 1
(**) ImExPS/2 Logitech Explorer Mouse: (accel) filter chain progression: 2.00
(**) ImExPS/2 Logitech Explorer Mouse: (accel) filter stage 0: 20.00 ms
(**) ImExPS/2 Logitech Explorer Mouse: (accel) set acceleration profile 0
(II) ImExPS/2 Logitech Explorer Mouse: initialized for relative axes.
Offline
Pages: 1