Giles Robertson forgot to use his enter key and wrote:
I don't think we will hit the limit for a long time.
> I suppose, if you used lots of property commands, you could already
> overfill it, but it shouldn't be an issue.
exactly, whenever there's really the need to put that much stuff into
the property tree or generally to provide that many parameters to
FlightGear, there are still better options for those scenarios:
Properties can also be set easily once FG has started up by using
either the GUI property browser or alternatively by using the
httpd/telnetd facilities.
Command line parameters can still easily be provided, too - probably
up to an abitrary amount ? - by using the corresponding fgfsrc file
for your specific platform.
On the other hand things like texture complexity/choice are probably
still best to be changed from within FG, so that these options are
self-explanatory and easily accessible for everybody.
Depending on what exactly Paul had in mind, one could already start to
provide the corresponding XML dialogs for such settings and then take
care of the necessary changes within the code to actually make use of
such new properties.
----------
Boris
_______________________________________________
Flightgear-users mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d
