Yep.. it's that simple. Pls note however that whatever content you're setting will not be actually visible until onCreate() is completed. If your onCreate() processing is lengthy, as ours, you're better off placing your startup image in a dedicated activity.
On May 5, 12:34 am, Marco Nelissen <[email protected]> wrote: > Why not set your content view to be an ImageView with the desired image, and > then once you're ready to show the real UI, call setContentView() again with > the real UI? > > On Mon, May 4, 2009 at 2:22 PM, GiladH <[email protected]> wrote: > > > Tnx but that is not what I'm looking for. > > I basically want to display an image (packed within form/view/ > > whatever) WITHOUT blocking the UI thread, > > > Can this be done? > > > On May 4, 8:16 pm, Jeff Sharkey <[email protected]> wrote: > > > Take a peek at AsyncTask, it can help you easily (and correctly) > > > transition between UI and background threads: > > > >http://d.android.com/reference/android/os/AsyncTask.html > > > > j > > > > On Mon, May 4, 2009 at 10:02 AM,GiladH<[email protected]> wrote: > > > > > Hey, > > > > > I want to display a fancy 'loading' image at my app's startup time. > > > > > The problem: my startup code is mostly GUI related, hence needs to run > > > > on UI thread. > > > > > Is there a way to do both - that is run UI-related code on UI thread > > > > while an image > > > > is displayed to the user? > > > > >GiladH > > > > -- > > > Jeff Sharkey > > > [email protected] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
