It's the stacks in the STANDALONE that are still open I believe. I think this because at one point there was an LC version that was confusing the source stack and the standalone stack, and as a result it was overwriting my stackfiles in the source stack with the locations of the standalone files.
This is a current *bug* if I may use the B word. You may need to get the openStacks and cycle through them to close them, but of course the stack containing the script that does this cannot itself be closed. You have to filter that one out of the openStacks. Bob S > On May 14, 2018, at 12:19 , Paul Dupuis via use-livecode > <use-livecode@lists.runrev.com> wrote: > > I know this has been discussed before, so my apologies that my Google-Fu > has failed to find any prior answer. > > I have a complex script - part of an Installer "maker" written in > LiveCode - that creates stacks and builds them into Standalones for > various platforms via a long automated script. After the script has > assembled all of the necessary stacks for a build, it executes: > > *send*"revSaveAsStandalone"&"e&tStackName"etostack"revSaveAsStandalone" > > To perform the build. All is good up to this point. The script then > executes "close stack tStackname" and reaches the 'end repeat' to start > the next loop for the next build. The problem is that the next build > contains some stacks with the same names as from the previous build and > I get warning messages about having multiple stacks in memory with the > same name. _______________________________________________ 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
