If the process is being killed, the Application is gone too. On Tue, Feb 1, 2011 at 9:38 PM, bruce <[email protected]> wrote: > If your process is killed, all the activities are killed so its not > like the globals are released and you still have activities running > causing a force close. Sounds like you need to extend Application() > and use that to contain your static globals. Not that its a good > practice and likely you have settings and other items that need to use > a database, etc. but it is available. > > See http://developer.android.com/reference/android/app/Application.html. > > Cheers, > Bruce > > -- > http://mtterra.com/quicklogger > > > On Feb 1, 5:31 pm, Scott Deutsch <[email protected]> wrote: >> Thats what I feared....ok I will redesign it to make it work. >> >> Thanks a bunch. > > -- > 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 >
-- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training in London: http://bit.ly/smand1 and http://bit.ly/smand2 -- 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
