If you want a stack to be removed from memory when it closes, it needs to have its destroyStack property enabled. Also check to make sure no script from the closing stack is executing -- that could prevent the stack from closing completely.
Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 2/12/14 4:24 PM, "Peter Haworth" <p...@lcsql.com> wrote: >I think I ran into this a while back but it's cropped up again. > >I have a script that deletes a stack from memory then opens it again from >a >different stack file. When the new stack is loaded, I get the usual LC >message about duplicate stack names and what do I want to do about them. > >In itself, that's weird because delete stack should remove the stack from >memory. I've also tried setting the destroystack property of the stack to >true before deleting it but same thing happens. > >What's even stranger is that the message asks what do I want to do with ><the new stack's filename> before loading <the old stack's filename>, when >it should be the other way round. I guess that could just be a bug in the >message display handler. > >If I step through the script in debug, the problem doesn't occur. > >It seems some amount of time is needed for the stack to really be gone >from >memory, question is how much of a wait should I put in there? > >Pete >lcSQL Software <http://www.lcsql.com> >Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and >SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html> >_______________________________________________ >use-livecode mailing list >use-livecode@lists.runrev.com >Please visit this url to subscribe, unsubscribe and manage your >subscription preferences: >http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
