[newToThis]

i dont know how exactly to do this but my goal is
for this to happen

1) user clicks yes in YES_NO Dialog
2) YES_NO Dialog will disappear
3) new screen is loaded
4) new screen starts a background thread to ask the server for string msg
5) new screen displays LabelField of the string msg after receiving string msg

MY PROBLEM:
im having issues right now with killed application due to
message queue overflow

i believe im blocking main event thread and taking too long to process
the Dialog response. (i block main event thread with a runnable object
because i want the YES_NO dialog to disappear first..) then load the new
screen.

[newToThis]

i read from - BlackBerry Developer Journal > July 2005 > BlackBerry Graphical User Interface Part 1 - ... "Calling invokeLater() repeatedly in rapid succession may cause the event queue to overflow and result in an exception."...

So i deleted one call to invokelater and it worked okay for now .. im hoping
it's really fixed.

[adwiv]

I don't see where you need to block the main thread. Use your dialog as the first screen that is pushed onto the stack. Implement the dialog closed listener and attach it to the Dialog. Now when the dialog is closed, your code will be called with the return value, if the value is yes, push the next screen on the stack. You never need to block the thread to wait for the user to click on Yes/No.

[newToThis]

thanks adwiv ill try this listener thing. i have to say though, right now im
not blockign the main event thread anymore. and it works okay although your
suggestion looks likes the safest way to go.