substack question

[Doug Lerner]

On 1/22/04 5:59 PM, "xbury.cs at clearstream.com" <xbury.cs at clearstream.com>
wrote:

> you can set a mainstack stack (with a substack) as a substack of another
> mainstack
> but you can't set a stack to be a substack of another substack. I tried,
> it wont work...

That is what I am finding too. So it seems that you can only have a two-deep
stack hierarchy. Is that right?

> 
> Workaround would be to make one central mainstack and keep your substacks
> all
> as brothers instead of creating children of children (hope that's
> clear...). But you can
> simulate children with some naming convention
> 
> eg:
> mainstack a1
> substacks
> aa1 - virtual substack of a1
> ab1 - virtual substack of a1
> ab2 - virtual substack of ab1
> etc...

Yes, I figured I would have to do something like that. Or use custom
properties to "link" them all together.

It would be nice to have more hierarchical levels though.

doug


> 
> It will be simpler to work with - guaranteed and there should be better
> performance.
> ---------------------=---------------------
> Xavier Bury
> Clearstream Services
> TNS NT LAN Server
> ext 36465
> Voice: +352 4656 43 6465
> Fax: +352 4656 493 6465
> 
> 
> 
> 
> Doug Lerner <doug at webcrossing.com>
> Sent by: use-revolution-bounces at lists.runrev.com
> 22/01/04 09:51
> Please respond to How to use Revolution
> 
> 
>       To:     How to use Revolution <use-revolution at lists.runrev.com>
>       cc:
>       Subject:        Re: substack question
> 
> .
> 
> 
> Logically speaking, A exists when the app opens. B is sometimes created,
> sometimes not.
> 
> If B is created, sometimes C is created, sometimes not.
> 
> C must be a substack of B which is a substack of A.
> 
> So the order is required. If it is possible. If not I'll need to find some
> work-around.
> 
> doug
> 
> On 1/22/04 5:03 PM, "Brian Yennie" <briany at qldlearning.com> wrote:
> 
>> Perhaps it matters what order you do things in?
>> IOW, if you want a hierarchy A->B->C then what happens if you attach C
>> to B, and then B to A (rather than B to A followed by C to B)?
>> 
>> HTH
>> -Brian
>> 
>>> I tried testing, but I get an error saying that the stack I am trying
>>> to
>>> make a mainStack "is not a main stack". That is why I was wondering if
>>> I
>>> couldn't make another substack the mainstack of another stack.
>>> 
>>> doug
>> 
>> _______________________________________________
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
>> http://lists.runrev.com/mailman/listinfo/use-revolution
> 
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
> 
> 
> 
> 
> Visit us at http://www.clearstream.com
> 
> IMPORTANT MESSAGE
> 
> Internet communications are not secure and therefore Clearstream International
> does not accept legal responsibility for the contents of this message.
> 
> The information contained in this e-mail is confidential and may be legally
> privileged. It is intended solely for the addressee. If you are not the
> intended recipient, any disclosure, copying, distribution or any action taken
> or omitted to be taken in reliance on it, is prohibited and may be unlawful.
> Any views expressed in this e-mail are those of the individual sender, except
> where the sender specifically states them to be the views of Clearstream
> International or of any of its affiliates or subsidiaries.
> 
> END OF DISCLAIMER
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution