Re: Building a standalone warns about duplicate stacks

2020-05-07 Thread J. Landman Gay via use-livecode
Thanks, that explains it. I've incorporated Trevor's DataView and it has 
about 10 stacks in use as behaviors and libraries. To add to the fun, I'd 
forgotten that building for mobile no longer disables desktop platforms so 
I didn't think to disable them manually, and the standalone builder put up 
that annoying dialog 50 times.


Surely the warning shouldn't apply to the SB. It knows you just want your 
working files back.

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On May 7, 2020 10:46:55 AM Devin Asay via use-livecode 
 wrote:



Jaque,

I’ve seen this when building standalones with stacks that are using library 
stacks, and the same library stackflles are included in the standalone 
build. Apparently the included stacks are opened during the build process, 
thus colliding with the library stacks already in memory. If this is the 
problem, I suppose a workaround would be to stop using the library stacks 
before running the build process.


Hope this helps.

Devin


On May 6, 2020, at 6:07 PM, J. Landman Gay via use-livecode 
 wrote:


When building a standalone (for mobile in this case) I'm getting repeated 
messages about stacks already being in memory and asking me what to do with 
them. Since I have a lot of included stacks I need to make a decision a 
dozen times. This is different from all the "open*" messages, so that 
workaround won't help.


It doesn't happen when I use the Test button to install directly to my 
phone. I think this is new behavior. Bug?


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
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


Devin Asay
Director
Office of Digital Humanities
Brigham Young University

___
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





___
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


Re: Building a standalone warns about duplicate stacks

2020-05-07 Thread Devin Asay via use-livecode
Jaque,

I’ve seen this when building standalones with stacks that are using library 
stacks, and the same library stackflles are included in the standalone build. 
Apparently the included stacks are opened during the build process, thus 
colliding with the library stacks already in memory. If this is the problem, I 
suppose a workaround would be to stop using the library stacks before running 
the build process.

Hope this helps.

Devin


> On May 6, 2020, at 6:07 PM, J. Landman Gay via use-livecode 
>  wrote:
> 
> When building a standalone (for mobile in this case) I'm getting repeated 
> messages about stacks already being in memory and asking me what to do with 
> them. Since I have a lot of included stacks I need to make a decision a dozen 
> times. This is different from all the "open*" messages, so that workaround 
> won't help.
> 
> It doesn't happen when I use the Test button to install directly to my phone. 
> I think this is new behavior. Bug?
> 
> -- 
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software   | http://www.hyperactivesw.com
> 
> ___
> 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

Devin Asay
Director
Office of Digital Humanities
Brigham Young University

___
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