diff options
author | José Expósito <jose.exposito89@gmail.com> | 2021-07-12 19:50:09 +0200 |
---|---|---|
committer | Simon Ser <contact@emersion.fr> | 2021-09-27 15:30:31 +0200 |
commit | d069a783bcafe65c240f2369b68f5e8d45d0b9a2 (patch) | |
tree | 2d0d1874ecb1703c560ec24bfcddf8a8bebd0b60 /backend/libinput | |
parent | fb15538247ea7f4b91ef987650542ae3f5acc89e (diff) |
pointer: add hold pointer event definition
As touchpad touches are generally fully abstracted, a client cannot
currently know when a user is interacting with the touchpad without
moving. This is solved by hold gestures.
Hold gestures are notifications about one or more fingers being held
down on the touchpad without significant movement.
Hold gestures are primarily designed for two interactions:
- Hold to interact: where a hold gesture is active for some time a
menu could pop up, some object could be selected, etc.
- Hold to cancel: where e.g. kinetic scrolling is currently active,
the start of a hold gesture can be used to stop the scroll.
Unlike swipe and pinch, hold gestures, by definition, do not have
movement, so there is no need for an "update" stage in the gesture.
Create two structs, wlr_event_pointer_hold_begin and
wlr_event_pointer_hold_end, to represent hold gesture events and the
signals to emit them: wlr_pointer->pointer.hold_begin/hold_end.
Diffstat (limited to 'backend/libinput')
0 files changed, 0 insertions, 0 deletions