Horizontal scroll on MX1000 sends click event as well. [SOLVED]

Aziere · 2007-03-24 21:05:33

As in the topic, I'm having problems with the horizontal scroll sending regular click events to apps as well as the scrolling, making the function pretty unusable. All my other keys work exactly as they should.

As for my configuration, I'm running evdev, and I have "pointer = 1 2 3 4 5 7 6 8 9 10 11 12" in xmodmap.
Ive tried changing the input with both imwheel and xbindkeys, but none of them would intercept the horizontal scroll. (Strange though, since it works fine with the other buttons)

I don't know what else I can do. Is it just a lost cause?

P.S: I know it's not app dependent, because I have tried it with every application I have.

Last edited by Aziere (2007-03-25 16:05:48)

vacant · 2007-03-24 21:54:16

Do you still need xmodmap these days? e.g. for my 5 button mouse (i.e. 4 buttons + scroll wheel)

    Driver         "mouse"
    Option         "Protocol" "ExplorerPS/2"
    Option         "Device" "/dev/input/mice"
    Option         "Buttons" "5"
    Option         "ZAxisMapping" "4 5"
    Option         "ButtonMapping" "1 2 3 6 7"

and what does xev report?

Last edited by vacant (2007-03-24 21:54:58)

Aziere · 2007-03-25 09:38:02

I prefer evdev because I can't seem to get the thumb buttons to work without it.

As for xev:

ButtonPress event, serial 31, synthetic NO, window 0x1e00001,
    root 0x155, subw 0x1e00002, time 1058103, (48,34), root:(471,325),
    state 0x10, button 13, same_screen YES

EnterNotify event, serial 31, synthetic NO, window 0x1e00001,
    root 0x155, subw 0x0, time 1058103, (48,34), root:(471,325),
    mode NotifyGrab, detail NotifyInferior, same_screen YES,
    focus YES, state 16

KeymapNotify event, serial 31, synthetic NO, window 0x0,
    keys:  85  0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

ButtonPress event, serial 31, synthetic NO, window 0x1e00001,
    root 0x155, subw 0x1e00002, time 1058127, (48,34), root:(471,325),
    state 0x10, button 6, same_screen YES

ButtonRelease event, serial 31, synthetic NO, window 0x1e00001,
    root 0x155, subw 0x1e00002, time 1058127, (48,34), root:(471,325),
    state 0x10, button 6, same_screen YES

LeaveNotify event, serial 31, synthetic NO, window 0x1e00001,
    root 0x155, subw 0x0, time 1058127, (48,34), root:(471,325),
    mode NotifyUngrab, detail NotifyInferior, same_screen YES,
    focus YES, state 16

ButtonRelease event, serial 31, synthetic NO, window 0x1e00001,
    root 0x155, subw 0x1e00002, time 1058263, (48,34), root:(471,325),
    state 0x10, button 13, same_screen YES



ButtonPress event, serial 31, synthetic NO, window 0x1e00001,
    root 0x155, subw 0x1e00002, time 1127089, (43,37), root:(466,328),
    state 0x10, button 14, same_screen YES

EnterNotify event, serial 31, synthetic NO, window 0x1e00001,
    root 0x155, subw 0x0, time 1127089, (43,37), root:(466,328),
    mode NotifyGrab, detail NotifyInferior, same_screen YES,
    focus YES, state 16

KeymapNotify event, serial 31, synthetic NO, window 0x0,
    keys:  38  0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

ButtonPress event, serial 31, synthetic NO, window 0x1e00001,
    root 0x155, subw 0x1e00002, time 1127105, (43,37), root:(466,328),
    state 0x10, button 7, same_screen YES

ButtonRelease event, serial 31, synthetic NO, window 0x1e00001,
    root 0x155, subw 0x1e00002, time 1127105, (43,37), root:(466,328),
    state 0x10, button 7, same_screen YES

LeaveNotify event, serial 31, synthetic NO, window 0x1e00001,
    root 0x155, subw 0x0, time 1127105, (43,37), root:(466,328),
    mode NotifyUngrab, detail NotifyInferior, same_screen YES,
    focus YES, state 16

ButtonRelease event, serial 31, synthetic NO, window 0x1e00001,
    root 0x155, subw 0x1e00002, time 1127489, (43,37), root:(466,328),
    state 0x10, button 14, same_screen YES

Seems pretty obvious what the problem is. It sends button 13/14 as input first, the continues with 6/7 which is the scroll. So what do I do to fix that?

qlus · 2007-03-25 10:25:07

Have you tried just the evdev without xmodmap?
My mx700 works fine using only evdev

    Identifier     "Evdev Mouse"
    Driver          "evdev"
    Option         "Name" "Logitech USB Receiver"

Aziere · 2007-03-25 16:05:33

The solution was in front of me all the time. Thanks to vacant for reminding me of xev.
I just disabled button 13 and 14 through xbindkeys, and now it works as it should.

Marking topic as solved.

Arch Linux

#1 2007-03-24 21:05:33

Horizontal scroll on MX1000 sends click event as well. [SOLVED]

#2 2007-03-24 21:54:16

Re: Horizontal scroll on MX1000 sends click event as well. [SOLVED]

#3 2007-03-25 09:38:02

Re: Horizontal scroll on MX1000 sends click event as well. [SOLVED]

#4 2007-03-25 10:25:07

Re: Horizontal scroll on MX1000 sends click event as well. [SOLVED]

#5 2007-03-25 16:05:33

Re: Horizontal scroll on MX1000 sends click event as well. [SOLVED]

Board footer