on Sunday 29 October 2017 at 22:13, Daniel Jakots wrote: > On Sun, 29 Oct 2017 11:37:45 -0400, gwes <g...@oat.com> wrote: > > On 10/25/17 07:20, Cág wrote: > > > Natasha Kerensikova wrote: > > > > > >> it started as a bug report: it have a 5-button mouse with a wheel, > > >> even though I don't use much the buttons 4 and 5 (I think only for > > >> previous and next in firefox history). I recently switched to > > >> OpenBSD, and I was surprised to find these buttons cause > > >> scrolling, like the wheel. If this behavior is intended, the rest > > >> of this e-mail is moot. > > > > > > This isn't a bug apparently. Are the extra buttons recognised by > > > xev? If they are, remap them with xmodmap(1). If they aren't, well, > > > then it should be done by xf86-input-evdev or libinput. There's > > > been some work in FreeBSD, and the drivers are in ports, but > > > OpenBSD doesn't have them. > > I use a 4-button Logitech trackball mouse. It required remapping in > > xmodmap to make it work. > > Yes, xev showed enough information to see "button up" and "button > > down" events to use as input to xmodmap. > > Do you mind sharing your configuration?
I'm also interested in it, because my analysis led me to believe that xmodmap(1) is only able to do the equivalent of a dynamic change to the X configuration "ButtonMapping", which is used after the confusion between physical buttons 4/5 and the wheel, so they cannot be distinguished unless I'm mistaken (or unless there is some non-default "ZAxisMapping" involved, which unless I'm mistaken cannot be changed by xmodmap(1) and is constant after loading of xf86-input-ws). I would welcome being corrected if I'm wrong, especially after being told that the confusion is a feature. Natasha
