Hey, * Sébastien MARQUE -- 2/23/2009 11:01 PM: > you can find the patch with, I hope, the correct improvement you asked.
Yes, thanks. I do currently not have access to my machine, but will commit in a few days if nobody is quicker. (Temporary variable names with a scope of just three lines should be shorter, but that's now *really* just nitpicking. :-) [change-only listeners] > Be sure that I'll be aware and will recall you of this change if one day > we run into problems, and no-one remembers about it before ;) I seem to remember that the current behavior is even "by design", and not a bug. OK, it probably qualifies as usability or consistency bug. I'll have a look at that, too. > Now I'm going to continue my tries about failures scenarii. The dialog should IMHO be done with XML-embedded Nasal in a regular dialog file, not as pure Nasal code in a *.nas file. This has two advantages: the dialog can easily get reloaded during development, and it doesn't fill up Nasal files with verbose and boring dialog generation code. I find it nicer to get this out of the Nasal files and to keep their focus more on "library" functionality. You can easily use template XML code that you copy and modify. Some dialogs do that already. m. ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
