Path: utzoo!mnetor!uunet!husc6!bbn!rochester!cornell!batcomputer!mab
From: mab@batcomputer.tn.cornell.edu (Mark Bodenstein)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: Suggested improvements in HyperCard (long)
Message-ID: <3807@batcomputer.tn.cornell.edu>
Date: 21 Feb 88 22:13:36 GMT
References: <7019@agate.BERKELEY.EDU>
Reply-To: mab@tcgould.tn.cornell.edu (Mark Bodenstein)
Organization: Cornell Theory Center, Cornell University, Ithaca NY
Lines: 19

In article <7019@agate.BERKELEY.EDU> edmoy@violet.berkeley.edu () writes:
>6) On getting a deleteCard message, "exit deleteCard" should abort the
>delete, giving you a chance to save yourself.  For consistency, this may
>mean that deleteCard handlers must have "pass deleteCard" to continue the
>delete.

More generally, there needs to be a mechanism to abort queued up system
actions.  Here's another example: I have a stack that does input consistency
checking in a closeCard handler.  Assume the user does something to leave the
current card, and the closeCard handler finds bad input.  What I'd like to do
is put up an error message dialog box, and somehow tell HyperCard to STAY AT
THE CURRENT CARD, allowing the user to fix the problem.  What I've had to do
instead is go through a perhaps lengthy series of dialogs to get the correct
information.  (Another solution would be to not show the menubar and/or trap
for anything that causes us to leave the current card.  I don't consider this
an acceptable solution.)
-- 
Mark Bodenstein                  {ihnp4,rochester}!cornell!batcomputer!mab
                                 mab@batcomputer.tn.cornell.edu