| Did you know ... | Search Documentation: |
| Send methods |
->cancel
and click_gesture<-max_drag_distance.
It performs the following steps:
->active: @off->focus
of the associated window->active: @on->event
if the gesture<-status
attribute is active and the event is a drag event (i.e.
the mouse is moved with one of the buttons held down).
gesture->drag
just succeeds. Intended to be redefined by gesture's subclasses.
->event
<->modifier,
the button matches gesture<->button,
the gesture<->condition
message is @nil
or executed successfully and gesture->verify
succeeds, the gesture will perform the following steps:
->initiate:
Event on itself to initiate<-status
to active->focus
to grab the event-focus
<-status
equals active, invokes gesture->drag:
event to itself<-status
equals active and the button matches the gesture<->button
of the gesture, invoke gesture->terminate
on itself and set gesture<->status
to inactive.
Fails when recogniser<->active
equals @off.
->drag ->initiate ->terminate ->verify -statusSpecification through class_variable/4 is advised as this allows the user to set his/her own preferences and it will give all similar gestures consistent user-interface.
Creating instances of this class is no common use. Note however that
a recogniser for a specific application may be created by creating an
instance of class recogniser
and attaching the necessary gesture->initiate,
gesture->verify, gesture->drag
and/or gesture->terminate
methods to it using object->send_method.
.modifier .button->event
on a button-down event when all conditions are verified. This method
should perform necessary initialisation for the gesture.
gesture->initiate
just succeeds. Intended to be redefined by gesture's subclasses.
->event ->verify->event
when the matching button-up event that terminates the gesture action
occurs.
gesture->terminate
just succeeds. Intended to be redefined by gesture's subclasses.
->event->event
on the button-down event after the button, modifier and condition have
been verified. This method may do additional verification. It is
supposed to succeed or fail without side-effects. Side-effects necessary
during initiation of the gesture should be defined at gesture->initiate.
gesture->verify
just succeeds. Intended to be redefined by gesture's subclasses.
->event ->initiate