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?
Under posix systems (Linux, BSD, and unixes), you can load the stack as a
bagrounder (non graphical) process using a .mt script saying :
on startup
open stack "the needed stack"
end startup
witch has to be lauched at boot time by a System V init script.
Not sure that the equivalent is avalaible on MacOS9, even using applescript,
keyquencer or quickeys at boottime.
>
> Thanks
>
> gc
>
> 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.
--
Pierre Sahores
WEB, DB, B2B & ASP design.
Because people develop knowledge from scratch
rather than being born with built-in knowledge,
we can adapt to different circumstances.
Sampson, Geoffrey. Educating Eve :
The "Language Instinct" debate.
London: Cassell, 1997 [1999].
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.
