Unfortunately that is not working. I put the function that checks in the script of the mainStack, and that script gets set as a backScript on preOpenstack so that all the handlers in that stack are available in a Windows standalone (when the Windows builder breaks out all the sub stacks, the script of the mainStack is no longer in the message path).
I then used the Find function to find all the (pre) openStack / closeStack handlers and add the statement at the beginning. However when I attempt to build for MacOS and Windows, or if I do a second build in the same Livecode session, I get the dreaded dialogs over, and over, and over…………. Again. Like 100 times. So my initial question is, what library actually pops up that dialog so I can force the cancel option every time, or is that something built into the engine? Bob S > On May 3, 2024, at 8:26 AM, Bob Sneidar <bobsnei...@iotecdigital.com> wrote: > > Hi Jacque. > > I did attempt to deploy this solution a while back, but for whatever reason > it failed to work, but I’m sure I missed something. I’m curious, should this > also be applied to (pre) openCard / closeCard handlers as well? > > Thanks this is the simplest explanation I have seen. > > Bob S > > >> On May 2, 2024, at 5:40 PM, J. Landman Gay via use-livecode >> <use-livecode@lists.runrev.com> wrote: >> >> It's this: >> <https://forums.livecode.com/viewtopic.php?f=8&t=34933&sid=3c32a0e28cf01b21391bbfae080efcd8&start=15#p198477> >> >> The engine used to lock messages when building a standalone but that was >> changed 4 years ago. Personally I think it causes more problems than it >> solves, but the solution is to add (multiple) handlers to your stack to >> avoid the dialog. Most of my stacks work okay without the additions, but if >> you have certain handlers in the message hierarchy you get the dialog. The >> code you need to add is in the link above. >> -- >> Jacqueline Landman Gay | jac...@hyperactivesw.com >> HyperActive Software | http://www.hyperactivesw.com >> On May 2, 2024 6:58:45 PM Bob Sneidar via use-livecode >> <use-livecode@lists.runrev.com> wrote: >> >>> Hi all. >>> >>> I have about had it with the Standalone asking me if I want to save, purge >>> or cancel for stacks that are already open. I ONLY ever have one version of >>> any stack that is open, unless the Standalone Builder is leaving stack IN >>> the Standalone in memory, which would be breathtakingly bad programming, >>> and I do not think they are doing that. >>> >>> What I would like to do is edit the library that is popping up that dialog, >>> and setting it to where it always cancels (doesn’t change anything). I know >>> I will have to update the library each time a new release came out but it’s >>> worth it just to avoid the hassle of quitting and relaunching every time a >>> different standalone need to be built. >>> >>> I tried editing the script of revSaveAsStandalone.livecode in the MacOS >>> bundle, but the word “purge” does not occur in the library. Any idea what >>> library is actually popping up that dialog? >>> >>> BTW the standalone building IS much faster with 9.6.12 (rc1) >>> >>> Bob S >>> _______________________________________________ >>> 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 > _______________________________________________ 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
