On Wed, Jan 21, 2009 at 5:01 PM, polo777 <[email protected]> wrote:
> 1 - What would be the life cycle of this class singleton if the user > sends the application (and so the activity that was displayed) in the > background and the activity is destroyed for instance? > 2 - How to make sure this singleton will stay alive as long as the > secondary thread needs? If you want to have work happening while in the background without the system thinking you are just a background app and available to be killed, you need to start a Service and have the work associated with that. > 3 - I still don't really understand what happens when the secondary > thread posts runnable toward the UI main thread that has been > destroyed or sent to the background! The main UI thread isn't destroyed. Well, it is destroyed when the process is killed, and at that point it doesn't matter because the entire process is gone. -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
