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, then look at the last thing it attempted to do. The problem will be in the thing you told it to do AFTER that, since that thing was what crashed the app.
Bob S > On Feb 27, 2015, at 09:56 , Dr. Hawkins <doch...@gmail.com> 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. > > Anyway, as I'm being advised that the standalones that people are testing > are needing force quits, I recalled that there seems to be something that > frequently stops the quit, even when the IDE is behaving. I also found > that at least sometimes, turning messages off allows the quit to happen > quickly. > > 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 there are always messages in the queue; is the engine > waiting for that to empty, or do i have something more awkward on my hands? > -- > Dr. Richard E. Hawkins, Esq. > (702) 508-8462 > _______________________________________________ > use-livecode mailing list > use-livecode@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@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
