On Wed, Jun 3, 2009 at 5:00 AM, guruk <[email protected]> wrote: > > Hi, i have a main activity that needs quit a lot to load > so i thought about a trick: > > i call a intropage that shows a pic and from directly it calls by > intent the > long loading page. > > Finaly I thought I would see the pic and in the background the other > intent > is loading, when its done the intro page dissapear automaticly and > voila. > > (yes i thought i am very clever.... ) > > But now i see, that the Intro Page does not come initialized at all. > I see in the header that the intro page is active, but the pic is not > shown. > immediatly it loads the main intent. > > So i guess i have to options.. make a small wait (but how) that the > pic from > the intro is finaly shown.. or more professional I have the option to > request > from windowmanager or so, if the layout from the intro is full shown. > Only when that is done, I would call the Intent to start the main > activity.
The problem is that you're blocking the main thread, which prevents the UI from being shown. You don't really need your 'intro' activity. In your main activity, you can just set a picture, then do whatever your activity needs to do at startup in another thread, and once that is done, update the UI. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
