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

Matthias: Do you use Microsoft OneDrive? The following happened to me and I was, at first, blaming Livecode. I couldn’t get Hermann’s turnImage contribution working, but then did a lot of work trying to clean my system of disc errors, then found that oneDrive was corrupting my boot drive (Mac

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

Thanks to all who responded and please excuse that i answer so late. I´ve checked all you suggestions. But nothing solved my problem. I then opened the stack in LC 9.0.1 and was able to built a standalone without a problem. After that i was also able to create a standalone again in LC 9.0.2

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

I just had an, "AHA!" moment. Bob S > On Feb 14, 2019, at 10:15 , Richard Gaskin via use-livecode > wrote: > > The example there is uses two paths that differ based on the Unix shortcut of > "~" for the user's home folder, e.g.: > > /home/matthias/workfolder/somestack.livecode > >

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

May want to review my comments on  https://quality.livecode.com/show_bug.cgi?id=18793 as well.  I‘m not so sure it is a problem in the engine itself (duplicate stack short names).  But the way the same file gets interpreted as duplicated is probably engine related.  I don’t think I looked at

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

I don't have the answer to your circumstance; the Standalone Builder is complex, and LC's introduction of stack name conflicts not inherent in the MC engine has become such an ongoing issue that it might be ideal to revisit that sometime*. In the here and now, I have only one tidbit to

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

Matthias Rebbe Tel +49 5741 31 ‌https://matthiasrebbe.eu ‌ > Am 14.02.2019 um 16:35 schrieb Bob Sneidar via use-livecode > mailto:use-livecode@lists.runrev.com>>: > > I have to quit each time I build a standalone. It's a known problem. > That also was my

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

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 > wrote:

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

Forgot to mention that i am working with LC 9.0.2 and Mac OS X. Matthias Rebbe free tools for Livecoders: https://instamaker.dermattes.de https://winsignhelper.dermattes.de > Am 14.02.2019 um 16:09 schrieb Matthias Rebbe

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

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