The correct way to quit a Windows standalone

Bob Sneidar bobsneidar at iotecdigital.com
Fri May 17 19:26:08 EDT 2019


NVM Apparently I am supposed to use lock messages to force a quit. There may be something in my code that is halting the quit process, but I don't really need to do any housekeeping, so this works. 

Bob S


> On May 17, 2019, at 13:37 , Richmond via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> As your splash stack is, presumably,either a substack of your main standalone, or the main stack itself
> I don't think you can exit it without the whole standalone exiting.
> 
> So, I suspect, you'll have to find another way of getting the splash stack out of the way.
> 
> Personally I'd make the splash stack invisible:
> 
> on openStack
>   set the vis of stack "mySplash" to false
> end openStack
> 
> or move it off-screen:
> 
> on openStack
>   set the bottom of stack "mySplash" to -100
> end openStack
> 
> Richmond.
> 
> 
> On 17.05.19 23:27, Bob Sneidar via use-livecode 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
> 
> _______________________________________________
> 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