launch & quit

Robert Brenstein runrev at robelko.de
Sun Oct 13 17:32:49 EDT 2019


I’d guess that quit command triggers some closeXxxx handlers to run 
and one causes the delay. The duration of delay sounds a bit like 
network timeout. Have you tried to switch off messages before quit?

> On Oct 12, 2019, at 13:28, Paul Dupuis via use-livecode 
> <use-livecode at lists.runrev.com> wrote:
>
> I have a stand alone with a card with a button with a mouseUp handler
>
> on mouseUp
>
>   -- some stuff
>
>   -- tApplication variable contains a path to another standalone for 
> OSX or Window depending upon what platform() this standalon is running 
> on
>
>   launch tApplication
>   put the result into tError
>   if tError is not empty then
>     answer error tErrormEssage
>   end if
>   quit
> end mouseUp
>
> On Windows, the designated application launches promptly and my app 
> quits immediately.
>
> On OSX, the designated application launches promptly and my app waits 
> way too long (a minute or two) before quitting.
>
> Standalone built for OSX and Windows on Windows under LC905
>
> Anyone have any experience like this? Any ideas on what to do to get 
> the OSX version to quit when told to quit?



More information about the use-livecode mailing list