Martin Baxter wrote:
The behaviour you note is interesting though as in normal stacks, the
handler should run to the end. It seems that this is not the case in a
modal stack, and any statements after the close stack command are
ignored. Whether this is a bug or by design I can't say. I couldn't find
anything in the dictionary that would lead me to expect this behaviour.
This is a real problem. Although we normally say that Rev doesn't do
threading, effectively there is a kind of threading going on with modal
stacks, such that 'exit to top' exits the processing going on in the open
modal stack - but doesn't affect the processing of the 'underneath' script
that was suspended when it executed the 'modal' statement.
I think that 'exit to top' should exit everything. This has been listed as
an enhancement for almost four years. My guess is that it's not an easy
change to make. But please add your comments/votes to:
<http://quality.runrev.com/qacenter/show_bug.cgi?id=294>
if you think it would be an important improvement. Meanwhile, the workaround
you noted in your original post is your only option.
- Ben
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
