[Flightgear-devel] Re: nasal scripts

2006-03-06 Thread Melchior FRANZ
* Andy Ross -- Monday 06 March 2006 16:35: > Melchior FRANZ wrote: > > Justin Smithies wrote: > > > Nasal parse error: illegal character > > > > There's nothing wrong with line 2. > > There almost certainly is. I mean: nothing wrong with line 2 in what I posted, and in what he posted. Of course,

Re: [Flightgear-devel] Re: nasal scripts

2006-03-06 Thread Andy Ross
Melchior FRANZ wrote: > Justin Smithies wrote: > > Nasal parse error: illegal character > > There's nothing wrong with line 2. There almost certainly is. This error is really quite specific: the lexer found a byte that wasn't whitespace and wasn't a legal start of a symbol. I'd suggest attaching

[Flightgear-devel] Re: nasal scripts

2006-03-06 Thread Melchior FRANZ
* Justin Smithies -- Monday 06 March 2006 14:43: > I'm using the cvs version as updated today. Then you corrupted that code snipped when you copied it to that file, and some invisible character got added. There was a bug in some older KDE versions that did such. Check the engine.nas file. I hadn't

Re: [Flightgear-devel] Re: nasal scripts

2006-03-06 Thread Justin Smithies
I'm using the cvs version as updated today. I update my local cvs daily. Justin Smithies On Monday 06 March 2006 13:20, Melchior FRANZ wrote: > * Justin Smithies -- Monday 06 March 2006 14:15: > > Sorry im too keen got that all sorted just seem to have an error in line > > 2 ? > > > > last_cuto

[Flightgear-devel] Re: nasal scripts

2006-03-06 Thread Melchior FRANZ
* Justin Smithies -- Monday 06 March 2006 14:15: > Sorry im too keen got that all sorted just seem to have an error in line 2 ? > > last_cutoff = 0; >   setlistener("/engines/engine[0]/cutoff", func { There's nothing wrong with line 2. But I get the impression that you are not running fgfs from C

Re: [Flightgear-devel] Re: nasal scripts

2006-03-06 Thread Justin Smithies
Sorry im too keen got that all sorted just seem to have an error in line 2 ? last_cutoff = 0;   setlistener("/engines/engine[0]/cutoff", func {           var new_cutoff = cmdarg().getBoolValue();           if (new_cutoff and !last_cutoff) {                   setprop("/engines/engine[0]/reversed",

[Flightgear-devel] Re: nasal scripts

2006-03-06 Thread Melchior FRANZ
* Justin Smithies -- Monday 06 March 2006 14:07: > Getting errors saying it could not read script file engine.nas into module > engine. Then this file isn't in the right place. > Could it be that the values for the cuttoff and reverse should be true or > false not 0 or 1 . no. >Aircra

[Flightgear-devel] Re: nasal scripts

2006-03-06 Thread Melchior FRANZ
* Justin Smithies -- Monday 06 March 2006 13:58: > Sorry to trouble you again Melchior FRANZ, > But how do i get this script to run in FG ? > > What do i place in the 737-300-set.xml file to make this nasal script active ? > I called the file engine.nas Just look at how the 737 does it already! I

Re: [Flightgear-devel] Re: nasal scripts

2006-03-06 Thread Justin Smithies
Getting errors saying it could not read script file engine.nas into module engine. Could it be that the values for the cuttoff and reverse should be true or false not 0 or 1 . If so can you rewrite that script so if i change ( toggle ) cutoff from false to true and visaversa it will write to th

Re: [Flightgear-devel] Re: nasal scripts

2006-03-06 Thread Justin Smithies
Sorry to trouble you again Melchior FRANZ, But how do i get this script to run in FG ? What do i place in the 737-300-set.xml file to make this nasal script active ? I called the file engine.nas Regards, Justin Smithies On Monday 06 March 2006 12:45, Melchior FRANZ wrote: > * Justin Smithies --

[Flightgear-devel] Re: nasal scripts

2006-03-06 Thread Melchior FRANZ
* Justin Smithies -- Monday 06 March 2006 13:40: > But just to get me going could you write it out as if it > was doing the following in script form. > That should help me heaps to understand this and keep me busy too ;) > > Say i wanted to monitor the /engines/engine[0]/cutoff property. > If it

Re: [Flightgear-devel] Re: nasal scripts

2006-03-06 Thread Justin Smithies
Hey thanks, But just to get me going could you write it out as if it was doing the following in script form. That should help me heaps to understand this and keep me busy too ;) Say i wanted to monitor the /engines/engine[0]/cutoff property. If it ever changed to true i woul

[Flightgear-devel] Re: nasal scripts

2006-03-06 Thread Melchior FRANZ
* Justin Smithies -- Monday 06 March 2006 13:15: > Is it possible to have a nasal script running and waiting for an event to > happen , say watching a switch then if the condition is met do the required ? setlistener("/some/switch", func { if (cmdarg().getBoolValue()) {