Are "var" variables inside a paint routine inside a namespace leaky?

[d.healey]

@VirtualVirgin said in Are "var" variables inside a paint routine inside a namespace leaky?:

And given that the inline function works while breaking the paint routine in the other namespace would make it seem like the local "chordSymbol" variable is the one that is leaking...?

Did you try changing chordSymbol to a different name temporarily to see if the error goes away?

[ustk]

@VirtualVirgin Is the Paint Routine related the same panel that is in CSU?

If yes, then since you do:

panel.getValue().chordSymbol[row][col] = chordSymbol;

Shouldn't the proper way to get it back be:

var chordSymbol = this.getValue().chordSymbol[row][col];

And as Dave said, at least for a confusing reason, don't give the same name. chordSymbols[row][col] with an S seems more appropriate

[VirtualVirgin]

@ustk said in Are "var" variables inside a paint routine inside a namespace leaky?:

@VirtualVirgin Is the Paint Routine related the same panel that is in CSU?

If yes, then since you do:

panel.getValue().chordSymbol[row][col] = chordSymbol;

Shouldn't the proper way to get it back be:

var chordSymbol = this.getValue().chordSymbol[row][col];

They are completely different panels. Just the local use of "panel" for widgets.

[ustk]

@VirtualVirgin ok, so what is pads here .pads[row][col]? Does it hold a panel? because calling getValue() on it seems weird without knowing more...

[VirtualVirgin]

@d-healey said in Are "var" variables inside a paint routine inside a namespace leaky?:

@VirtualVirgin said in Are "var" variables inside a paint routine inside a namespace leaky?:

And given that the inline function works while breaking the paint routine in the other namespace would make it seem like the local "chordSymbol" variable is the one that is leaking...?

Did you try changing chordSymbol to a different name temporarily to see if the error goes away?

So I went through each line in the inline function and found the trouble.
One of the lines was returning an "undefined" because I did not initialize the data storage for it properly,
and once that was in the mix it threw errors for things down the line that were being loaded as persistent data.
The confusion occurred because the error that was coming up in the console is not where the root of the error was taking place,
just a subsequent error being caused by an external script getting detached I think.

TLDR - no leaky variables here.

[VirtualVirgin]

@VirtualVirgin said in Are "var" variables inside a paint routine inside a namespace leaky?:

@ustk said in Are "var" variables inside a paint routine inside a namespace leaky?:

@VirtualVirgin Is the Paint Routine related the same panel that is in CSU?

If yes, then since you do:

panel.getValue().chordSymbol[row][col] = chordSymbol;

Shouldn't the proper way to get it back be:

var chordSymbol = this.getValue().chordSymbol[row][col];

They are completely different panels. Just the local use of "panel" for widgets.

Yes, that is a panel.

[d.healey]

@VirtualVirgin said in Are "var" variables inside a paint routine inside a namespace leaky?:

The confusion occurred because the error that was coming up in the console is not where the root of the error was taking place,

Turning on stack trace in project preferences might help here.

[VirtualVirgin]

@d-healey I'm curious. Where do I find that feature? I'm looking in the Docs for "preferences" and not finding anything.

[d.healey]

@VirtualVirgin might be called call stack, it's in project preferences

[d.healey]

@VirtualVirgin This one

You might also simplify your code a little by using a helper function or two for your panel data management.

For example a generic function to set a property in your 3D array structure.

inline function setPanelData(panel, key, row, col, value)
{
    panel.getValue()[key][row][col] = value;
}