This is the same issue I have been talking about for over a year. The 
standalone builder opens the *copied* stacks in memory and doesn't close them, 
so the next time you build for another platform you run into duplicate stack 
issues. This started happening around v7 I think. The workaround at present is 
to build for one platform only, and quit LC each time. I suppose you could have 
a script that purges the openStacks and unregisters any libraries (stacksInUse) 
but that would cause plugin issues, unless you accounted for those. 

Bob S

> On Apr 10, 2018, at 09:29 , William Prothero via use-livecode 
> <> wrote:
> BR:
> I have not tried to build standalones during the last few releases, but with 
> the latest 9.0.0, I am. I notice that when I build my standalone, it loads 
> all of the stacks in the “Stacks” list (in standalone settings. Also, I use a 
> splash stack approach) and leaves them in memory. So, when I want to do a 
> debug after building and trying the standalone, I have all of my stacks 
> loaded and it interferes with my workflow. I’d really like the project to 
> return to the state I started with. It also seems to run scripts in my 
> project which sets various globals. Note: I have implemented Panos’ 
> suggestion to test for the mode of stack “revStandaloneProgress”.  I have a 
> script that returns the project to it’s initial state, but to be safe, I find 
> this behavior forces me to quit livecode and reload it, to make sure my 
> project is returned to its initial state for continued debugging.
> This seems like an undesirable behavior. I can live with it, but ….
> Best,
> Bill
> William A. Prothero

use-livecode mailing list
Please visit this url to subscribe, unsubscribe and manage your subscription 

Reply via email to