[jmbegley]

I have a question regarding control flow when pushing and popping screens off the stack.

When I push a screen onto the stack, my thread continues on to the end. What would be a good way to wait until the screen is done/popped?

For example if I have screen1 which in turn pushes screen2 am I forced to put the code for pushing screen2 into the code for screen1? Would it make more sense to control the screen pushes from the same place?

As a more real example, I have added a menu item to the Compose email page in the Mail application. When the user invokes it, I send the email and then my own screen is pushed onto the stack. When done, the screen pops itself, but then I am back on the compose page. I know how to pop the current screen, the question is "from where"?


Thanks
John

[ecarmody]

Hi John,

There is a pushModalScreen() function. This would cause your thread to suspend while waiting for a return. You have to be careful though, you need to call it from a thread that is allowed to block. IE. not your apps main thread.

I'm not clear on the examples you've given, I can't figure out what your trying to do, or what the issue is, so I can't offer a thought on that.

Regards,
Eric

[jmbegley]

Thankyou. Can't believe I didn't see that method

Basically I am filing the contents of the email to another entity (our own Document management system) after sending and want to close the Compose screen after it is done.

That should work. Thanks a lot.