unopen
stacks.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Phil Davis
Sent: Tuesday, August 02, 2005 8:53 PM
To: How to use Revolution
Subject: Re: when can I set a substack's properties?
One forgotten yet exciting (?) detail:
Phil Davis wrote:
--
Very, very nifty. It's making me think about redesigning the main-
stack / complicated-dialog relation I'm working on. Many thanks.
Charles
On Aug 2, 2005, at 8:46 PM, Phil Davis wrote:
Hi Charles,
You can do a LOT with a substack without officially opening it.
- I'm assuming you're talkin
One forgotten yet exciting (?) detail:
Phil Davis wrote:
-- snip --
You can do all these same things to any unopened stack. But in the case
of an unopened stack that's not already in memory, the first thing that
happens when you "touch" it in any way is that is gets loaded into
memory. This me
Hi Charles,
You can do a LOT with a substack without officially opening it.
- I'm assuming you're talking about a substack of a stack that's already
open. If so, the substack is already in memory.
- You can get/set its properties.
- You can run its handlers by invoking them directly:
send
Thanks. Two details just to check --
On Aug 2, 2005, at 7:46 PM, Dan Shafer wrote:
I suspect it'll be just fine in the standlone. I've done this a few
times as I recall and haven't seen any negative consequences.
And the same with a stack to be run under the Player? (I have
Dreamcard; no st
I suspect it'll be just fine in the standlone. I've done this a few
times as I recall and haven't seen any negative consequences.
Another way of doing this -- I mention it because when I do, people
often say, "I didn't know you could do that!" -- is to use the open
invisible option on the s
I'm not clear about when a substack "exists." I want to set some
custom properties in a substack from a script in the main stack, and
it would be a lot handier if I could do it before issuing the "open"
command for the substack. It seems to work OK during my development
cycle in the IDE. Bu
