Choices*set of system variables.
Choices:AppName.*must be used to read settings, and
<Choices$Write>.AppName.*must be used to save settings.
Choices:will usually be set by the system to a comma-separated list of paths to choices locations, with
<Choices$Write>at the beginning, so that any preferences that the user has saved are checked first.
Choicesfile run when the application is booted or run. The default settings are in the
!Runfile itself, and these are overridden by any user preferences by the final lines:
| Override with any local choices: /Z80Tube:X /Choices:Z80Tube.Choices
I have tweeked my version of
CPMFS to run a choices file.
The end of the
!Run file contains:
| Set any local choices: /CPMFS:Resources.X /Choices:CPMFS.Choices | /CPMFS:!RunImage %*0The Choices should be run before the !RunImage.
X command executes a command and ignores any
errors. It is best to not depend on the application running on a
system with an X command built in, so it is best to put an
X command in the application directory itself. You can
use and distribute this
here, which is 32bit clean, and also has a RISC
OS 4 header.
Choices:AppName.Run, etc. FTPc uses
When !Choices is run or Double-Clicked on, it sets the Choices: path to start with that !Choices directory. When !Choices is Double-Clicked on with Ctrl held down, it removes that !Choices from the Choices path. !Choices is available here:
X now has a RISC OS 4 header and should be correctly
validated on 32-bit systems.
Justin Fletcher has written a much better overview than I could on
Choices system in
document. (local copy).