Inconsistent preset behavior #44
Description
There is inconsistency between how the CLI and TUI behavior with regards to presets.
- When using the TUI, it will currently preserve the volatile state of the currently selected preset, but when switching to another preset, the non-volatile state will be used.
- When using the CLI, the non-volatile state will always be used.
The CLI and TUI should both offer options to load from volatile and non-volatile states of a given preset.
To support this a --recall option should be introduced (alongside of --preset) which will be used to recall the volatile state via the CLI.
By default, when using the TUI, the volatile state should be used to allow a user to pick-up where they last left off.
CAUTION (NEEDS MORE CONSIDERATION)
The TUI should support a key-stroke (Shift+0-9) to restore the preset from its non-volatile state.
Keys 0-9 will be used to recall the last volatile state of the preset.
Since this changes the default TUI behavior, we should consider introducing a warning-notice mechanism that is activated on first launch of this new build. Once dismissed, the user-settings will save an acknowledgement state and no longer display the notice.
Also consider adding a soft-reset of the presets to their non-volatile state via an option.