Re: launch & quit

2019-10-14 Thread Curry Kenworthy via use-livecode
Robert: > Have you tried to switch off messages before quit? Yes - get angry and then quit with prejudice. Lock messages, unload libraries, close stacks, etc, and really QUIT! :) Also, consider an alternate approach to launching the second app, so that shell doesn't keep your first app

Re: launch & quit

2019-10-13 Thread Robert Brenstein via use-livecode
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 wrote: I have a stand alone with

Re: launch & quit

2019-10-13 Thread Paul Hibbert via use-livecode
I’ve used quit before on Mac with no problems, so I tried a few tests and it still seems to work fine for me (even with your mismatch variable tError/tErrormEssage). I tried both with and without generating a deliberate error and it quit straight away, so I’d guess there may be something else

launch & quit

2019-10-12 Thread Paul Dupuis via use-livecode
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