Path: utzoo!utgpu!watmath!att!tut.cis.ohio-state.edu!purdue!haven!uvaarpa!mcnc!ecsvax!dlugose
From: dlugose@ecsvax.UUCP (Dan Dlugose)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: The card that would not die!
Message-ID: <7462@ecsvax.UUCP>
Date: 9 Aug 89 17:01:39 GMT
References: <113@citycs.UUCP> <9719@phoenix.Princeton.EDU> <2665NUAPPLE@NDSUVM1>
Reply-To: dlugose@ecsvax.uncecs.edu.UUCP (Dan Dlugose)
Organization: UNC Educational Computing Service
Lines: 31

In article <2665NUAPPLE@NDSUVM1> NUAPPLE@NDSUVM1.BITNET (M. G. Stinnett) writes:
>I had a little problem the other day with a card.  It didn't do anything,
>but I couldn't kill or delete it, either.
>
>There was a card script:
>on openCard
>   global name,class
>   ask "What is your name?" with "Type your name here"
>   ask "What class?" with "Type your class name or number here"
>   go next
>end openCard
>
>But the worst thing was that I couldn't get at the script to change it.
>
>Now the question:  Was there a better way?  Could it have been done from
>within HyperCard?

   I think I've found the solution.  Put this in the stack or
backgrouns script:
on domenu x
  if x is "next" then beep
  else
    pass domenu
  end if
end domenu
   
SO that go next will NOT go next, and you can edit the script, then
take out the "domenu script".  I tested it once.

Dan Dlugose
UNC Educational Computing Service