Richard: I tried doing “Lock messages” before the quit, and closing unused stacks, but it didn’t seem to make any difference. Apparently the toolbar menu quit command does some kind of cleanup before it actually quits.
Re the system log, I don’t usually try to interpret that. There is a large crash message, tho. I didn’t try to interpret it. Not my area of expertise, but I’ll crash it again and take a look to see if anything pops out. To me, it’s sorta like looking under the hood when the car stops, perhaps kicking a tire. Best, Bill On Dec 8, 2014, at 2:10 PM, Richard Gaskin <ambassa...@fourthworld.com> wrote: > William Prothero wrote: > > > I’ve tried a number of things to get my app to shut down without > > crashing the app. I know it must be possible because the toolbar > > menu quits fine. I may just stop trying to use a script to quit. > > It’s not essential since the toolbar menu quits fine. Anyway, I’ve > > tried locking messages, closing all substacks, delaying the “quit” > > with a send command, and it crashes no matter. > > When it crashes, does the OS present a dialog? Anything in the system logs? > > > But, a bare stack works fine. > > Interesting. Any pending messages at the time quit is invoked? > > > -- > Richard Gaskin > Fourth World Systems > Software Design and Development for the Desktop, Mobile, and the Web > ____________________________________________________________________ > ambassa...@fourthworld.com http://www.FourthWorld.com > > _______________________________________________ > 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
