https://bugs.freedesktop.org/show_bug.cgi?id=89999
--- Comment #3 from Hans de Goede <[email protected]> --- (In reply to Peter Hutterer from comment #2) > couple of question here, can we do something with a timeout? i.e. three > fingers down + timeout X switches to drag motion, otherwise the swipe > triggers. Yes that is possible, do we want to handle this in gestures.c or in tap.c though, I've a feeling it belongs in tap.c. because we do not want the following sequence to trigger it: Finger 1 down Finger 1 moves over tap threshold Fingers 2 + 3 down Timeout Where as having it in the gesture code would lead to the timeout eventually activating 3 finger mode, and then if more time is passed before moving, switch to 3fg drag-n-drop. I guess one could argue that is desirable behavior, and in that case this is easy to implement in the gesture code, esp. since the tap statemachine already is too complicated IMHO. > we don't have any movement restrictions on swipe motions atm, right? > anything is a swipe once 3 fingers are down, so maybe we should add > restrictions to horizontal/vertical swiping here? I've deliberately not added any limits as I've seen e.g. usb-touchpads with firmware handled gestures which have diagonal swipes, so I would rather leave any direction locking up to the user. > once of the drawbacks of having this via gestures if of course that we need > both the compositor (for cursor movement) and the toolkits to support this. > that's the upside too though I guess, it makes context-specific interaction > more doable than emulating it in libinput. Ack. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ wayland-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-bugs
