Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!ukc!tcdcs!swift.cs.tcd.ie!maths.tcd.ie!mlloyd
From: mlloyd@maths.tcd.ie (Michael Lloyd)
Newsgroups: comp.sys.mac.hypercard
Subject: Lock Screen in SuperCard
Message-ID: <1990Feb26.192004.25183@maths.tcd.ie>
Date: 26 Feb 90 19:20:04 GMT
Sender: mlloyd@maths.tcd.ie (Michael Lloyd)
Organization: Dept. of Maths, Trinity College, Dublin, Ireland.
Lines: 17

Listen, have I missed something, or does "Lock Screen" really not mean "Lock
Screen" at all in SC?

I have repeatedly found that commands such as "open window foo" or
"go window foo" cause (unwanted) unlocking of the screen mid-script.

Just allowing that window to become visible would be a pain, but to
actually unlock all future activity is disastrous.

I find I have to "setwindow window foo" before I lock, then I MUST
stick to that window throughout, forcing unwanted constraints on stack
design.

Does anyone out there know what I am hitting here, and what should be done
about it?

Mike.