Standalone builder tells me that there is a stack ... already open and so on

[Bob Sneidar]

Could be a library that is getting opened twice because it's been copied to the standalone, and hasn't been purged yet. I have the same problem. I have to quit each time I build a standalone. It's a known problem. 

Bob S

> On Feb 14, 2019, at 07:09 , Matthias Rebbe via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> Hi today
> 
> i´ve made some modifications to a stack today , which i compiled 2 daysago w/o an error.
> 
> But today i get the following error message when trying to build a Windows standalone:
> 
> "a stack <....> is already in memory. The LiveCode UI does not distinguish stacks which have identical names, so editing these stack files while both are in memory could result in data loss."
> 
> I see this error from time to time regardless what stack i am working on. In the past a restart of LC solved this and i was able to compile again w/o error.
> 
> But this is not working.
> 
> 
> The only modification i´ve done was to change the width of a field. So this should not be the problem.
> 
> I´ve checked the stack and its 12 substack. No other stack is there, only the ones that should be there.
> 
> 
> Any idea what i could do?
> 
> 
> Regards,
> 
> Matthias
> 
> 
> 
> 
> 
> Matthias Rebbe
> 
> free tools for Livecoders:
> https://instamaker.dermattes.de
> https://winsignhelper.dermattes.de
> 
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode