On Wed, 10 Mar 2010, James Turner wrote: > Maybe my comment about 'changed from Nasal' was misleading, I'm not > really suggesting these properties particularly need to be dynamically > configured, but for example it does mean the values can be tweaked in > the Property Inspector during aircraft development. With your original > code, changes made that way will not be picked up. Obviously 99% of the > time the values would come from instrumentation.xml as you intended.
I don't know much about modern avionics but it seems reasonable that the trigger points of over-speed and/or under-speed warnings could change with the current aircraft configuration and that these changes could be reflected on the airspeed indicator. I'd vote for keeping these parameters changeable at runtime. Cheers, Anders -- --------------------------------------------------------------------------- Anders Gidenstam WWW: http://www.gidenstam.org/FlightGear/ ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
