On the Buttons Screen, you can specify actions to take place when any of the following triggers go off:
Note: not all triggers are available on every device. Just ignore the ones you don't have.
- Hrd1 - Hard Button 1
- Hrd2 - Hard Button 2
- Hrd3 - Hard Button 3 2
- Hrd4 - Hard Button 4 2
- NavU - Up on the 5-Way Navigation
- NavD - Down on the 5-Way Navigation
- NavL - Left on the 5-Way Navigation 1
- NavR - Right on the 5-Way Navigation 1
- Cntr - Center on the 5-Way Navigation 1
- oHrd1 - Option + Hard Button 1 3 This trigger also responds to Voice Memo on the LifeDrive, and maybe other special buttons on other devices.
- oHrd2 - Option + Hard Button 2 3 This trigger also responds to the Screen Flip (?) button on the LifeDrive, and maybe other special buttons on other devices.
- oHrd3 - Option + Hard Button 3 3 This button may respond to other 'unusual' hard buttons on some devices.
- oHrd4 - Option + Hard Button 4 3 This button may respond to other 'unusual' hard buttons on some devices.
- Side - Side Hard Button 3
- VolUp - Volume Up 3
- VolDn - Volume Down 3
- VLnch - Home button on the silkscreen
- VMenu - Menu button on the silkscreen. This trigger also responds when the hard menu button on a Treo is pressed.
- VFind - Find button on the silkscreen. Also responds to the option + find on a Treo.
- Powr - Power Button. Triggers only when you manually turn the device off. Use the Wake trigger for a turn on event.
1 - Unavailable on the Palm Zire 21
2 - Unavailable on the Palm Zire 21, 22 and 31
3 - Available only on Treos
Tip
(For advanced users!) Since Apt can generate an action that is equivalent to a button press (action categories Nav and Hard), you can define a trigger whose action includes firing another trigger. This is a rudimentary way of implementing "sub-routines" in Apt.
For example, you can make a certain trigger generate an oHrd1 button press at a given point; and have a set of other actions to run when oHrd1 is pressed (even if your device physically does not have oHrd1).