I think you could also use the constructor for your class that extends Activity. But I could be wrong, as I haven't tried this trick. Yet. :-)
Jim Renkel On Mar 21, 2:52 pm, "Dan U." <[EMAIL PROTECTED]> wrote: > I believe the onCreate() for the first Activity is the right place to > do this. I don't think you can put any code earlier than this. At this > point, the window is not shown anyway, so it shouldn't be a problem. > The Activity docs explain it a bit. I think it's onStart() when the > Activity becomes visible, which is after onCreate. > > On Mar 21, 12:03 am, Jakob Bjerre Jensen > > <[EMAIL PROTECTED]> wrote: > > Hello, > > > As far as I understand the Android framework, the entry point for an > > application is the > > onCreate() method for some activity. However I would like to do some > > initialization (prior > > to showing the first window in the app), which are related to the whole > > application, not to > > a specific activity. > > > Does there exist some hook for doing this? Or is there any other natural > > place to put this kind of > > initialization code? > > > Best regards, > > Jakob Bjerre Jensen --~--~---------~--~----~------------~-------~--~----~ 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] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
