Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!wuarchive!uwm.edu!ogicse!milton!tvex From: tvex@milton.u.washington.edu (t@vex) Newsgroups: comp.sys.mac.hypercard Subject: Re: 'magic' command Keywords: hypercard, 'magic' Message-ID: <1991Apr30.151423.4671@milton.u.washington.edu> Date: 30 Apr 91 15:14:23 GMT References: <283.2819CAE3@mcws.fidonet.org> Organization: University of Washington, Seattle Lines: 29 In article <283.2819CAE3@mcws.fidonet.org> Harry.Myhre@p2.f863.n102.z1.fidonet.org (Harry Myhre) writes: > >Francis Coll writes in a message to All on 24 Apr 91 > >FC> Could somebody explain how to get access to all user levels on >FC> the Hypercard shipped with new macs (using the magic command). > >This sure has caused a lot of confusion. Hope I get this right: > >1) go to the preferences card of your home stack. >2) make the message box visible (command - m) >3) type "set the userlevel to 5" into the message box and press . > >buttons on the preferences card. You should now be able to remove them. This usually works for me. One more thing, though. Unless there are specific traps built into a stack's script that prohibit or interfere with normal message hierarchies, you should be able to invoke this command from anywhere, in any stack, and if you have "blind typing" set to "true" on the same card that Harry mentions, you should be able to do it without even calling up the message box. If, for example, the userLevel is set to "painting" (whatever the numerical equivalent of that is) and you need to get at a stack script to make a minor change, you can change the userLevel, edit your script, and then not worry about it. If the preferences card says something different than what you specified in your "set userLevel to [1-5]", the userLevel will revert to that specified on the preferences card next time you open the stack. I have seenthose little "cheater" fields or buttons that cover some of the userLevel stuff on the preferences card of some institutional home stacks where the netOps didn't want people to inadvertantly wipe scripts and so forth--it's a poor protection scheme, but can help to prevent accidents.