* Curtis Olson -- Saturday 14 February 2009:
> No I think Melchior is justified (as occasionally can be the case) :-)
:-P
> We could simply default wild fires to off in the preferences.xml file and
> that is perhaps the thing to do.
Exactly, and as I've said before:
| Melchior FRANZ -- Saturday 14 February 2009:
| * gerard robin -- Saturday 14 February 2009:
| > Won't it be better to have it default "false" ?
|
| Yes.
^^^
And not because it's too "game-like", but because it lowers the frame
rate much too much and has a tendency to grow out of hands.
If some people here were less blinded with their private crusade and
gave reason a chance, at least once in a while, then they would have
understood. But I see that this is hard. :-}
The wildfire setting is saved to autosave.xml, and it's up to the
user to decide whether he wants it or not. It's not something that
an aircraft developer may decide. What if the next aircraft
feels like turning off metar? What if one decides that flying
at night is nicer, and just switches to midnight? What if some
aircraft developer thinks his aircraft should only fly in LFPO?
One would assume that the problem is obvious enough for anyone.
m.
PS: Yes, I've announced a while ago that I would no longer care
about what aircraft developers do, if they mess everything up
or not. Sorry about that little mistake.
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
