Under the *Default* app in the app selector pulldown, there are two other 'special' apps called *Tag 1* and *Tag 2*. The purpose of these apps is to allow you to define named sets of actions called Tags, which can then be called from any other
application profile.

Why Tags ?

  • tags allow reuse of sets of actions, whether it be a menu or a macro, so you don't have to specify the actions in several places
  • the *Default* triggers often get crowded. By using a Tag, you only need to use up one space in *Defaults* to e.g. specify a menu with 14 entries
  • you give tags a 4 character name, which can be more useful than the default text that appears up in e.g. a star menu
  • tags allow you to specify if-then-else style execution with macros

Defining A Tag

Looking at a *Tag* app, you will see three screens are selectable (named One, Two and… Three). You can define your Tags in any of the three screens in either of the Tag apps, it makes no difference.

Select a trigger popup, and pick the trigger 'Tag'. Press the left hand button and give the tag a name of 1-4 letters, then
select the associated action you want. Now
use *, > and & on the rows below to make a star menu, popup menu or macro (a Tag can have also only one action, if you wish).

Using a Tag

That's the easy bit. Wherever you want to use a tag, select the action Apt:Call and fill in the name of the Tag that you defined above.


*Tag 1*

defines a tag called 'rset', which runs Applications and selects the first application starting with 'C'.


will call the tag rset whenever a reset occurs, or whenever hard button 1 is pressed.
