Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!apple!stadler From: stadler@Apple.COM (Andy Stadler) Newsgroups: comp.sys.mac.hypercard Subject: Re: Trapping out Command-Period key presses. Message-ID: <44774@apple.Apple.COM> Date: 13 Sep 90 16:41:53 GMT Organization: Apple Computer Inc., Cupertino, CA Lines: 24 References:<10190@goofy.Apple.COM> In article nayeri@cs.umass.edu writes: >In article <10190@goofy.Apple.COM> stm@apple.com (Steve Maller) writes: > > HyperCard 2.0 has a new property called "cantAbort". It prevents > Command-Period from doing anything. However, note that this is VERY > dangerous, because causing a script to be un-stoppable could force a user > to reboot his machine if the script runs away from itself. This can easily > destroy a stack! > >Steve, why can't command-period be an event and generate a message just like >anything else? So that you can specify a handler in the hierarchy? It seems to >make a lot of sense to me. So programmer can specify a handler like: > Sending "abort" messages wouldn't be very useful, because the only time you could receive such a message is during idling - during which cmd-period doesn't really do anything anyway. Command period is dangerous when it is pressed in the middle of a long script or during some long operation. By the time you received the "abort" message the long operation will have long since completed and it won't really be able to do any good. --Andy stadler@apple.com