Jim Wilson writes:
> There must be a reason for not having it hard coded, but I can't
> think of what it would be. Is this just to make minor
> spelling/syntax corrections without rebuilding...or are you looking
> toward supporting multiple languages?
It would be interesting to make options themselves configurable, as
in
<PropertyList>
<option>
<name>heading</name>
<arg>true</arg>
<property>/orientation/heading-deg</property>
<description>Initial heading in degrees true.</description>
</option>
<option>
<name>pitch</name>
<arg>true</arg>
<property>/orientation/pitch-deg</property>
<description>Initial pitch in degrees true.</description>
</option>
<option>
<name>disable-panel</name>
<arg>false</arg>
<property>/sim/panel/visibility</property>
<value>false</value>
<description>Hide the control panel on startup.</description>
</option>
<option>
<name>enable-panel</name>
<arg>false</arg>
<property>/sim/panel/visibility</property>
<value>true</value>
<description>Show the control panel on startup.</description>
</option>
<!-- and so on -->
</PropertyList>
It would be much easier to keep the help text up-to-date this way,
though a few of the options would be trickier (the ones that require
special parsing of the argument, for example). Any volunteers?
All the best,
David
--
David Megginson, [EMAIL PROTECTED], http://www.megginson.com/
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
