Transitions and Gestures
49
Modero G4 Touch Panels - Configuration and Programming
Touch Gesture Recognition
Gesturing
refers to the act of moving a finger or stylus across the overlay and having the panel recognize and process this
motion as a gesture.
Once a gesture is detected, it is processed as another external button on the panel. This enables the user to design pages
that translate gesture operations into any functionality available to external buttons. In addition, a gesture velocity is
calculated and transmitted to the master along with the gesture type itself in a custom event message. Nothing will be
processed if the external button associated with this gesture has no page flip operations programmed, is disabled, or has
no values programmed for address, channel, level, string output or command output. The custom event, however, is
always transmitted.
The following seven gesture types are supported:
Swipe up
Swipe down
Swipe right
Swipe left
Clockwise circle
Counter-clockwise circle
Double-Tap
The Modero X Series introduces new multi-touch gestures as well:
2 Finger Swipe up
2 Finger Swipe down
2 Finger Swipe right
2 Finger Swipe left
Gesture Velocity
A gesture “velocity” is calculated to represent the speed of the gesture. This is done by measuring the time from when
the user first presses the screen until the user releases. The following simplified velocities are supported and transferred
to the master in the custom event message:
1.
Fast
2.
Normal
3.
Slow
A precise velocity is sent in the custom event message which represents the velocity in terms of pixels per second for
slides and circles. For a double tap, this value is the total time in milliseconds from the first press to the second release.
Gesture Prioritization
It is important to prioritize the operation of the presses, moves and releases of the user to avoid confusion over what the
user intended. The following process is used to determine what the user meant whenever a gesture operation is defined
globally or for this page.
Gesture Prioritization
The user presses outside of a button
or slider and moves before releasing.
The firmware will always try to recognize a gesture as long as the user moves
at least 20 pixels before the release occurs.
The user presses inside of a slider
and moves before releasing.
This will always be processed as a slider operation and no attempt will be
made to recognize a gesture.
The user presses inside of a joystick
button and moves before releasing.
This will always be processed as a joystick operation and no attempt will be
made to recognize a gesture.
The user moves a movable popup page. This will always be processed as a popup page move and not a gesture.
The user presses on a button and then
moves.
In this case, the press will not be sent for the first 0.15 second. If the user has
moved at least 60 pixels by this time, then a button press/release will not be
processed, but this will be processed as a gesture. At 0.15 second, the button
press is processed and once the user releases, the release is processed and
no gesture recognition is attempted.
To be clear, it is not necessary for the user to move off of a button to be
considered a gesture, but to move at least 60 pixels in that first 0.15 of a
second.