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,
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 , line 1
> > > Failed to execute command nasal
> > >
> > > on the console ;-) Something not commited ?
> >
> > Sounds li
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
fil
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) do
Andy Ross wrote :
> Frederic Bouvier wrote:
> > The only eye-candy I am getting pressing X is this :
> >
> > Nasal runtime error: no such member
> > at , line 1
> > Failed to execute command nasal
> >
> > on the console ;-) Something not commited ?
>
> Sounds like you are missing the Nasal/vie
Frederic Bouvier wrote:
> The only eye-candy I am getting pressing X is this :
>
> Nasal runtime error: no such member
> at , 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 y
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 th
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 chec
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 prope
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 Flig
10 matches
Mail list logo
