The timeout can be avoided by sending tap+drag as press/release/(wait)/press/drag. I don't have it here to test but I remember hearing this is what some (all?) mac implementations do.
This requires libinput to also decide whether a click is a "double click" or not, the fact that our software was doing it's own timeout rather than use the system api is why I heard about this. Moving double click decision into libinput certainly seems consistent with what is being done here, and would avoid a big annoyance where different clients have different rules. The fact that this "mouse gesture" is interpreted by clients on X is just historical because X predates the double-click idea. Searching on the web shows that recent versions of OS/X turned off tap-and-drag, since all the discussion was from people asking how to turn it back on. This indicates two things: first that somebody at Apple decided that it was not desirable to a big enough set of users to change the default, second that there is a non-zero set of users that *do* like it. On Fri, Jan 8, 2016 at 9:14 AM, Cyril B. <[email protected]> wrote: > Peter Hutterer wrote: > >> thanks for doing this work. tbh, I'm not a big fan of having this as a >> configuration option. IMO if you are using tapping as an interaction >> method >> on the touchpad, having tap-and-drag available is the natural extension >> and >> I don't see why we should disable it. >> > > I have the same issue as Caibin: I simply cannot use tap-to-click as it > is, as it triggers unwanted drags all the time. I even wonder how other > people do not have the same problem: do they systematically (consciously or > not) wait before moving the cursor after tapping? > > However, I'd like to point out that both Windows and OSX have tap-and-drag > disabled by default. That means that many users are probably used to that > behaviour, and may find it frustrating not being able to turn off > tap-and-drag. > > Regarding decreasing the timeout, in my case I doubt it would work as my > tap + move combination is done very quickly, as fast as a double-tap > actually. I'm willing to try it though, but I'm not sure what constant > should be modified in the code. > > Caibin: thanks for the work, I'll test your branch very soon. > > -- > Cyril B. > > _______________________________________________ > wayland-devel mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/wayland-devel >
_______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
