Erik Hofman wrote:
David Culp wrote:
Unable to read submodels file:
/home/dave/FlightGear/data/Aircraft/FW190/submodels.xml
Did you already load the file in your browser to see if it's XML compliant?
I would like to suggest adding an optional --validate-xml option to
FlightGear, while this would be mainly used by developers, it could
certainly reduce the amount of debugging efforts in that regard.
During my instrument design efforts I noticed a couple of problems
related to (accidentally) invalid XML files - e.g. FG starts happily
(and that takes some time !) just in order to tell me *then* that
there were parsing errors in some XML file ...
What surprised me a bit: I couldn't even use the menubar after a
parsing error in an instrument definition file ...
(No, I didn't touch the menubar.xml file=)
One would probably only have to tell expat to optionally validate
the xml files that it is supposed to parse.
We could agree on specifying different validation levels, so that
one could optionally only validate the fundamental files like
preferences.xml, menubar.xml or additionally also make FlightGear
check all XML files within the Aircraft sub-folder of a chosen
aircraft.
What do you think ?
And before anybody yells at me: As long as others also think
that it might be useful, I would not mind looking into it.
----------
Boris
P.S.: Is there any way to make FG reload its textures
(i.e. panel/instruments) - I didn't seem to find one,
and if I understood the sources correctly, each texture
is only loaded ONCE, without the possibility to reload
it ?
If that's true, I would also like to see a new fgcommand
to re-load textures: it's a bit awkward during panel/instrument
design to have to restart FG only to see the changes take effect,
I think the panel/instrument/aircraft desginers probably agree ?
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
