General Examples - Basic Level

App Redirect

redirect.png
Cryptopad will always be loaded instead whenever Memopad tries to load.

Brightness Dimming: Idle-based

events.png

In the Memos app, every 8 seconds of the user not doing anything, the brightness will go down by 20 (the Idle + trigger). If the user enters anything after at least 8 seconds of idle time, the brightness will be restored to the level specified in the Prefs screen.

There must be a Prefs screen setting for Brightness enabled, either in the target app or in defaults.

Brightness Dimming: Time-of-day-based

*Default*/Events/0700/ "when time is x"/ Brght/"set Brightness preference in *Defaults* to x"/180

*Default*/Events/1900/ "when time is x"/ Brght/"set Brightness preference in *Defaults* to x"/100

DimTime.png

These lines, added to *Default*/Events, allow you to have a bright screen for the day, a dull one for the night. It will work in all applications except those for which you have set an application-specific default screen brightness. There are two switches, at 7am (brightness set to 180) and, at 7pm (brightness set to 100). NB this image is from the Events screen for the app BlueMoon.

As a prerequisite, there must be a Prefs screen setting for Brightness enabled in *Default* (i.e with the slider). Also, if the screen is actually on at the time-point for the changeover, the brightness change doesn't take place until you "do something".

The image shows the same setting as described above, but now it's not a *Default*-level (i.e. global) setting - it is only affecting the application BlueMoon. As a prerequisite, there must be a Prefs screen brightness setting enabled in *Default* or in BlueMoon itself (i.e with the slider). The BlueMoon settings will over-ride any other settings that affect default Screen Brightness. Note that we can only see the two first numerals (0 and 1) of the time settings (0700 and 1900), because of the small size of the "Trigger argument" input area.

Run Applications after Hotsync

postsync.png

When Hotsync finishes, you are taken directly to the default Applications launcher.

Bluetooth Enable/Disable with Panel

bluetooth.png

(only when the device has the relevant preferences panel)

Note: currently there's no way to specifying returning to the app before the panel was opened, so in this example we go to the default launcher afterwards. We could also tapped on the Done button in the panel to exit.

Enable Apps After Reset

reset.png

Whenever a reset takes place, PXA clocker will be loaded and enabled,
then the Application app is launched.

Responding to SD card name

events.png

The Mnt (short for Mount) triggers on the left dictate what happens when an card is inserted
while in the Memos app. The first trigger matches cards with label 'music'
(you can see the whole label by pressing onto the 'm' button, moving out of
the button, then releasing the pen). The second one has a blank argument
and matches any card name. The first matching one has it's actions
executed
.

These two Mnt triggers result in Aeroplayer launching for the 'music' card,
and otherwise FileZ.

Grafitti/DIA/Command-Bar Automatic Control

anywhere.png

If you add the above settings in the Events tab of Apt, your Grafitti-Anywhere function will be automatically turned on when you do a command-stroke (that upwards-right shortcut.gif stroke) to call up the command-bar, and off after it goes away. This is useful because it allows you to easily give menu commands (which normally have command-bar shortcuts) even if your Grafitti-Anywhere is off.

The DIA triggers say that whenever the DIA comes up (for palms with the feature), Grafitti Anywhere should be turned off
and whenever the DIA goes down turned on again (since you probably don't need G.A. when the DIA is open).

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License