Path: utzoo!attcan!uunet!mcvax!tnosel!hvt
From: hvt@tnosel.UUCP (henq)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: Thoroughly protecting stacks
Message-ID: <697@tnosel.UUCP>
Date: 2 Jul 88 07:43:34 GMT
References: <208taylorj@byuvax.bitnet>
Reply-To: hvt@tnosel.UUCP (henq)
Organization: Organisation for Applied Scientific Research, IBBC-TNO, The Netherlands
Lines: 39

In article <208taylorj@byuvax.bitnet> taylorj@byuvax.bitnet writes:
>
>The userlevel is set to browse.  The message box is hidden.  The only way
>you can raise the userlevel, and thus gain any control over the stack, is
>to type the needed HyperTalk commands into the message box.  But if the
>"Message" menu command (which includes Command-M) is trapped by a domenu
>handler, you can't get the message box.  You are effectively locked out
>of making any changes to the stack.


The menuhandler used in protected stacks usually is located
in the background or at the stack level. I once made a small stack to
patch this sort of scripts. Basically, one button fetches the script 
and puts it in a scrollable field where you can edit it. A second
button puts the changed script back in place. The button scripts
are something like: (I havenUt been hypering since long, so it's
pseudo-hypertalk at best 8).

--the fetch button:
on mouseup
  push card
  get the script of stack TargetStack   --use SFfile XCMD to get it
  pop card
  put it into card field EditMe
end mouseup

--the restore button:
on mouseup
  get card field Editme
  push card
  put it into stack TargetStack
  pop card
end mouseup

Hope this is of some sort of help to ya.

Henk vanTyen

Have a nice day!