Prefs+ Screen

This screen has some miscellaneous preferences that you can set for a target app.


Lock Triggers

Apt can be used to restrict access to particular applications. If one or more lock triggers (max 3) are specified in the Prefs+ screen, then access will be denied unless the user can replicate the sequence of triggers specified here (more information on 'triggers' later). Some triggers are unsuitable for use as lock triggers, you will be informed when an invalid trigger is selected. Strokes/taps do not function as lock triggers when it's not a full-screen lock (see below). An interesting one is using a named memory card insertion to unlock an app
In the screenshot, Hard 3 button must be pressed and the screen tapped in a particular place to gain access to the Calc app (keep those calculations secret, OK ?)
The lock triggers in the *default* app have two purposes. Firstly, they are used to lock Apt itself (if set of course). Secondly, they are used to make a lock whenever a Lock action is executed (see below).

Full Screen

By default, a lock is applied after the target has run, and the lock window is small so the target app can be seen in the background. When Full Screen is selected, the lock window appears before the target runs and the screen is blanked.
Small note: with full-screen locking, -Lnch, +Lnch and Exit triggers (see later) are never triggered if the lock check fails. With the small lock window they are.

Prefs Off

Do not apply any preferences in the target app (compatibility aid)

Triggers Off

Do not respond to any triggers in the target app (compatibility aid)

Cmd Apt Apply

whether to show the relevant menu command bar icon. If this is enabled in *default* or the target app, it will appear. The initial value for this checkbox in new target preferences follow those of *default*.

Remember Me

if not checked, then visits to the target app will be ignored for the purposes of the Back and Rcnt actions (see Actions help item)
This control does not work for the *default* app.

Disp. -Launch

usually, the rotation, DIA and status bar settings from the Prefs screen (leftmost one) are applied once an application has finished loading, setting up the screen etc, otherwise the Apt preferences may get undone as the app loads. For some apps, applying them before the app starts up may result in less flicker and 'jumping around'.


These checkboxes allow you to define lists of your favourite apps. Each checkbox includes the current target app in one of 4 lists. You can then assign one of the actions Fill:Fav1-4 to e.g. a button to show the apps with the corresponding checkbox checked. In the screenshot, Contacts will be included whenever Favourites list 1 or 2 is shown,

SD -> Launcher

If not checked in either *default* or the target, when an external memory card is inserted PalmOS is blocked from it's usual action of switching to Applications and showing apps in PALM/Launcher.


Whether to show, mask or hide private records in the target app.

Khroma Theme

if you have installed the DB file from the Khroma distribution (KhromaDB.pdb, can also be found in the thirdparties/ directory) you will find here a list of available colour themes to apply. Unlike most other Apt preferences, the colour theme is removed by the system when the target exits, so you do not need to set a colour theme in *default* if you don't wish to.


Whether to keep the app hidden (by setting the 'hide' attribute on the file). '-' means Apt will not do anything with the attribute. When 'Keep Visible' is set, Apt will make sure the target is visible, even when another app tries to make it hidden (and vice versa for 'Keep Hidden').
This control does not work for the *default* app.


Same as the 'Hiding' selector, but affects whether the 'backup' attribute on the file is set i.e. whether it is backed up in a Hotsync.
This control does not work for the *default* app.

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