[Wayland-bugs] [Bug 106435] Enable middle-button-drag coexisting with scroll emulation

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue May 8 04:34:15 UTC 2018


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

            Bug ID: 106435
           Summary: Enable middle-button-drag coexisting with scroll
                    emulation
           Product: Wayland
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: medium
         Component: libinput
          Assignee: wayland-bugs at lists.freedesktop.org
          Reporter: john+bugs_freedesktop_org at daaave.org

I have a Trackpoint mouse ("eraser mouse") and when scroll wheel emulation is
enabled there's no way to do a middle-button-drag, because as soon as you hold
down the middle mouse button, it activates the scroll wheel emulation.

The thought I had, and I admit this is hacky and I'm open to suggestions, was
that if you hold the middle mouse button down for a threshold amount of time
without moving the pointer, it would switch back from scroll wheel emulation to
normal behaviour (where the middle button is acting like a middle button
again).  So you can do a middle-button-drag, you just have to hold the mouse
button down for say 1 second before you can start dragging.  Not perfect, but
certainly better than not ever being able to do it at all.

I'd say this functionality would probably require two new configurable values:

1. The amount of time (in milliseconds) you have to hold the middle button down
(or both buttons down, if it's a two-button setup where the middle button
itself is being emulated)
2. The distance the mouse is allowed to move during the delay without
triggering scroll emulation

In other words, if the settings above were "1000 ms" and "10 pixels", then
you'd have to hold the button for one second and keep the pointer within a
10-pixel radius to initiate a middle-button-drag.

There's also a related question of whether the user should be notified that the
operational switch has occurred (and if so, how)?  Personally I'm fine with no
notification and just doing it by muscle memory, but I'm sure I'd be happy with
other approaches as well.

-- 
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/20180508/3829e7a1/attachment.html>


More information about the wayland-bugs mailing list