20,741
edits
Using listeners and signals with Nasal: Difference between revisions
Jump to navigation
Jump to search
m
Using listeners and signals with Nasal (view source)
Revision as of 19:36, 19 May 2013
, 19 May 2013→Signals: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg13022.html
m (→Signals: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg13022.html) |
|||
| Line 191: | Line 191: | ||
* <tt>/sim/signals/reinit-gui</tt> ... set to "true" when the GUI has just been reset (e.g. via Help menu). This is used by the gui.Dialog class to reload Nasal-loaded XML dialogs. | * <tt>/sim/signals/reinit-gui</tt> ... set to "true" when the GUI has just been reset (e.g. via Help menu). This is used by the gui.Dialog class to reload Nasal-loaded XML dialogs. | ||
* <tt>/sim/signals/frame</tt> ... triggered at the beginning of each iteration of the main loop (a.k.a. "frame"). This is meant for debugging purposes. Normally, one would just use a settimer() with interval 0 for the same effect. The difference is that the signal is guaranteed to be raised at a defined moment, while the timer call may change when subsystems are re-ordered. | * <tt>/sim/signals/frame</tt> ... triggered at the beginning of each iteration of the main loop (a.k.a. "frame"). This is meant for debugging purposes. Normally, one would just use a settimer() with interval 0 for the same effect. The difference is that the signal is guaranteed to be raised at a defined moment, while the timer call may change when subsystems are re-ordered. | ||
=== Nasal code coupled to the autopilot system === | |||
Some FDM stuff would like to be tied to the FDM update rate, and that's a desirable goal. What about a callback function then? The FDM subsystem would set /sim/signals/fdm-update, and you could attach a listener to that which does all the things that should interact with the FDM, such as AP, FCS, etc. The rest of Nasal would keep running with the frame rate. | |||