Free Flight, Free Speech

Okay, Nasal is giving me a headache again. I am in a Nasal class ...



You can see I defined txtAltHold
later in a method called "init"
comes


it obviously works because when I bring the dialog up, the field shows. Now, here begins the drama. I can't find any event type, I can listen to for a lineEdit-widget. So I have to poll it. I set me a timer and ...



I get the printed message, then boom ... Nasal runtime error: undefined symbol: txtAltHold
at /home/peter/flightgear/fgdevelopment/Aircraft/JPack/Voodoomaster/Dialogs/autopilot9_1.nas, line 1002

I tried also instead me.txtAltHold ... then it says "me" is undefined.
any idea what's wrong? Help is appreciated, I am total rusty after months of absence.

come on Mumble

I'd be happy to help if I can

I see a scope issue here. I do not know nasal, but generally it works like this: Variables scoped at class level can be reached via "me" in methods of that class.

What is see here is:

- in init the variable assigned is local to the method (no me used)
- i do not know where that function "update" is, but if it is a method in that class, you should definitely use me
- if it is outside the class, you need to instantiate the class and use the handle to it in the way you use me

Kind regards, Vincent

Well if's undefined, try to see where that is defined. If it is defined above all classes, then it should work everywhere. If it's defined inside a specific class, then it won't work in all classes.

Yeah, it is defined in THE SAME class as the method that throws the erroe. And while I usually don't need an explicit me if I am in the same class, I tried that too. Same error. So I can't access it with me nor without, I can though access it in init where I instantiated it with and without me.

I would go for consistently using me in methods for class level variables and try to get it to work. That is to rule out any scope issues.

I also see update calling update recursively. Check if it does not get in a endless loop. It is one of the most common causes of "boom".

Kind regards, Vincent

It doesn't go in an endless loop. it just resets the event that calls it for the next call. And no it can't go in an endless loop at this time because it still crashes
And I used consequently me only the Nasal interpreter didn't like that either. Since Nasal isn't maintained since some years anymore, we don't know what strange things lurk there and it looks more and more as if I found one. Here is the thing ...

if I define a pointer variable ...

myPointer: nil,

on class level and then doe the new in a method, it seems to establish a copy of it on method level, like a local pointer variable. Not sure why, I still hope, I only messed somewhere up.