* Sébastien MARQUE -- Sunday 15 February 2009: > I'm quite "surprised" not to see someone purpose an other solution which > is only to override wildfire.ignite() function in a single aircraft, as > we are used to do for brakes, or starting engines.
That's because this is *still* wrong. This is a gui setting, and the user sets it as s/he likes it. What if the user has decided that s/he *wants* fire? What's wrong with respecting the users' wishes? It's true, of course, that the wildfire should be intelligent enough to not ignite if there's no fuel on board (gliders, empty tank), or if the kind of crash doesn't justify fire. But we've discussed that on IRC a few times already, and everyone (including the author) agreed with it. It just has to be done yet. May I remind people that CVS/HEAD is about development? Nothing there needs to be perfect already. (And nothing is. ;-) If you don't want the fire in the development version, just turn it off on your machine. Is this such a problem?! m. ------------------------------------------------------------------------------ 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
