If the code you are running takes long enough to noticeably block the UI (ie: more than 200ms) then you should do it in another thread. Allowing the user to see the UI but not interact with it (because your app is doing some heavy lifting in the main thread) is just as bad of a user experience as having to wait a long time for the app to load. The only exception is if you put up a loading screen that says something along the lines of "please wait" but that's still not nearly as user friendly as doing the heavy lifting in another thread.
On Jul 22, 7:10 am, Peter Jeffe <[email protected]> wrote: > On Jul 22, 1:29 am, skink <[email protected]> wrote: > > > use MessageQueue.addIdleHandler() > > Very cool, thanks! So I guess this works since it only gets back to > the (now empty) message queue when it's completely done starting the > activity? > > -- Peter --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
