On Nov 11, 11:35 am, dreamerBoy <[EMAIL PROTECTED]> wrote:
> Actually, thank you - you WERE correct - onCreate is NOT being called
> for this Activity.
>
> I tried doing a wait() for 5  - then 30 seconds on the onCreate
> callback being called - the wait timed out...  Hmmm.... how to force
> an Activity to properly initialize itself.....

Wait isn't going to do anything, because all application components
are called from them main thread.  So if you block in one of the
callbacks, none of the others will run either.

See the section on threads here: 
http://code.google.com/android/intro/appmodel.html

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to