Supress Standalone Builder Warnings

[Klaus major-k]

Hi all,

as I already wrote in this thread in the LC forum:
-> Maybe the mothership could add another "messageless" application which will create the standalone(s)?

See here: <https://forums.livecode.com/viewtopic.php?f=8&t=34933>

> Am 06.05.2024 um 17:39 schrieb Bob Sneidar via use-livecode <use-livecode at lists.runrev.com>:
> 
> Hi Curry. Thanks for your help and Jacque as well. 
> 
> I did as you say, in card 1 of the splash stack (which is the stack I build from because I do not have the need to modify it runtime) I have this code in the card script: 
> 
> on closestack
>   --- curryk 2020 no-purge LC build:
>   if the environment is “development" then
>      lock messages
>      --- and only if add'l loaded MAIN stacks with issues:
>      try
>         save stack "Forms Generator"
>         delete stack "Forms Generator"
>         # delete stack "XYZ" --- etc
>      end try
>   end if
> end closestack
> 
> The result is the first time I build everything goes smoothly (as it always has.) The SECOND time I build I get an alert dialog for every stack that is a behavior of something in the Main Stack or that I started using (library I guess). 
> 
> The standalone Builder opens COPIES of these stacks to add to the standalone, then LEAVES THEM OPEN IN MEMORY. THAT is the heart of the matter. The SB ought not to do that! (I’m talking to you LC devs.) 
> 
> I suppose I could enumerate all of those and then just have code that statically closes each stack. That is probably what I will do. 
> Deleting the main stack does not delete the COPIES of those library or behavior stacks. 
> In summary the problem is not what is open when I go to build. The problem is what is open after I build.
> Anyway, my thanks again for everyone who offered a suggestion on how to resolve this. Sometime the brute force workaround is the only workaround. 
> 
> Bob S

Best

Klaus

--
Klaus Major
https://www.major-k.de
https://www.major-k.de/bass
klaus at major-k.de