Creating custom Gestures

This article will focus on how you can make your own gestures in order to get most out of the library for your project.
The GestureManager detects gestures based on the TouchEvents and TuioEvents dispatched by the TuioManager. Every gesture has a kind of checklist that has to be completed from top to bottom in order dispatch the gesture's event to the stage. This process is called "saturation" and if the GestureManager reaches the bottom of the list it is fully "saturated". From now on I'll call every single item on the checklist "gesture step" and I'll call the checklist "gesture step sequence".
So in order to create your own gesture you simply have to define this gesture step sequence and have to implement a function that will be called if the sequence is saturated.
Before you can define your gesture step sequence you have to create a class for your gesture that extends the Gesture class. This could look somehow like this:

This gesture won't do much now because we have no gesture step sequence or callback behaviour defined yet. So let's change that and add some steps.

As you can see steps are added via the function addStep(...). This function expects an instance of the GestureStep class which has two parameters. The first one is the name of the event and should be quite familiar if you ever happended to use events in as3. You can put all types of TuioEvents and TouchEvents in there. A step will be saturated as soon as the desired event is received. The second argument is an object which defines additional behaviours for the step. Here is a list of all the possible properties:

• targetAlias: This is a String that is used as an alias name for the event's target. By using the same targetAlias for different GestureSteps you can make sure that the event was dispatched on the same target. If you use a "!" as the first character the value behind the name will be overwritten if it already has been set. This might be useful within loops.
• tuioContainerAlias: This is again a String which if used for different GestureSteps makes sure that the tracked object that generated the event is the same. If you use a "!" as the first character the value behind the name will be overwritten if it already has been set.
• frameIDAlias: This is also a String which can be used to make sure that the events were all generated by tracked objects from the same tuio frame. If you use a "!" as the first character the value behind the name will be overwritten if it already has been set. Also a failed match will cause the gesture to fail unlike the other alias types.
• minDelay: Sets the minimum delay in ms for the specified event. After this the event is accepted.
• maxDelay: Sets the maximum allowed delay in ms for the specified event. After this the gesture fails.
• die: If set true the gesture fails if the GestureStep is saturated. GestureSteps that have die set true are optional and if the next GestureStep with die set false is saturated will be skipped.
• goto: If set to a value between [1-n° of steps] the next check will occur on the specified GestureStep. This is basically for creating loops e.g. jump to an earlier step after reaching the final step.
• optional: If set true the GestureStep will be skipped if it doesn't saturate or dies and the next GestureStep is saturated. If an optional GestureStep dies this won't cause the whole gesture to die.

Now that we have our gesture step sequence set up we have to take care of the actual event dispatching which is pretty straight forward.

The dispatchGestureEvent function will receive two arguments when called. The first one is the target DisplayObject of the event that saturated the last step. The second one is the GestureStepSequence object that was saturated which is very handy because it gives you access to all the targets, tuioContainers and frameIDs saved under the aliases you used when specifying your gesture's steps. I used the getTarget(...) function to retrieve the target of the very first touch so i can dispatch the event on it. You can also use the GestureStepSequence to store and retrieve custom values with storeValue(...) and getValue(...). THis is very useful in looping GestureStepSequences.

Sometimes you might want to handle each step of the sequence or do some additional calculations after certain steps. This can be achieved very easily because after each step a GestureStepEvent is dispatched on you gesture. This could look like this:

Now you should be able to write your own gestures but if you happen to run into any problems or parts of the article aren't comprehensible write a comment or send me an email.