On Tue, 21 May 2024, joelp%sdf.org@localhost wrote:
2. See if it has `Option "EmulateWheel"' and/or `Option "EmulateWheelButton"' is set if the input driver is "mouse"?I tried those options and I could not get this to change the behavior.
Those should, actually, _not_ be set ;-)
When I created an xorg.conf, I used "wsmouse".
I meant the Xorg input driver ("mouse" or "ws" on NetBSD), not the device the
driver is using.
Can you post your Xorg.0.log, that should make things clear.
Oh nice, Iain also suggested xev. I can now confirm that simply moving the mouse causes multiple events. I noticed that the scroll action on the mouse does not produce any events.
Hmm. Simply moving the mouse should generate only MotionNotify events; and using the mouse-wheel only should generate only ButtonPress & ButtonRelease events, typically button 5 for a down-scroll & button 4 for up-scroll.
MotionNotify event, serial 25, synthetic NO, window 0xa00001, root 0x3a6, subw 0x0, time 11141293, (171,138), root:(329,315), state 0x0, is_hint 0, same_screen YES ButtonPress event, serial 25, synthetic NO, window 0xa00001, root 0x3a6, subw 0x0, time 11141293, (171,138), root:(329,315), state 0x0, button 5, same_screen YES ButtonRelease event, serial 25, synthetic NO, window 0xa00001, root 0x3a6, subw 0x0, time 11141293, (171,138), root:(329,315), state 0x1000, button 5, same_screen YES
So, that's both motion and down-scroll buttons. Can you also show the output of: xinput list and, xinput list-props <ID-no.-of-mouse> -RVP