The taps and strokes on the left lead to the screen area definitions on the right. It can be seen that the begin point of a stroke has a small box and is labelled with the first associated action. (leftmost image header is out of date, sorry about that).
In the shot on the left (not related to the previous configuration) you can see the strokes and taps which are active in the target app. The 'grayed out' red stroke is a stroke defined in the *Default* configuration (and thus active in all apps). You can see this view with the Apt:Menu action.
The taps and strokes on the left lead to the screen area definitions on the right. It can be seen that the begin point of a stroke has a small box and is labelled with the first associated action. (leftmost image header is out of date, sorry about that).
In the shot on the left (not related to the previous configuration) you can see the strokes and taps which are active in the target app. The 'grayed out' red stroke is a stroke defined in the *Default* configuration (and thus active in all apps). You can see this view with the Apt:Menu action.
Rona
A 'ronamatic' stroke from bottom-centre of the screen to top-centre.
Tap
Argument: Tap Point
A single tap somewhere on the screen. You can define the tap position in as many as three different ways!
- Press the trigger arg button and tap wherever you wish
- Leave the trigger arg undefined ('?' showing), go to the target app, and use the Apt:GetTap action (with default settings you can reach this by holding hard key 4 for 2 seconds. This has the advantage of being able to see the other controls on the screen when defining the tap.
- Don't create a Tap trigger in Apt at all. When you are using an app and want to add a tap trigger just use Add Tap and a new one will be created. Then use the Apt Menu again to go to Apt and define the associated action.
When you are actually using the trigger, the tap does not have to be on the exact same pixel that you defined. The range within it must be is specified in the trigger argument section for more info on defining points.
Warning: tap points will obscure controls which are at the same place Although this can of course be useful sometimes, usually you will want to find an area in the target app without any controls.
Stroke
Argument: Start, End Coordinates
A drag of the pen from one specific point on the screen to another. The start and end points can be defined as for the Tap above.
When the pen goes down inside the start point of a stroke, controls underneath the stroke will not see it. However, if the pen goes up outside of the defined end point then Apt will resend the original pen up and pen down events. In other words, controls underneath should not be affected by fixed Apt strokes, but it remains to be seen :-)
Tip: to cancel a stroke (return it to undefined), you can just tap twice on the screen during recording.
Relative Stroke
Argument: Start, End Coordinates
A drag of the pen from one point on the screen to another, a specific direction and distance away. The direction and distance can be defined as for the Stroke above. In the screenshot, the red strokes show that the brightness can be increased/decreased by making a side stroke right/left anywhere on the screen. Of necessity, relative strokes are more likely to affect underlying screen elements so it might be preferable to use fixed ones where possible.
Note: relative strokes will not be registered if they start in the silkscreen/DIA area. They may, however, end there.
Tip: to cancel a relative stroke (return it to undefined), you can just tap twice on the screen during recording.
Letter (Let)
Argument: A letter (a-z) or "*"
Graffiti characters a-z. Does not trigger if a field has focus. "*" arg matches any lowercase letter.
Held Letter (Let+)
As above, but for a held letter. The hold time is specified in the Apt Settings form. This trigger fires
when a field has focus, unlike Let.
Digit (Dig)
Argument: a digit (0-9) or "*"
Digit 0-9. Does not trigger if a field has focus. "*" arg matches any digit.
Held Digit (Dig+)
As above, but for a held digit. The hold time is specified in the Apt Settings form. This trigger fires
when a field has focus, unlike Dig.
Backspace (BSpc)
Backspace character. Does not trigger if a field has focus.
Space (Spc)
Space character. Does not trigger if a field has focus.
Full-stop (".")
Full-stop character. Does not trigger if a field has focus. Useful as a double-tap on the graffiti area to do something.
"$"
"$" character. Does not trigger if a field has focus. No, it's unknown why this one was put in, perhaps a money fetish?
