Template:IO Restrictions: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
<font color="red"><b>Note:</b> All FlightGear disk I/O handled via [[Nasal]] and/or fgcommands, is subject to validation via [[IOrules]]. This includes the '''SGPath''' bindings in FlightGear 2.99+</font> | <font color="red"><b>Note:</b> All FlightGear disk I/O handled via [[Nasal]] scripting and/or [[Howto:Add new fgcommands to FlightGear|fgcommands]], is subject to validation via [[IOrules]]. This includes the '''SGPath''' bindings in FlightGear 2.99+</font> | ||
However, unlike [[$FG_ROOT]], [[$FG_HOME]] is generally accessible for writing, consider this example: | However, unlike [[$FG_ROOT]], [[$FG_HOME]] is generally accessible for writing, consider this example: | ||
Revision as of 15:25, 20 December 2013
Note: All FlightGear disk I/O handled via Nasal scripting and/or fgcommands, is subject to validation via IOrules. This includes the SGPath bindings in FlightGear 2.99+
However, unlike $FG_ROOT, $FG_HOME is generally accessible for writing, consider this example:
# come up with a path and filename in $FG_HOME, inside the Export sub folder, file name is test.xml
var filename = getprop("/sim/fg-home") ~ "/Export/test.xml";
# use the write_properties() helper in io.nas, which is a wrapper for the savexml fgcommand (see README.commands)
io.write_properties( path: filename, prop: "/sim" );This will dump the sub branch of the /sim property tree into $FG_HOME/Export/test.xml
For additional examples, see $FG_ROOT/Nasal/io.nas To learn more about PropertyList processing via loadxml and savexml, please see $FG_ROOT/Docs/README.commands