chrisb wrote: ↑Fri Aug 19, 2022 12:55 pm
I admit that I have abused the "Save new" function from the preferences. It created the structure and I could replace the contents of the xml file.
I just create a random named directory in the Mod directory. In it I added a directory called PreferencePackTemplates. In it I added my .cfg file.
When I tried Save new, it did find and add my .cfg to the list of params to save.
the .cfg file contents:
Code: Select all
<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<FCParameters>
<FCParamGroup Name="Root">
<FCParamGroup Name="BaseApp">
<FCParamGroup Name="Preferences">
<FCParamGroup Name="General">
<FCText Name="AutoloadModule">PartDesignWorkbench</FCText>
</FCParamGroup>
<FCParamGroup Name="MacMods">
<FCText Name="MacString">Test MacModString</FCText>
</FCParamGroup>
</FCParamGroup>
</FCParamGroup>
</FCParamGroup>
</FCParameters>
The template created with this .cfg unchecked didn't include the General group or MacMods. As expected.
Creating the template with it checked produced:
Code: Select all
...
<FCParamGroup Name="General">
<FCText Name="AutoloadModule">SMWorkbench</FCText>
</FCParamGroup>
<FCParamGroup Name="MacMods">
<FCText Name="MacString">Test MacModString</FCText>
</FCParamGroup>
</FCParamGroup>
...
SMWorkbench is what is currently set in the preferences.
But, the value specified in the .cfg was PartDesignWorkbench
This seems anomalous behaviour.
But, also, how would one effect the changing of parameters (since it seems the value is taken from the current state, not as specified in the .cfg.)?
Star Trek II: The Wrath of Khan: Spock: "...His pattern indicates two-dimensional thinking."