I have an app that declares an Application class in the manifest. I noticed that by having an application class, a process hangs around after all my activities exit. The process name is the same as the package name for my app, and I'm assuming that this holds an instance of my Application subclass. (onCreate gets called the first time I run my app in an emulator instance, and thereafter only if I kill this process first.)
This behavior doesn't change if I add android:persistent="false" to the application tag in the manifest. Is this a bug or a feature? (I'm using m5-rc15, if that makes a difference.) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
