pointer_gestures_unstable_v1 protocol

zwp_pointer_gestures_v1 interface version 2

A global interface to provide semantic touchpad gestures for a given pointer. Two gestures are currently supported: swipe and pinch. All gestures follow a three-stage cycle: begin, update, end and are identified by a unique id. Warning! The protocol described in this file is experimental and backward incompatible changes may be made. Backward compatible changes may be added together with the corresponding interface version bump. Backward incompatible changes are done by bumping the version number in the protocol and interface names and resetting the interface version. Once the protocol is to be declared stable, the 'z' prefix and the version number in the protocol and interface names are removed and the interface version number is reset.

Requests

get_swipe_gesture since version 0

Create a swipe gesture object. See the wl_pointer_gesture_swipe interface for details.

Arguments
id (new_id) (zwp_pointer_gesture_swipe_v1)
pointer (object) (wl_pointer)

get_pinch_gesture since version 0

Create a pinch gesture object. See the wl_pointer_gesture_pinch interface for details.

Arguments
id (new_id) (zwp_pointer_gesture_pinch_v1)
pointer (object) (wl_pointer)

release (destructor) since version 2

Destroy the pointer gesture object. Swipe and pinch objects created via this gesture object remain valid.





zwp_pointer_gesture_swipe_v1 interface version 2

A swipe gesture object notifies a client about a multi-finger swipe gesture detected on an indirect input device such as a touchpad. The gesture is usually initiated by multiple fingers moving in the same direction but once initiated the direction may change. The precise conditions of when such a gesture is detected are implementation-dependent. A gesture consists of three stages: begin, update (optional) and end. There cannot be multiple simultaneous pinch or swipe gestures on a same pointer/seat, how compositors prevent these situations is implementation-dependent. A gesture may be cancelled by the compositor or the hardware. Clients should not consider performing permanent or irreversible actions until the end of a gesture has been received.

Requests

destroy (destructor) since version 0

Events

begin since version 0

This event is sent when a multi-finger swipe gesture is detected on the device.

serial (uint)
time (uint)

timestamp with millisecond granularity

surface (object) (wl_surface)
fingers (uint)

number of fingers


update since version 0

This event is sent when a multi-finger swipe gesture changes the position of the logical center. The dx and dy coordinates are relative coordinates of the logical center of the gesture compared to the previous event.

time (uint)

timestamp with millisecond granularity

dx (fixed)

delta x coordinate in surface coordinate space

dy (fixed)

delta y coordinate in surface coordinate space


end since version 0

This event is sent when a multi-finger swipe gesture ceases to be valid. This may happen when one or more fingers are lifted or the gesture is cancelled. When a gesture is cancelled, the client should undo state changes caused by this gesture. What causes a gesture to be cancelled is implementation-dependent.

serial (uint)
time (uint)

timestamp with millisecond granularity

cancelled (int)

1 if the gesture was cancelled, 0 otherwise





zwp_pointer_gesture_pinch_v1 interface version 2

A pinch gesture object notifies a client about a multi-finger pinch gesture detected on an indirect input device such as a touchpad. The gesture is usually initiated by multiple fingers moving towards each other or away from each other, or by two or more fingers rotating around a logical center of gravity. The precise conditions of when such a gesture is detected are implementation-dependent. A gesture consists of three stages: begin, update (optional) and end. There cannot be multiple simultaneous pinch or swipe gestures on a same pointer/seat, how compositors prevent these situations is implementation-dependent. A gesture may be cancelled by the compositor or the hardware. Clients should not consider performing permanent or irreversible actions until the end of a gesture has been received.

Requests

destroy (destructor) since version 0

Events

begin since version 0

This event is sent when a multi-finger pinch gesture is detected on the device.

serial (uint)
time (uint)

timestamp with millisecond granularity

surface (object) (wl_surface)
fingers (uint)

number of fingers


update since version 0

This event is sent when a multi-finger pinch gesture changes the position of the logical center, the rotation or the relative scale. The dx and dy coordinates are relative coordinates in the surface coordinate space of the logical center of the gesture. The scale factor is an absolute scale compared to the pointer_gesture_pinch.begin event, e.g. a scale of 2 means the fingers are now twice as far apart as on pointer_gesture_pinch.begin. The rotation is the relative angle in degrees clockwise compared to the previous pointer_gesture_pinch.begin or pointer_gesture_pinch.update event.

time (uint)

timestamp with millisecond granularity

dx (fixed)

delta x coordinate in surface coordinate space

dy (fixed)

delta y coordinate in surface coordinate space

scale (fixed)

scale relative to the initial finger position

rotation (fixed)

angle in degrees cw relative to the previous event


end since version 0

This event is sent when a multi-finger pinch gesture ceases to be valid. This may happen when one or more fingers are lifted or the gesture is cancelled. When a gesture is cancelled, the client should undo state changes caused by this gesture. What causes a gesture to be cancelled is implementation-dependent.

serial (uint)
time (uint)

timestamp with millisecond granularity

cancelled (int)

1 if the gesture was cancelled, 0 otherwise