Memory-managed wrapper type.

Type class for types which can be safely cast to Gesture, for instance with toGesture.

Cast to Gesture, for types for which this is known to be safe. For general casts, use castTo.

A convenience alias for Nothing :: Maybe Gesture.

If there are touch sequences being currently handled by gesture, this function returns True and fills in rect with the bounding box containing all active touches. Otherwise, False will be returned.

Note: This function will yield unexpected results on touchpad gestures. Since there is no correlation between physical and pixel distances, these will look as if constrained in an infinitely small area, rect width and height will thus be 0 regardless of the number of touchpoints.

Since: 3.14

If there are touch sequences being currently handled by gesture, this function returns True and fills in x and y with the center of the bounding box containing all active touches. Otherwise, False will be returned.

Since: 3.14

Returns the master Device that is currently operating on gesture, or Nothing if the gesture is not being interacted.

Since: 3.14

Returns all gestures in the group of gesture

Since: 3.14

Returns the last event that was processed for sequence.

Note that the returned pointer is only valid as long as the sequence is still interpreted by the gesture. If in doubt, you should make a copy of the event.

Returns the EventSequence that was last updated on gesture.

Since: 3.14

If sequence is currently being interpreted by gesture, this function returns True and fills in x and y with the last coordinates stored for that event sequence. The coordinates are always relative to the widget allocation.

Since: 3.14

Returns the sequence state, as seen by gesture.

Since: 3.14

Returns the list of GdkEventSequences currently being interpreted by gesture.

Since: 3.14

Returns the user-defined window that receives the events handled by gesture. See gestureSetWindow for more information.

Since: 3.14

Adds gesture to the same group than groupGesture. Gestures are by default isolated in their own groups.

When gestures are grouped, the state of GdkEventSequences is kept in sync for all of those, so calling gestureSetSequenceState, on one will transfer the same value to the others.

Groups also perform an "implicit grabbing" of sequences, if a EventSequence state is set to GTK_EVENT_SEQUENCE_CLAIMED on one group, every other gesture group attached to the same Widget will switch the state for that sequence to GTK_EVENT_SEQUENCE_DENIED.

Since: 3.14

Returns True if gesture is currently handling events corresponding to sequence.

Since: 3.14

Returns True if the gesture is currently active. A gesture is active meanwhile there are touch sequences interacting with it.

Since: 3.14

Returns True if both gestures pertain to the same group.

Since: 3.14

Returns True if the gesture is currently recognized. A gesture is recognized if there are as many interacting touch sequences as required by gesture, and Gesture::check returned True for the sequences being currently interpreted.

Since: 3.14

Sets the state of sequence in gesture. Sequences start in state GTK_EVENT_SEQUENCE_NONE, and whenever they change state, they can never go back to that state. Likewise, sequences in state GTK_EVENT_SEQUENCE_DENIED cannot turn back to a not denied state. With these rules, the lifetime of an event sequence is constrained to the next four:

• None
• None → Denied
• None → Claimed
• None → Claimed → Denied

Note: Due to event handling ordering, it may be unsafe to set the state on another gesture within a Gesture::begin signal handler, as the callback might be executed before the other gesture knows about the sequence. A safe way to perform this could be:

static void
first_gesture_begin_cb (GtkGesture       *first_gesture,
                        GdkEventSequence *sequence,
                        gpointer          user_data)
{
  gtk_gesture_set_sequence_state (first_gesture, sequence, GTK_EVENT_SEQUENCE_CLAIMED);
  gtk_gesture_set_sequence_state (second_gesture, sequence, GTK_EVENT_SEQUENCE_DENIED);
}

static void
second_gesture_begin_cb (GtkGesture       *second_gesture,
                         GdkEventSequence *sequence,
                         gpointer          user_data)
{
  if (gtk_gesture_get_sequence_state (first_gesture, sequence) == GTK_EVENT_SEQUENCE_CLAIMED)
    gtk_gesture_set_sequence_state (second_gesture, sequence, GTK_EVENT_SEQUENCE_DENIED);
}

If both gestures are in the same group, just set the state on the gesture emitting the event, the sequence will be already be initialized to the group's global state when the second gesture processes the event.

Since: 3.14

Sets the state of all sequences that gesture is currently interacting with. See gestureSetSequenceState for more details on sequence states.

Since: 3.14

Sets a specific window to receive events about, so gesture will effectively handle only events targeting window, or a child of it. window must pertain to eventControllerGetWidget.

Since: 3.14

Separates gesture into an isolated group.

Since: 3.14

Construct a GValueConstruct with valid value for the “n-points” property. This is rarely needed directly, but it is used by new.

Get the value of the “n-points” property. When overloading is enabled, this is equivalent to

