[Wayland-bugs] [Bug 89274] libinput ignores finger distance when emulating second button
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Feb 26 23:18:45 PST 2015
https://bugs.freedesktop.org/show_bug.cgi?id=89274
Giovanni Campagna <scampa.giovanni at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |scampa.giovanni at gmail.com
--- Comment #3 from Giovanni Campagna <scampa.giovanni at gmail.com> ---
I think this should be reevaluated.
I'll try to explain. I come from years using a previous laptop with a touchpad
without working multitouch, so I'm used to clicking using physical buttons.
In practice, this translated to using the middle finger to move the pointer,
and the index finger for primary click.
On a clickpad, this is also natural: to click, I lift the middle finger and
click with the index, and the hand movement is roughly the same on the two
touchpads (the old one was quite small, so physical buttons were in reach).
To drag, this translates also naturally: just don't lift the index finger, put
the middle finger back and move the mouse.
On the other hand, your proposed behavior would require me to click using the
middle finger, and then keep moving it until the drag distance triggers, or the
keep it clicked without other fingers until the drag timeout.
I understand that there is added complication in looking at the finger
distance, but there is also existing code in synaptics to handle this, and
again IMHO it feels very natural, especially for someone coming from a touchpad
with physical buttons, so I'd like you to reconsider.
evemu-describe attached. The clickpad in question is a standard Apple touchpad.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-bugs/attachments/20150227/3376a2b3/attachment.html>
More information about the wayland-bugs
mailing list