Thanks Jim and Bob,
Jim, this is what I thought but I am experiencing sudden death of the
application that seems to be related to setting the menubar based on
data in the pref stack. Based on the sequence of
preopenstack of main stack runs until command to open the pref stack
then
preopenstack of pref stack runs
openstack of pref stack runs
preopenstack of main stack finishes
openstack of main stack runs
I'll keep working on the problem.
Bob - the preopenstack and openstack in the main stack are in the card
so that only the opening of the mainstack sends the message.
Otherwise, every other stack that opens would eventually (unless
explicitly stopped) pass through the mainstack handler and I want to
avoid that.
Thanks
Ron
On Mar 10, 2010, at 10:32 AM, Jim Bufalini wrote:
Ron wrote:
I have a mainstack with a preopenstack and openstack handler in the
card. In the preopenstack handler there is a call to write out a
preference stack from a custom property, then open that stack, read
data from that stack and then continue with other operations.
My question is, is the preopenstack handler of the main stack
completed before any preopenstack handlers in the preference stack?
or
does the call to open the preference stack interrupt the main stacks
preopenstack handler?
Thanks if you can follow this...
The preOpenStack and openStack of the PREFERENCES stack will
complete prior
to the completion of the MAINSTACK.
This is because you are calling for the opening of the preferences
stack
from inside of the preOpenStack handler of the mainstack. As opening
a stack
requires the preOpenStack and openStack to run for the stack to be
"opened,"
these handlers of the preference stack will run before control is
returned
to the preOpenStack of the mainstack to continue running. Otherwise,
you
would not be able to open a stack and do something with it (like
*start
using*) from within the preOpenStack of another stack.
Aloha from Hawaii,
Jim Bufalini
_______________________________________________
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
_______________________________________________
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
