[Wayland-bugs] [Bug 99554] No horizontal scrolling with mouse

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=99554

--- Comment #3 from Peter Hutterer <peter.hutterer at who-t.net> ---
(In reply to Sergey Bugaev from comment #2)
> No, I never changed any settings. Are you saying that the software changes
> some settings inside the mouse itself, as opposed to OS/driver configuration?

yep, on many devices this is the case. google e.g. libratbag or solaar as
projects to do exactly that.

> You *can* tell the difference, at least for this very mouse model with its
> default configuration. As I've said, physical back and forward buttons map
> to BTN_SIDE and BTN_EXTRA, whereas the wheel maps to BTN_BACK/BTN_FORWARD.

oh, right. I misread that while looking at the evemu outupt only

> If other mice map back/forward buttons to BTN_BACK/BTN_FORWARD, then this
> sounds to be a candidate for its own HWDB field. On the other hand, let me
> mention once again that back/forward buttons do work for me now, so maybe
> BTN_SIDE & BTN_EXTRA *is* what other mice emit for back/forward buttons.

yes, it's an unfortunate naming. the kernel has side/extra before back/forward,
but most clients map buttons 4 and 5 (i.e. anything after LMR) to back/forward.
I should probably document this in libinput too, just in case...

back to the RAT7: any configuration where back/forward would be mapped to other
buttons? the thing with a hwdb is that it's not easily reversible, so by
putting one in place we'd break it for anyone using the software to reconfigure
the wheel. given these devices are gaming devices, that's assumed to be a large
percentage.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/wayland-bugs/attachments/20170130/4994037e/attachment.html>