Path: utzoo!utgpu!watmath!att!tut.cis.ohio-state.edu!purdue!decwrl!shelby!agate!saturn!ssyx.ucsc.edu!sirkm
From: sirkm@ssyx.ucsc.edu (Greg Anderson)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: The card that would not die!
Message-ID: <8658@saturn.ucsc.edu>
Date: 8 Aug 89 16:09:28 GMT
References: <113@citycs.UUCP> <9719@phoenix.Princeton.EDU> <2665NUAPPLE@NDSUVM1> <14907@dartvax.Dartmouth.EDU>
Sender: usenet@saturn.ucsc.edu
Reply-To: sirkm@ssyx.ucsc.edu (Greg Anderson)
Organization: UC Santa Cruz; Division of Social Sciences
Lines: 19

In article <14907@dartvax.Dartmouth.EDU> sean@eleazar.dartmouth.edu (Sean P. Nolan) writes:
>From anywhere else in Hypercard, type:
>
>     edit script of card "xxx" of stack "yyy"

You could also solve the problem by setting lockMessages to true.  If you
do that, no openCard, idle or other messages will be passed to your stacks.
After you've fixed the damage, set lockMessages back to false.

As a general rule, openStack handlers should never cause HyperCard to go
to another card.  Such methods are too easy to throw into endless loops
(as the original poster discovered).

Just use a "next" button on the background.

  ___\    /___               Greg Anderson              ___\    /___ 
  \   \  /   /         Social Sciences Computing        \   \  /   /
   \  /\/\  /    University of California, Santa Cruz    \  /\/\  /
    \/    \/              sirkm@ssyx.ucsc.edu             \/    \/