Globals and clone this stack

[Mag]

Hi all!

If I clone a stack the new instance of the stack uses the same globals, right? And if I would like to have different globals in each instance of the stack?

[Klaus]

Hi Mag,

globals are... well, globals! No way!

Maybe you can "get away" with LOCAL vars in the stack script?


Best

Klaus

[FourthWorld]

If you need values specific to the stack you could use custom properties, effectively binding the data to the object.

[Mag]

Thank you Klaus, I will examine the possibility to implement local vars...

FourthWorld nice idea, are the custom propperties a lot slower than globals?

[FourthWorld]

FourthWorld nice idea, are the custom propperties a lot slower than globals?

Measurably, but rarely noticeably.

[Mag]

Thank you for the info guys!

And if I have two instances of the same main stack (called for example "MyStack"), each one with their substacks, when I set a custom property for the stack MyStack from within a substack, can I be sure that the property set is the one of the current mainstack?

PS
I know, not an easy question...

[Mag]

PS
I noticed that the substacks are not cloned with the main stack. So if I have to set a custom property of a main stack cloned from a substack, I have to know the name of it. This because the substacks continues to own by the original stack.

[FourthWorld]

After executing a "create" or "clone" command, the value on the local variable"it" will contain a absolute reference to the new object.

[Mag]

Thank you Richard!