The correct way to quit a Windows standalone

Bob Sneidar bobsneidar at iotecdigital.com
Fri May 17 16:43:58 EDT 2019


The Splash Stack has the mainstack in it's stackFiles. The actual mainstack is the application the user interacts with. But by the time a standalone is created, there are not mainstacks/substacks. 

So the Splashstack is the standalone, which then opens the mainstack and gets the ball rolling. Yes I do hide the splash stack, not sure why someone wouldn't. When I quit, I am quitting the actual Splash application, but it doesn't wuit it tosses an error and the precess continues to run. I will have to poke around somehow to figure out why. Curious, the Apple standalone does not behave this way, so I don't think it's an error in the code. 

Bob S


> On May 17, 2019, at 13:27 , Bob Sneidar via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> Hi all. 
> 
> I have a splash stach in a Windows Standalone. When I close (or otherwise quit) the stack which the splash stack opens (the actual application) I get a runtime error, and the Splash process continues to run. 
> 
> What is the proper way to cleanly exit an app of this nature? 
> 
> Bob S
> 
> 
> _______________________________________________
> 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





More information about the Use-livecode mailing list