<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - No horizontal scrolling with mouse" href="https://bugs.freedesktop.org/show_bug.cgi?id=99554#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - No horizontal scrolling with mouse" href="https://bugs.freedesktop.org/show_bug.cgi?id=99554">bug 99554</a> from <a class="email" href="mailto:bugaevc@gmail.com" title="Sergey Bugaev <bugaevc@gmail.com>"> Sergey Bugaev</a> <pre>> this device can be configured with the custom software (under windows), right? Yes > If so, did you change the wheel settings at all? 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? > Unfortunately this isn't something we can work around in libinput because doing so would mean you lose the back/forward buttons. we can't tell the difference between a real button press and a mouse wheel, the look exactly the same. 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. 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. Hope that this is not too confusing...</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>