Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!chaph.usc.edu!nunki.usc.edu!talcott From: talcott@nunki.usc.edu (Adam Talcott) Newsgroups: comp.sys.mac.hypercard Subject: Re: Trapping out Command-Period key presses. Message-ID: <11983@chaph.usc.edu> Date: 16 Sep 90 03:40:50 GMT References: <10190@goofy.Apple.COM> <44774@apple.Apple.COM> Sender: news@chaph.usc.edu Organization: University of Southern California, Los Angeles, CA Lines: 29 Nntp-Posting-Host: nunki.usc.edu In article <44774@apple.Apple.COM> stadler@Apple.COM (Andy Stadler) writes: > [Stuff deleted] > >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. I disagree. What if the abort message was something like a hardware interrupt. The user would press the command-period key combination and HC would do the following: a) if the current instruction is not complete, finish the operation b) remember which script and the location in that script that was about to be executed and generate an "abort" message c) in the abort message handler, the user can verify whether or not they actually wish to cancel the current operation or continue. If the user wishes to continue, execute a new HyperTalk command that would return to the location stored in part b). Otherwist just exit IMHO, this would be a good feature to add to HC... -- | Adam Talcott | Not a bad bit of rescuing, | | talcott@nunki.usc.edu | huh? You know, sometimes I | | Electrical Engineering (Computers) Senior | even amaze myself. | | University of Southern California | --Han Solo |