Josh Babcock wrote:
> I don't have a problem with fg putting stuff into my preferences.xml,
> that is a pretty common practice with configuration software. The
> problem is the stuff it took out.
> And to add insult to injury, the idea of persistent configuration
> changes is good, but it looks like I can't take advantage of it unless I
> give up my custom configuration.
You already can. Just rename your custom config to myprefs.xml and start
fgfs with --config=~/.fgfs/myprefs.xml.
FG would still use the ~/.fgfs/preferences.xml for options saving.
Sorry, that I caused you trouble. I derived the name from the global
preferences.xml and did not give much thought about it, as I didn't
think the code would be included so soon. Nowadays I'd probably call it
~/.fgfs/options-autosave.xml so chance of clashing with existing files
should be negligible.
Oh, and one can edit that file manually: all properties that get loaded
from there get their userarchive flag set, so they are written back on
exit. But their value will be the last value they got in the running
program, so this is mainly useful, if one wants to have additional
properties saved (for example radio settings).