The Tone'ster writes: > Applied to these documents seperately, we would end up with a > intersection of a number of named elements.
Overall, you end up with the union of all the properties in the different files, with the values loaded later overriding those loaded earlier. > a) render a GUI exposing these values ... > b) allow a user to change these values and persist them > > ... then ... > > a) do I "merge" these values into a final DOM, where the last entry > "wins" and where load order is important ? I'd avoid the DOM and stick with the SimGear property code -- it will make your life a lot easier. > b) where do I persist the change ? > > to the "aircraft" ? to the "preferences" ? You should probably save to a config file in the user's home directory rather than trying to save the preferences globally. 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
