Re: [Flightgear-devel] location dialog
Andy Ross wrote: I wrote: I have some modifications in the works that will allow you to create new dialogs dynamically with a dialog-new command. You can then generate a SGPropertyNode dynamically or just use one in the global tree and modify it as you like before generating the dialog. OK, this is checked in now. Take a look at the view.nas module for a demonstration. The new zoom key bindings now dynamically calculate minimum/maximum bounds for the FOV and pop up a tiny dialog indicating the new FOV value. After one second, it automaically disappears. Let me know if you hate the eye candy. Andy, The only eye-candy I am getting pressing X is this : Nasal runtime error: no such member at command, line 1 Failed to execute command nasal on the console ;-) Something not commited ? ( compiled on windows with MSVC ) -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] location dialog
Frederic Bouvier wrote: The only eye-candy I am getting pressing X is this : Nasal runtime error: no such member at command, line 1 Failed to execute command nasal on the console ;-) Something not commited ? Sounds like you are missing the Nasal/view.nas file in your base package. If you don't use the -d option to cvs update, you probably don't have the (relatively new) Nasal directory yet. Andy ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] location dialog
Andy Ross wrote : Frederic Bouvier wrote: The only eye-candy I am getting pressing X is this : Nasal runtime error: no such member at command, line 1 Failed to execute command nasal on the console ;-) Something not commited ? Sounds like you are missing the Nasal/view.nas file in your base package. If you don't use the -d option to cvs update, you probably don't have the (relatively new) Nasal directory yet. No, it is there. Could the parser be screwed by line endings ? -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] location dialog
Frederic Bouvier wrote: Andy Ross wrote: Sounds like you are missing the Nasal/view.nas file in your base package. No, it is there. Could the parser be screwed by line endings ? No, carriage returns are just whitespace to Nasal. And the script source in question (in keyboard.xml) doesn't even have any line endings. It looks like this: scriptview.increase()/script The no such member error, in this context, can only mean that there is no view module or that it contains no symbol named increase. Are you sure you don't have any other changes (cvs collision garbage, extra files, miscellaneous typos...) that might be causing a Nasal initialization error? Is there nothing printed to the console on startup? Andy ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] location dialog
Frederic Bouvier wrote: Bingo ! Just retried with line endings converted to unix for all .nas and it works That's not a solution, that's a bug. :) Nasal shouldn't care about line endings. Things seem to work fine for me when I try \r\n line endings on my Linux box. Can you send me the files you have which aren't working? Andy ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] location dialog
I wrote : Andy Ross wrote : Frederic Bouvier wrote: The only eye-candy I am getting pressing X is this : Nasal runtime error: no such member at command, line 1 Failed to execute command nasal on the console ;-) Something not commited ? Sounds like you are missing the Nasal/view.nas file in your base package. If you don't use the -d option to cvs update, you probably don't have the (relatively new) Nasal directory yet. No, it is there. Could the parser be screwed by line endings ? Bingo ! Just retried with line endings converted to unix for all .nas and it works -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] location dialog
Andy Ross wrote: Nasal shouldn't care about line endings. Things seem to work fine for me when I try \r\n line endings on my Linux box. Can you send me the files you have which aren't working? Found it. The bug was with the byte index - line table creation. Due to an extra increment, DOS files would look like they were all on one line. They would still parse correctly, but any comments would skip to the end of the file. Most of my test code doesn't have comments. :) Fixed in SimGear. Andy ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] location dialog
Curtis L. Olson wrote: Is there a way to preset certain property values when opening up a dialog box? I see that we can force arbitrary property values when clicking ok, but it would be nice to force some default values when a dialog box is opened. Not right now, unfortunately. The property trees defining the dialog objects don't live in a place where you can find them. I have some modifications in the works that will allow you to create new dialogs dynamically with a dialog-new command. You can then generate a SGPropertyNode dynamically or just use one in the global tree and modify it as you like before generating the dialog. None of this is Nasal-specific. But that would, of course, be the obvious choice for such work. :) Andy ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] location dialog
I wrote: I have some modifications in the works that will allow you to create new dialogs dynamically with a dialog-new command. You can then generate a SGPropertyNode dynamically or just use one in the global tree and modify it as you like before generating the dialog. OK, this is checked in now. Take a look at the view.nas module for a demonstration. The new zoom key bindings now dynamically calculate minimum/maximum bounds for the FOV and pop up a tiny dialog indicating the new FOV value. After one second, it automaically disappears. Let me know if you hate the eye candy. Andy ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] location dialog
Is there a way to preset certain property values when opening up a dialog box? I see that we can force arbitrary property values when clicking ok, but it would be nice to force some default values when a dialog box is opened. Thanks, Curt. -- Curtis Olson HumanFIRST Program FlightGear Project Twin Citiescurt 'at' me.umn.edu curt 'at' flightgear.org Minnesota http://www.flightgear.org/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
