No, it was never my intention to try to delete a mainstack without it substacks - I’m sure this is impossible (and undesirable!). I thought that if I had selected ‘purge stack on close’ for the mainstack, and all the stacks and substacks involved had ‘cantdelete’ set to false, then closing the mainstack would act like ‘delete’ and the whole thing - stack and substacks - would vanish in a puff of smoke. However, see my mail replying to Mike - maybe there really IS a script executing when I attempt the delete. I would like to think it’s just a subtle mistake by me rather than some engine problem.
Cheers and thanks for the reply. Graham > On 19 Oct 2016, at 18:12, J. Landman Gay <[email protected]> wrote: > > On October 19, 2016 10:57:09 AM Mike Bonner <[email protected]> wrote: > >> Silly question but.. If the mainstack has a bunch of substacks, and you try >> to close and remove the mainstack from memory while the substacks remain >> open, is this even possible? > > I didn't think so, and it would explain the error message. The thing that's > "executing" is the open substacks. > > Specifically closing the palettes before deleting the mainstack should fix it. > > > Jacqueline Landman Gay | [email protected] > HyperActive Software | http://www.hyperactivesw.com > > > > _______________________________________________ > use-livecode mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
