On Wed, Nov 5, 2008 at 3:20 PM, Curtis Olson <[EMAIL PROTECTED]> wrote: > What is the proper mechanism for calling nasal initialization code in an > aircraft specific nasal file. > > I see that core nasal code sets a listener on > /sim/signals/nasal-dir-initialized however, I don't really care when the > nasal-dir is initialized for aircraft specific code since it doesn't live in > the main nasal directory. Would it be nitpicky of me to ask what it means > to initialize a directory? Is there a corresponding unix system call for > instance? :-)
Slight misnomer, not the directory is initialized of course. Rather, the signal means all the modules in the nasal dir are loaded and ready to use. > So is there a "proper" way to do this. I understand the old "set timer" > mechanism is discouraged. Preferably you should wait for a signal that whatever features you want to use are ready. If you *use* any modules from the common nasal directory (including props.nas!) you should wait for the nasal-dir-initialized. If you depend on fdm properties, you should wait for fdm-initialized, and so on. Disclaimer: I am not *the* expert on this, but since nobody answered yet, I thought I'd give you my understanding of the situation :) -- Csaba/Jester ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
