Only time I have to force quit is if I made a database call to a stale database
connection, and that of course is my fault for not closing the connection when
done with it. About the only way to find something like this is to have a
logging system that records everything your application does,
On 2/27/2015 11:56 AM, Dr. Hawkins wrote:
There isn't any code that should be intercepting the quit or shutdown
requests, but I'm wondering if the period handlers could be somehow
blocking this? e.g., ones like
on doIt
doSomething
send doIt to me in 100 milliseconds
end doIt
This means that
I've been force-quitting the IDE as my standard so long that I don't give
it any thought . . . the frequency with which it gets lost, beachballs, or
whatever is high enough that I usually don't even try a plain quit.
Anyway, as I'm being advised that the standalones that people are testing
are
On 27/02/2015 17:56, Dr. Hawkins wrote:
I've been force-quitting the IDE as my standard so long that I don't give
it any thought . . . the frequency with which it gets lost, beachballs, or
whatever is high enough that I usually don't even try a plain quit.
Something isn't right on your set-up
is empty
cancel item 1 of line 1 of the pendingMessages
end repeat
end closeStack
Paul
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/Standalones-requiring-force-quit-and-messages-tp4689450p4689468.html
Sent from the Revolution - User mailing list archive