get gesture #nPoints

Set the value of the “window” property to Nothing. When overloading is enabled, this is equivalent to

clear #window

Construct a GValueConstruct with valid value for the “window” property. This is rarely needed directly, but it is used by new.

Get the value of the “window” property. When overloading is enabled, this is equivalent to

get gesture #window

Set the value of the “window” property. When overloading is enabled, this is equivalent to

set gesture [ #window := value ]

Type for the callback on the (unwrapped) C side.

This signal is emitted when the gesture is recognized. This means the number of touch sequences matches Gesture:n-points, and the Gesture::check handler(s) returned TRUE.

Note: These conditions may also happen when an extra touch (eg. a third touch on a 2-touches gesture) is lifted, in that situation sequence won't pertain to the current set of active touches, so don't rely on this being true.

Since: 3.14

Connect a signal handler for the “begin” signal, to be run after the default handler. When overloading is enabled, this is equivalent to

after gesture #begin callback

Wrap the callback into a Closure.

Generate a function pointer callable from C code, from a C_GestureBeginCallback.

A convenience synonym for Nothing :: Maybe GestureBeginCallback.

Connect a signal handler for the “begin” signal, to be run before the default handler. When overloading is enabled, this is equivalent to

on gesture #begin callback

Wrap a GestureBeginCallback into a C_GestureBeginCallback.

Type for the callback on the (unwrapped) C side.

This signal is emitted whenever a sequence is cancelled. This usually happens on active touches when eventControllerReset is called on gesture (manually, due to grabs...), or the individual sequence was claimed by parent widgets' controllers (see gestureSetSequenceState).

gesture must forget everything about sequence as a reaction to this signal.

Since: 3.14

Connect a signal handler for the “cancel” signal, to be run after the default handler. When overloading is enabled, this is equivalent to

after gesture #cancel callback

Wrap the callback into a Closure.

Generate a function pointer callable from C code, from a C_GestureCancelCallback.

A convenience synonym for Nothing :: Maybe GestureCancelCallback.

Connect a signal handler for the “cancel” signal, to be run before the default handler. When overloading is enabled, this is equivalent to

on gesture #cancel callback

Wrap a GestureCancelCallback into a C_GestureCancelCallback.

Type for the callback on the (unwrapped) C side.

This signal is emitted when gesture either stopped recognizing the event sequences as something to be handled (the Gesture::check handler returned False), or the number of touch sequences became higher or lower than Gesture:n-points.

Note: sequence might not pertain to the group of sequences that were previously triggering recognition on gesture (ie. a just pressed touch sequence that exceeds Gesture:n-points). This situation may be detected by checking through gestureHandlesSequence.

Since: 3.14

Connect a signal handler for the “end” signal, to be run after the default handler. When overloading is enabled, this is equivalent to

after gesture #end callback

Wrap the callback into a Closure.

Generate a function pointer callable from C code, from a C_GestureEndCallback.

A convenience synonym for Nothing :: Maybe GestureEndCallback.

Connect a signal handler for the “end” signal, to be run before the default handler. When overloading is enabled, this is equivalent to

on gesture #end callback

Wrap a GestureEndCallback into a C_GestureEndCallback.

Type for the callback on the (unwrapped) C side.

This signal is emitted whenever a sequence state changes. See gestureSetSequenceState to know more about the expectable sequence lifetimes.

Since: 3.14

Connect a signal handler for the “sequence-state-changed” signal, to be run after the default handler. When overloading is enabled, this is equivalent to

after gesture #sequenceStateChanged callback

Wrap the callback into a Closure.

Generate a function pointer callable from C code, from a C_GestureSequenceStateChangedCallback.

A convenience synonym for Nothing :: Maybe GestureSequenceStateChangedCallback.

Connect a signal handler for the “sequence-state-changed” signal, to be run before the default handler. When overloading is enabled, this is equivalent to

on gesture #sequenceStateChanged callback

Wrap a GestureSequenceStateChangedCallback into a C_GestureSequenceStateChangedCallback.

Type for the callback on the (unwrapped) C side.

This signal is emitted whenever an event is handled while the gesture is recognized. sequence is guaranteed to pertain to the set of active touches.

Since: 3.14

Connect a signal handler for the “update” signal, to be run after the default handler. When overloading is enabled, this is equivalent to

after gesture #update callback

Wrap the callback into a Closure.

Generate a function pointer callable from C code, from a C_GestureUpdateCallback.

A convenience synonym for Nothing :: Maybe GestureUpdateCallback.

Connect a signal handler for the “update” signal, to be run before the default handler. When overloading is enabled, this is equivalent to

on gesture #update callback

Wrap a GestureUpdateCallback into a C_GestureUpdateCallback.