GestureLongPressSignalName

This signal is emitted when the gesture is recognized. This means the number of touch sequences matches GtkGesture:n-points, and the GtkGesture::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.

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

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

This signal is emitted whenever a press moved too far, or was released before GtkGestureLongPress::pressed happened.

This signal is emitted when gesture either stopped recognizing the event sequences as something to be handled (the GtkGesture::check handler returned false), or the number of touch sequences became higher or lower than GtkGesture: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 GtkGesture:n-points). This situation may be detected by checking through gtk_gesture_handles_sequence().

The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.

Note that getting this signal doesn’t itself guarantee that the value of the property has actually changed. When it is emitted is determined by the derived GObject class. If the implementor did not create the property with G_PARAM_EXPLICIT_NOTIFY, then any call to g_object_set_property() results in notify being emitted, even if the new value is the same as the old. If they did pass G_PARAM_EXPLICIT_NOTIFY, then this signal is emitted only when they explicitly call g_object_notify() or g_object_notify_by_pspec(), and common practice is to do that only when the value has actually changed.

This signal is typically used to obtain change notification for a single property, by specifying the property name as a detail in the g_signal_connect() call, like this:

(C Language Example):

g_signal_connect (text_view->buffer, "notify::paste-target-list",
                  G_CALLBACK (gtk_text_view_target_list_notify),
                  text_view)

It is important to note that you must use canonical parameter names as detail strings for the notify signal.

This signal is emitted whenever a press goes unmoved/unreleased longer than what the GTK+ defaults tell.

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

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.

Mouse button number to listen to, or 0 to listen for any button.

Undocumented

Whether the gesture is exclusive. Exclusive gestures only listen to pointer and pointer emulated events.

The number of touch points that trigger recognition on this gesture,

The propagation phase at which this controller will handle events.

Whether the gesture handles only touch events.

The widget receiving the GdkEvents that the controller will handle.

If non-nil, the gesture will only listen for events that happen on this GdkWindow, or a child of it.