Ray and Jim: Tnx for the suggestions. Tried both. I did lock messages prior to the quit statement. I couldn’t get the toolbar menu to fire on quit. The menu is “PT_Explorer” and the item I want is “Quit PT_Explorer”. So I did domenu “Quit PT_Explorer” of menu “PT_Explorer”
I got no response from the doMenu command, so perhaps I needed to include the shortcut key in the name? Anyway, I haven’t fully tried destroying all my substacks before trying to quit. The quit command does work in a bare stack with no other code, tho. Tnx for the suggestions. Bill On Dec 8, 2014, at 9:29 AM, Ray <r...@linkit.com> wrote: > I just issue the command "quit". You might consider saving first or, if you > don't want any interruptions, locking messages first. > > On 12/8/2014 2:04 PM, Jim Lambert wrote: >>> Prothero wrote: >>> >>> why won?t the button work when the toolbar menu does. Obviously, there?s a >>> difference in the way each works. >> What happens if you >> >> doMenu “Quit” from menu [appName] >> >> ? >> >> >> Jim Lambert >> _______________________________________________ >> 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 _______________________________________________ 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
