Basic CLI config handling #23
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allows for specifying configuration options via CLI arguments,
Should in theory work with most Serializable options in
ShowConfiguration.cshowever I have not tested "complex" data structures.Config is stacked in the following order, with 3 taking priority over 2, and 2 priority over 1:
-config-file=<path>-config-<option>=<value>Loading a configuration file with the UI will override all configured launch configuration options set via launch flags.
Also note the
ReadCLIConfig()call at the start is to fix a race condition with having no Config file set in flags,It gets re-applied after the initial Config file load via
-config-file, load button doesn't do this.EXAMPLE:
-config-file=configfile.shwcfg --config-targetframerate=120(yes it handles both single and double dashes, for flexiblity)