Isaac Waller wrote: > No, what you are supposed to do, is not return from onCreate until you > are ready to show your GUI.
The notion that you should "not return from onCreate until you are ready to show your GUI" is simply incorrect. 1. There is nothing forcing you to construct your UI in onCreate(). 2. There is nothing forcing you to have your lists fully populated in onCreate(). 3. There are things forcing you to not put sleep() calls in any UI thread operation, such as usability and the eventual ANR if your guess is wrong sometimes and it takes longer than ~5 seconds. > the screen flashes 'LOADING' and then shows the > items. It looks quite ugly. Then remove "LOADING". You put that there, not Android. > And then there is the losing of scroll position and focus too. Then handle rotations differently. http://wiki.andmob.org/samplecode Look for "Rotational Forces" for a set of five links on ways to handle rotation events. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy _The Busy Coder's Guide to Android Development_ Version 2.0 Available! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
