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
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
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
