No, what you are supposed to do, is not return from onCreate until you are ready to show your GUI. I am not ready without these items. If it took, say, 2 or 3 seconds to load these items, maybe, but it takes a fraction of a second - the screen flashes 'LOADING' and then shows the items. It looks quite ugly. And then there is the losing of scroll position and focus too.
On May 23, 8:23 pm, Marco Nelissen <marc...@android.com> wrote: > "hanging the UI thread" is the hack. I suggest you do it the right way > instead. > > On Sat, May 23, 2009 at 8:09 PM, Isaac Waller <ad...@isaacwaller.com> wrote: > > > Even if I changed that, I would lose the saved list scroll position > > and selected item. > > I do not want to make some hack around running it in the UI thread - I > > want to hang the UI thread. > > > On May 23, 8:06 pm, Jason Proctor <ja...@particularplace.com> wrote: > > > >If I do this, then I lose the benefits of running it in the UI thread. > > > >I want to hang my application until it gets these items, because if > > > >not, my view with id="android:empty" shows up for a second, and that > > > >looks ugly. > > > > >So put in another view, one that's not ugly. > > > > how about some kind of progress indicator to indicate that something > > > is happening? > > > > -- > > > jason.software.particle --~--~---------~--~----~------------~-------~--~----~ 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 android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
