Connect to Begin signal.
Connect to Cancel signal.
Connect to End signal.
Connect to SequenceStateChanged signal.
Connect to Update signal.
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.
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.
Returns the master #GdkDevice that is currently operating on gesture, or null if the gesture is not being interacted.
Returns all gestures in the group of gesture
Returns the last event that was processed for sequence.
Returns the #GdkEventSequence that was last updated on gesture.
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.
Returns the sequence state, as seen by gesture.
Returns the list of #GdkEventSequences currently being interpreted by gesture.
Returns the user-defined window that receives the events handled by gesture. See gtk.gesture.Gesture.setWindow for more information.
Adds gesture to the same group than group_gesture. Gestures are by default isolated in their own groups.
Returns true if gesture is currently handling events corresponding to sequence.
Returns true if the gesture is currently active. A gesture is active meanwhile there are touch sequences interacting with it.
Returns true if both gestures pertain to the same group.
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 #GtkGesture::check returned true for the sequences being currently interpreted.
Returns this, for use in with statements.
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:
Sets the state of all sequences that gesture is currently interacting with. See gtk.gesture.Gesture.setSequenceState for more details on sequence states.
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 gtk.event_controller.EventController.getWidget.
Separates gesture into an isolated group.
Get nPoints property.
Get window property.
Set window property.
Get builder for gtk.gesture.Gesture
Returns this, for use in with statements.
Get builder for gtk.event_controller.EventController
Get propagationPhase property.
Set propagationPhase property.
Get widget property.
Gets the propagation phase at which controller handles events.
Returns the #GtkWidget this controller relates to.
Feeds an events into controller, so it can be interpreted and the controller actions triggered.
Resets the controller to a clean state. Every interaction the controller did through #GtkEventController::handle-event will be dropped at this point.
Sets the propagation phase at which a controller handles events.
#GtkGesture is the base object for gesture recognition, although this object is quite generalized to serve as a base for multi-touch gestures, it is suitable to implement single-touch and pointer-based gestures (using the special null #GdkEventSequence value for these).
The number of touches that a #GtkGesture need to be recognized is controlled by the #GtkGesture:n-points property, if a gesture is keeping track of less or more than that number of sequences, it won't check wether the gesture is recognized.
As soon as the gesture has the expected number of touches, the gesture will run the #GtkGesture::check signal regularly on input events until the gesture is recognized, the criteria to consider a gesture as "recognized" is left to #GtkGesture subclasses.
A recognized gesture will then emit the following signals:
Event propagation
In order to receive events, a gesture needs to either set a propagation phase through gtk.event_controller.EventController.setPropagationPhase, or feed those manually through gtk.event_controller.EventController.handleEvent.
In the capture phase, events are propagated from the toplevel down to the target widget, and gestures that are attached to containers above the widget get a chance to interact with the event before it reaches the target.
After the capture phase, GTK+ emits the traditional #GtkWidget::button-press-event, #GtkWidget::button-release-event, #GtkWidget::touch-event, etc signals. Gestures with the gtk.types.PropagationPhase.Target phase are fed events from the default #GtkWidget::event handlers.
In the bubble phase, events are propagated up from the target widget to the toplevel, and gestures that are attached to containers above the widget get a chance to interact with events that have not been handled yet.
States of a sequence # {#touch-sequence-states}
Whenever input interaction happens, a single event may trigger a cascade of #GtkGestures, both across the parents of the widget receiving the event and in parallel within an individual widget. It is a responsibility of the widgets using those gestures to set the state of touch sequences accordingly in order to enable cooperation of gestures around the #GdkEventSequences triggering those.
Within a widget, gestures can be grouped through gtk.gesture.Gesture.group, grouped gestures synchronize the state of sequences, so calling gtk.gesture.Gesture.setSequenceState on one will effectively propagate the state throughout the group.
By default, all sequences start out in the #GTK_EVENT_SEQUENCE_NONE state, sequences in this state trigger the gesture event handler, but event propagation will continue unstopped by gestures.
If a sequence enters into the #GTK_EVENT_SEQUENCE_DENIED state, the gesture group will effectively ignore the sequence, letting events go unstopped through the gesture, but the "slot" will still remain occupied while the touch is active.
If a sequence enters in the #GTK_EVENT_SEQUENCE_CLAIMED state, the gesture group will grab all interaction on the sequence, by:
Note: if a sequence is set early to #GTK_EVENT_SEQUENCE_CLAIMED on #GDK_TOUCH_BEGIN/#GDK_BUTTON_PRESS (so those events are captured before reaching the event widget, this implies #GTK_PHASE_CAPTURE), one similar event will emulated if the sequence changes to #GTK_EVENT_SEQUENCE_DENIED. This way event coherence is preserved before event propagation is unstopped again.
Sequence states can't be changed freely, see gtk.gesture.Gesture.setSequenceState to know about the possible lifetimes of a #GdkEventSequence.
Touchpad gestures
On the platforms that support it, #GtkGesture will handle transparently touchpad gesture events. The only precautions users of #GtkGesture should do to enable this support are: