<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Continue moving the pointer when 2fg scrolling ends" href="https://bugs.freedesktop.org/show_bug.cgi?id=86807#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Continue moving the pointer when 2fg scrolling ends" href="https://bugs.freedesktop.org/show_bug.cgi?id=86807">bug 86807</a> from <a class="email" href="mailto:jstpierre@mecheye.net" title="Jasper St. Pierre <jstpierre@mecheye.net>"> Jasper St. Pierre</a> <pre>(In reply to Hans de Goede from <a href="show_bug.cgi?id=86807#c1">comment #1</a> > This is a different problem, here the clicking finger is also the one doing > the dragging, so here the unpin is deliberate. 2fg scrolling may or may not > trigger here, the problem is that when the 2nd finger comes down the 1st one > is the pointer, and we do not look for a new pointer candidate when the 1st > finger lifts. AFAIK this is deliberate, we don't want which finger is the > pointer to be jumping between fingers when there is an (accidental) lift. I do not lift the first pointer. Sequence: Put index finger down on touchpad. Click touchpad down with index to start drag. Move index around on touchpad. Realize I don't have enough range. Push down middle, and move middle around index while index is still on touchpad. When I want to drop, I release middle and then index. I notice here that xf86-input-synaptics never emits scrolling events while the clickpad is pushed down. That could be a solution.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>