"Deleting" Stacks in Memory - What About Behaviors?
J. Landman Gay
jacque at hyperactivesw.com
Fri Feb 10 13:27:52 EST 2017
How would the engine know whether that behavior is used elsewhere, or will
be needed in the stack that opens next? The easiest way to get the behavior
you want, without any scripting, is to put the script in a button in the
stack. Then when the stack is deleted, the behavior is gone.
If you're using script only stacks, it's not difficult to remove the script
stack when you no longer need it.
On February 10, 2017 10:45:01 AM Sannyasin Brahmanathaswami via
use-livecode <use-livecode at lists.runrev.com> wrote:
> When we delete a main stack, the main stack and all its substacks are
> removed from memory.
> But if we delete a stack that has behaviors set from external
> *_behavior.livecodescript stacks for controls in the "main" (parent?)
> stack, those behaviors are still in memory.
> Does it make sense to file an enhancement request, to at least allow the
> dev to set a preference
> __ Delete behavior stacks from memory when stack using them are deleted
Jacqueline Landman Gay | jacque at hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
More information about the Use-livecode