Hi,
switching between FG2.4.0 and next/2.5.0 it really annoyed me to get the
preferences mixed up. Currently we store all settings in one directory
("$(HOME)/.fgfs", different name for Windows). This can cause issues
when running different fgfs version on a single machine. The default
values for the preferences are stored in the base package
(preferences.xml). But users upgrading FG only get the default values of
new properties of FG2.4 - while all existing properties keep the values
of FG2.0.0. Sometimes this works (TM), sometimes this is weird.
I have a patch appending the base package version to the .fgfs directory
- so FG 2.5.0 would use ".fgfs-2.5.0/...", which keeps the configuration
for each FG version separate. I think for the average user that's
better, since they start off with clean/default settings when switching
to a new FG version. Also, this excludes any risk of interference when
multiple FG versions are used on a single machine.
I would push that patch to git/next - but am open for discussion.
cheers,
Thorsten
------------------------------------------------------------------------------
FREE DOWNLOAD - uberSVN with Social Coding for Subversion.
Subversion made easy with a complete admin console. Easy
to use, easy to manage, easy to install, easy to extend.
Get a Free download of the new open ALM Subversion platform now.
http://p.sf.net/sfu/wandisco-dev2dev
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
