Finding the Stack that Started Up a Stack

[xavier.bury at clearstream.com]

Hi Dave,

the best way to do that is the following:

- grab line 2 of "the windows" - but there's no guarantee this was the 
stack that did it.

- Put a frontscript that watches the closestack or suspendstack events and 
records which stack was last... This may not work if a lock messages is in 
effect...

- Use an alternate handler (on gomystack) or within your handler, pass a 
parameter that says which was the stack that sent the message...

- Similar to the last, use a global to track navigation history... 
Probably the easiest...

cheers
Xavier


use-revolution-bounces at lists.runrev.com wrote on 28/10/2005 14:52:08:

> Hi,
> 
> A quick question, If I have two stacks StackA and StackB:
> 
> A script in this StackA executes:
> 
> go to stack "StackB"
> 
> In StackB (in one of the preOpen or open handlers) is there any way 
> of finding out that StackB was run by StackA? I would like to know 
> the current Stack that caused StackB to get control?
> 
> Thanks a lot
> All the Best
> Dave
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your 
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution



-----------------------------------------
To make communications with Clearstream easier, Clearstream has
recently changed the email address format to conform with industry
standards. The new format is 'firstname.familyname at clearstream.com'.

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