Configuration file

[djh0ffman]

Allow the user to configure PT-1210 with an .INI-format configuration file that's human-readable and easy to edit with standard Amiga or PC text editors.

Idea: could these options be mirrored in icon ToolTypes, too? Perhaps ToolTypes would take priority, followed by config file, followed by default values.

Initial list of options to implement (checked = implemented):

general

• splash: Enable splash screen on startup (on/off, default: on)
• close_wb: Attempt to close Workbench when PT-1210 starts (on/off, default: off)

dir_cache

• mode: Set directory caching mode: 0 = disabled, 1 = auto, 2 = manual (0/1/2, default: 1)
• whitelist: Comma-separated list of paths to include when caching (manual mode only) (default: empty)
• blacklist: Comma-separated list of paths to exclude when caching (manual and automatic modes) (default: Ram Disk:*)

player

• soft_nudge_bpm: BPM to add/subtract when using the 'soft' nudge function (default: 1)
• hard_nudge_bpm: BPM to add/subtract when using the 'hard' nudge function (default: 6)

keyboard

• repeat_delay: Amount of time, in milliseconds, that a key must be held before it repeats (default: 500)
• repeat_rate: Period, in milliseconds, at which a held key repeats (default: 1000)

gameport

• port_0_mode: Mouse port mode: 0 = disabled, 1 = auto detect, 2 = force joystick, 3 = force CD32 pad. (0/1/2/3, default: 0)
• port_1_mode: Joystick port mode: 0 = disabled, 1 = auto detect, 2 = force joystick, 3 = force CD32 pad. (0/1/2/3, default: 1)

bindings

• A list of keyboard/joystick action bindings in some reasonable format.
  Example: LEFT_SHIFT + UP = pitch_up_fine
  This section should contain the entire default binding list, maybe commented out so the user can easily tweak as they please. PT-1210 will contain the default bindings internally in case that a config file is not found. If this section contains at least one valid binding, the internal defaults should be ignored, and it's then on the user to map all the keys they want in this file.