Re: "Deleting" Stacks in Memory - What About Behaviors?

2017-02-10 Thread J. Landman Gay via use-livecode
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

Re: "Deleting" Stacks in Memory - What About Behaviors?

2017-02-10 Thread Bob Sneidar via use-livecode
I was thinking the same thing. I'm pretty sure that when an app for Windows uses DotNET Framework, it takes some time to initially load the framework, then the app can launch. Once the app is quit, I do not think it unloads DotNET Framework, because the next time I launch the app, the process

Re: "Deleting" Stacks in Memory - What About Behaviors?

2017-02-10 Thread Richard Gaskin via use-livecode
Sannyasin Brahmanathaswami 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

"Deleting" Stacks in Memory - What About Behaviors?

2017-02-10 Thread Sannyasin Brahmanathaswami via use-livecode
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