Question re destroyStack
prothero at earthednet.org
Wed Feb 18 20:52:52 EST 2015
Tnx for the suggestion. I guess debugging would go the same. It could make things much easier and cleaner.
> On Feb 18, 2015, at 5:07 PM, Richard Gaskin <ambassador at fourthworld.com> wrote:
> William Prothero wrote:
> > I’m setting up my app. It consists of various stacks and their
> > library stacks. When each sub-section of the app gets called from
> > the main index stack, the destination main stack is loaded, and this
> > then loads a library stack and its substacks that hold the library
> > code. The library substacks have been put into the message path
> > with the “start using ….” command. When the sub-section app quits,
> > I want it and its “used” library stacks to be removed from memory.
> It may be simpler to put the library code into buttons and assign each to your sub-section stacks as behaviors. That way they'll be loaded only with your sub-section, can't affect anything else but the stuff in those sub-sections, and will be cleanly put away when each sub-section stack is closed.
> Richard Gaskin
> Fourth World Systems
> Software Design and Development for the Desktop, Mobile, and the Web
> Ambassador at FourthWorld.com http://www.FourthWorld.com
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode