modal stack "Prompt"

[Lynch, Jonathan]

It is consistent with the way the message path works, and I can envision
situations where you would need this sort of behavior - such as if you
had an app that created many stacks on the fly, and needed to do
something when one of those stacks was opened.

However, it can still cause problems. Be especially careful of this
danger if you have a resizestack handler in your main stack. A
resizestack handler that produces an error will crash the program.

Here is an easy way to avoid problems:

On preopenstack
  If the short name of the owner of the target <> the short name of this
stack then exit preopenstack

-- do whatever else needs to be done
End preopenstack


A preopenstack message first goes to the card, then the stack. So, the
above script makes sure that preopenstack message was triggered by the
same stack in which it resides.

-----Original Message-----
From: use-revolution-bounces at lists.runrev.com
[mailto:use-revolution-bounces at lists.runrev.com] On Behalf Of Peter T.
Evensen
Sent: Wednesday, August 31, 2005 6:28 PM
To: How to use Revolution
Subject: Re: modal stack "Prompt"

That seems to be what it was.  That is rather esoteric behavior.

I think the main stack was catching a preOpenCard or OpenCard, but the 
substack that did the modal command also had those.  I added empty 
preOpenStack, openCard and preOpenCard handlers and that seems to have 
solved the problem.

This just seems like odd behavior.  I would consider it a bug.  I don't 
know when you would want a modal dialog to appear over and bring forward
a 
stack other than the one containing the script which calls the modal
function.

At 05:15 PM 8/31/2005, you wrote:
>Since no Rev-pro has stepped up to bat on this one,
>I'll hesitatingly venture a suggestion...
>
>Is there an "on openStack" or "on preOpenStack"
>handler in the "Prompt" substack? The reason I ask
>is that, when any stack first opens, I think an "openStack"
>message is generated. Thus, if the "Prompt" stack
>doesn't handle this message, then the next stack up
>will, i.e., the mainstack.
>
>Thus, my solution in the past to something like your problem
>here was to insert an empty "on openStack" handler
>in the stack.
>
>Hope that helps.
>
>--
>Nicolas Cueto
>niconiko language school
>_______________________________________________
>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

Peter T. Evensen
http://www.PetersRoadToHealth.com
24-hour recorded info hotline: 1-800-624-7671 

_______________________________________________
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