Oh hey I didn't think about trapping for the menuPick and command key. Good idea.
Bob On Dec 8, 2010, at 1:27 PM, FlexibleLearning wrote: > Bob, > > As I said, 'quit' is non-negotiable. Trap a closeStackRequest in the main > stack's card script and offer the option to abort... > > --| Main stack, card script > on closeStackRequest > checkQuit > end closeStackRequest > > --| Main stack, stack script > on checkQuit > answer "Are you sure you want to quit?" with "Yes" or "No" > if it="Yes" then quit > end checkQuit > > You can use the same handler in your File menu... > > on menuPick which > if which="Quit" then checkQuit > end menuPick > > and in your shortcuts handler thus... > > on commandKeyDown pKey > if pKey="Q" then checkQuit > end commandKeyDown > > > Hugh Senior > FLCo > > > > Hi Hugh. CloseStackRequest does not prevent quitting in the IDE. It appears > nothing does. I suspect however that it would work in a standalone. I will > test that shortly. > > Bob > > > On Dec 8, 2010, at 11:25 AM, FlexibleLearning wrote: > >> 'quit' cannot be terminated once issued. See 'closeStackRequest' instead > of >> 'closeStack'. >> >> Hugh Senior >> FLCo >> >> How do you get an answer dialogue to halt the quit process? If you have a >> "close stack" handler and it has a "do you really want to quit?" dialogue >> and you quit the livecode application you see that answer message flash > for >> a second but it doesn't halt the quit process. > > > _______________________________________________ > use-livecode mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
