More than being accepted, it's the only way. If you do blocking operations in the main thread, you will soon give the user an "Application Not Responding" dialog and they will kill you.
Now you -can- create another thread and run a dialog window thread... but any thread running UI has the same "do not block for a significant amount of time" rule, and thus result in ANRs if it is not responding so the UI is responsive to the user. On Nov 7, 3:00 pm, Jason Proctor <[EMAIL PROTECTED]> wrote: > thanks for the response. > > ok so that's the accepted way to do it. great. > > >Fine. Yes, the only way to get a response from a button is via the > >onClick() handler. So yes, you use that to start up a thread and put > >up a progress dialog, then close it when the thread has done its long > >transaction. > > >Or not have the progress dialog - then the rest of the UI is still > >active while the other stuff is going on in the background, if that's > >what you prefer. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
