4,400
edits
Reset & re-init: Difference between revisions
Jump to navigation
Jump to search
m
Update forum links
m (Update forum links) |
|||
| Line 52: | Line 52: | ||
* Dynamic switching of aircraft (saving/loading flights [https://code.google.com/p/flightgear-bugs/issues/detail?id=1151#c1]) | * Dynamic switching of aircraft (saving/loading flights [https://code.google.com/p/flightgear-bugs/issues/detail?id=1151#c1]) | ||
** Since the property tree will be rebuilt, we can safely read a different -set.xml file without the universe imploding. | ** Since the property tree will be rebuilt, we can safely read a different -set.xml file without the universe imploding. | ||
* Restarting of Nasal (re-read scripts on the fly, also see [[Nasal Events]] [http://flightgear.org | * Restarting of Nasal (re-read scripts on the fly, also see [[Nasal Events]] [http://forum.flightgear.org/viewtopic.php?f=30&t=19487] [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg36668.html]) | ||
** Since it's a new property tree, we have to destroy and restart the Nasal context anyway. This should greatly simplify aircraft Nasal script development. | ** Since it's a new property tree, we have to destroy and restart the Nasal context anyway. This should greatly simplify aircraft Nasal script development. | ||
* Separate startup GUI frontends like fgrun may become obsolete or at least optional eventually, because FlightGear itself would become increasingly runtime-configurable ([[FlightGear Sessions#The FlightGear Frontend Debacle|we have about 10-15 GUI launchers for FG currently]]). | * Separate startup GUI frontends like fgrun may become obsolete or at least optional eventually, because FlightGear itself would become increasingly runtime-configurable ([[FlightGear Sessions#The FlightGear Frontend Debacle|we have about 10-15 GUI launchers for FG currently]]). | ||