Home stack

[Jim Hurley]

>
>Message: 7
>Date: Fri, 7 Feb 2003 14:16:42 -0800 (PST)
>From: erik hansen <erikhans08 at yahoo.com>
>Subject: Re: home stack
>To: use-revolution at lists.runrev.com
>Reply-To: use-revolution at lists.runrev.com
>
>
>--- Jan Schenkel <janschenkel at yahoo.com> wrote:
>
>thanks, this makes it simple.
>
>>  insert the script of stack "Foobar" into back
>>  From then on, messages, handlers and functions
>>  travel 'through' this script as well.
>
>is it possible to put
>
>on startup
>    insert the script of stack "Foobar" into back
>    open stack "aa"
>    ...
>end startup
>
>somewhere so that startup is activated when you
>click on the Revolution app icon in Finder?
>that would be convenient!
>
>=====
>erik at erikhansen.org    http://www.erikhansen.org


Eric,

A minor addendum to Jan's suggestion. The following ritual works for 
me--employing a suggestion from Jeanne. Put the stack that is to 
masquerade as a home stack into the plug-in folder. Include in the 
stack script:

on openStack
   insert the script of  me into back
   hide stack "MyPlugIn"
end openStack

After opening the current stack of interest I go to the 
Development/Plugins menu and select MyPlugIn. And there is the plugin 
acting as background home stack, out of sight and (lurking 
dangerously) out of mind. All relatively painless and, Jeanne tells 
us, to become more so in 2.0.

I wonder if it would work as well to load the plugin before all other 
stacks. Would its scripts then be available to all other loaded 
subsequently? I am unclear of exactly what the plugin would be in 
back of.

When you say: "insert the script of stack "myStack" into back" are 
those scripts then available only to  the stack from which they were 
inserted, to  all open stacks, to all stacks open subsequently, to 
attacks from al queda?

Theorem: All answers raise questions.

Jim