https://bugzilla.novell.com/show_bug.cgi?id=227458 mhopf@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |INVALID ------- Comment #13 from mhopf@novell.com 2006-12-19 07:11 MST ------- (In reply to comment #9)
I've commented the pointer=... in my /etc/X11/Xmodmap that I've added because of a bad assumption (In fact it was the line I've added on my 10.0 to make my mouse working). Without this line xev shows better result:
This was no bad assumption, this was the only possible workaround before 10.1. I think this was mentioned in the release notes, if not, that certainly is a bug :-P
little top button = button 1
We can't do nothing about that, that's PS/2 magic...
Now, just by curiosity, I started my 10.0 again, on it, without any Xmodmap modification the results were: mouse wheel up = nothing mouse wheel down = nothing
You would need a 'Option "ZAxisMapping" "4 5"' for that - this is now the default value. You had "7 8" - which is quite odd.
extra left = button 4 extra right = button 5
No button reordering by the driver in 10.0. The ButtonMapping option is new.
I don't really understand how all that works, but at that time I had to add this line to my /etc/X11/Xmodmap:
10.0: Physical button # 1-5 -> Logical # 1-5 -> user # 1,2,3,6,7 Wheel -> Logical # 7,8 -> user # 4,5 The last change was done by the xmodmap line - necessary, because the driver couldn't change buttons (physical == logical). Usually, wheel was mapped to 6,7 and "pointer = 1 2 3 6 7 4 5" was used. So your config was a bit odd, too.
Thank you for your help, and sorry for this waste of time. I shouldn't have copied my old conf file to this 10.2 so fast ... In fact I didn't knew that Xmodmap could modify the result of Xev (thought it was something returned by the kernel, something immutable), so when I saw no event for one button, I thought it was a "bug" ...
Xev shows events delivered to user programs. You can watch kernel events by using evtest. (In reply to comment #10)
Maybe a stupid question but are there any sax2 changes needed. According to comment #8 sax creates a valid configuration, according to comment #9 ButtonMapping is missing to make you happy ? :)
Stupid in the sense that the answer is trivial: no ;-) (In reply to comment #11)
But, the two extra buttons only act as "left-click". Then I can add the ButtonMapping in xorg.conf to make them work as "back/forward", or add a line in Xmodmap (which I don't remember now).
No, they act as button #8 and #9, and there is no default action in most programs. However, several you can configure to your needs. As we need buttons #6 and #7 free for a horizontal wheel, this is about all we can do for a general configuration. The user is always free to change as he likes, of course.
My understanding (which is more "intuition" based on the many tests I've made) is that "back/forward" are by default expected/mapped to "button6" and "button7", that's why I added:
You only get back/forward because that are the default actions for the horizontal wheel ;-) Try them in a panel with two scrollbars, they probably will scroll left/right. Closing this as INVALID, as it is in fact not a bug :-P -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.