sigh. please read the message fully? thanks. it wasn't about blocking as a UI concept.
>Eh, blocking on user input is rarely the way to do things. Your >activity has to be able to respond to other events - such as being >killed or put to sleep when the phone rings. A mobile phone is an >event driven environment - so Google built Android that way. > >If I read your post right, I'd be doing anything that's a long server >transaction in a thread, and if the user must wait for that, I'd >present them with a progress dialog, which is dismissed when the >thread completes (i.e. posts via a Runnable). > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
