On 30 Oct 2011, at 11:49, Durk Talsma wrote: > It turns out that I had the option --time-match-local included in my .fgfsrc > file. Commenting out this option from .fgfsrc makes both --timeofday=dawn, > as well as --start-date-gmt work again. Originally, the order of precedence > was that command line options specified in .fgfsrc should be overridden be > values specified on the command line, so in this particualr case, --timeofday > should override --time-match-local. I haven't tested --start-date-gmt yet, > but I assume that a similar problem occurs here. My tests sofar point to > commit b1c7495 (Sunday Oct 16: 19:35), as the commit where overriding the > --time-match-local option stopped working. I had a quick glanch at the > changes but haven't been able to determine how this may happen. I hope that > James has some ideas.
Right, and that's definitely still the case - the 'code' order has changed, but the end result should be identical - .fgfsrc over-rides system.fgfsrc, and the command line over-rides either. And I did quite a bit of testing of that before committing the changes - admittedly using --aircraft and --airport, but it 'should' be the same for any other option. Clearly my 'should' is not working out as planned :) Just to be clear, this isn't a case of specifying the same option in multiple places - you're using two different options, but relying on one to cancel out the other? James ------------------------------------------------------------------------------ Get your Android app more play: Bring it to the BlackBerry PlayBook in minutes. BlackBerry App World™ now supports Android™ Apps for the BlackBerry® PlayBook™. Discover just how easy and simple it is! http://p.sf.net/sfu/android-dev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
