memory, buffered images and closed stacks (and groups?)

[Ken Ray]

On Jul 29, 2011, at 12:27 AM, Nicolas Cueto wrote:

> Hello.
> 
> Actually, this is about a crash caused by the command "group". Which I
> explain further down. But first...
> 
> How can I make sure that a closed stack releases all memory, i.e.,
> that the stack is "really" closed?

You can do one of the following:

1) Set the 'destroyStack' property of the stack to true. WHen it closes, it should be purged from memory.
2) Issue the "delete stack <stackname>" command, but BE CAREFUL!!! - if <stackname> is a *substack*, the stack will ACTUALLY BE DELETED; if the stack is a *mainstack*, it will close the stack and remove it from memory. (I tend to use something like "if the mainstack of <stack> = the short name of <stack> then delete stack <stack>".)

The way you can test is to look at "the mainstacks".... if the name of the stack is no longer in "the mainstacks", then it has been closed and purged from memory.

Ken Ray
Sons of Thunder Software, Inc.
Email: kray at sonsothunder.com
Web Site: http://www.sonsothunder.com/