On Tue, Aug 7, 2012 at 6:36 AM, Wolfgang Rostek wrote:
> Hi all,
>
> I was playing around with two different scenery directories.
>
> It takes me some time to recognize that the value from ~/.fgfsrc
> is used and not the command line parameter 'fgfs --fg-scenery=...'
> in the first place.
>
> What are the rationale to give the command line parameters not
>
Hi Wolfgang,
I'm pretty sure our intention is for the command line to take priority over
the "dot" file options which in turn take priority over the preferences.xml.
But a while ago we redid the option parsing system and it may be possible
there are some rare usage cases that still aren't quite right. Taking a
quick peek at the code, it appears that no matter what, options are
appended to the scenery path in the order the system reads the option
sources (which may not be in order of precedence?)
I did a quick test here and it does look like we have the backwards --
although it's not obvious from the code if there is a quick fix. James is
the one who redid the option parsing (and I know he's busy with some MacOS
release work) but this one might end up on his plate to puzzle through.
Curt.
--
Curtis Olson:
http://www.atiak.com - http://aem.umn.edu/~uav/
http://www.flightgear.org - http://gallinazo.flightgear.org
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Flightgear-users mailing list
Flightgear-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-users
