Please check the information regarding the three Trigger Screens layout before reading this page.
Here's how trigger/action evaluation takes place:
- it does not matter if there are gaps between triggers.
- the number of trigger rows available depends on the screen size, long-screen devices have more rows available.
- if no defined trigger is found to match an event in the target app settings, then the *Default* settings are searched for a matching trigger. If no matching trigger is found there, the event is ignored.
- As everything in Apt, whatever is defined in a specific app's profile overrides an identical trigger in the *Default* profile, when inside that app. So, put your triggers in the *Default* profile if you want them available everywhere, and then create exceptions in specific app's profiles.
Some triggers have arguments. For those, not only the trigger must match the event, but also the argument:
- button triggers have repeat counters arguments. This is the number of repeat times that the button must be held before the trigger becomes active. A count of 0 means the button is pressed and released (almost: see Min Delay in the Settings Screen) immediately. While the button is held, the repeat count will be displayed on the screen.
- letter arguments take a lower case graffiti letter (a-z). A '*' letter argument indicates that any letter will satisfy the trigger argument.
- digit arguments take a digit (0-9). A '*' argument indicates that any digit will satisfy the trigger argument
- numeric arguments take a number up to 9999. For example, an idle timeout trigger has a numeric argument representing how many idle seconds must pass before the trigger matches.
- stroke arguments record start and end point coordinates of a stroke. When no points have been assigned, the button shows a '?' and no event will match the trigger. When points have been assigned (the trigger is active) a '-' is displayed.
- tap arguments record a pen tap point coordinate. When no point has been assigned, the button shows a '?' and no event will match the trigger. When a point has been assigned (the trigger is active) a '.' is displayed.
In all cases, tap on the trigger arguments button (1st column) to change the argument.
When changing strokes or taps, other strokes and taps which apply to the current target are displayed. Taps are show in blue. Relative strokes are shown in red. Fixed strokes are show in green.
For some triggers (the ones not completely displayable in the button), you can press on the trigger argument button, drag the pen out of the button, then release, to see the trigger argument displayed. This is most useful for the tap and stroke arguments.
On the far left of a trigger screen is a '.' which allows specification of a trigger 'condition'. If the condition doesn't match, then the trigger is not executed. For more on this, see variables, even if the trigger argument DOES match.
Click on "Triggers" on the top bar menu of this site to learn more about specific Triggers.