Dave Cragg
Wed, 13 Sep 2000 16:42:29 -0700
At 3:51 PM -0700 9/13/00, Geoff Canyon wrote:
>This seems like a simple question, but my pea-brain isn't cooperating with
>me today, so:
>
>I'm using the following code to open a stack invisibly:
>
> set the lockscreen to true --locks the screen?
> if there is a file theStackFile then
> go stack theStackFile --shouldn't show, but does
> hide stack "prefs" --then hides here
> end if
> go stack "Main"
>
>And it isn't working. When it executes, the second stack, indicated by
>theStackFile above, flashes into existence visibly before hiding.
>
>First, is there a better way to do this? I want to store the second stack
>("theStackFile") separately, because it will be modified, and you can't
>modify a standalone. Second, why isn't the lockScreen property actually
>locking the screen through opening the second stack? Doesn't it do that?
If the second stack (theStackFile) is always to be invisible when
opened, you could do this in a preOpenStack handler.
on preOpenStack
hide this stack
end preOpenStack
If you need to control the visibility from the calling stack, I think
you can use the following (from memory):
open invisible stack theStackFile
Cheers
Dave Cragg
--
_____________________________________________
The LACS Centre (Business English Training Resources)
mailto:[EMAIL PROTECTED]
http://www.lacscentre.co.uk
_____________________________________________
Archives: http://www.mail-archive.com/metacard%40lists.best.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.