Devin Asay wrote: > I have seen what you’re describing on all of the recent releases—9.5 - > 9.6.x; i.e., a stack with destroyStack set to true, then closed, is > not always removed from memory. Sometimes this has caused an infinite > loop with the Save - Purge - Cancel dialog. I would report it, but I > haven’t been able to come up with a reliable recipe. It’s a problem > that I would like to nail down and squash.
Is this to avoid stack name conflicts, or is there some other reason to use this feature?
Because if it's just the stack name conflict thang, I'd rather we solve that at the root by being done with that IDE-imposed limitation that doesn't actually exist in the engine:
https://quality.livecode.com/show_bug.cgi?id=1061 -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ____________________________________________________________________ ambassa...@fourthworld.com http://www.FourthWorld.com _______________________________________________ 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
