> I assumed that the function should also be accessible via other > means than just the dialog (e.g. keyboard bindings). If not, > then I absolutely agree with your change. That's the cleanest way. I'll leave this to the original author (Gijs) if he wants to extend the functionality that way. If so, we might think about a more global solution. > > Yes. All local variables in dialog embedded Nasal are put in > a separate module, and this is destroyed on closing. The only > two things that one has to care for are timer loops and > listeners. These should be stopped/removed manually. OK, thanks. That makes things somewhat clearer for me. What I observe is, that, if the dialog gets closed while the towtruck is moving (the door-object is interpolating), the truck (door) keeps moving until it reached its final position. Probably because the underlying interpolate() function keeps running until its finished. I don't think that should get us into any trouble...
BTW: I just played with the pushback feature for the Hansa Jet - a little bit oversized... http://www.t3r.de/fg/hansajet_with_pushback.jpg http://www.t3r.de/fg/hansajet_with_pushback_2.jpg Torsten ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
