Take a look at Ed Burnette's comment on this blog: http://androidguys.com/?p=2084
"The simplest way is to implement onRetainNonConfigurationInstance() to save some data that will be kept across the destroy. You use getLastNonConfigurationInstance() in the new instance of the Activity to recover that information. You can keep anything, even a reference to your current Intent or references to running Threads." Hope this helps. On Dec 3, 3:31 am, Kevin <[EMAIL PROTECTED]> wrote: > I have a chain of messages passed between my UI thread and my network > thread. When a chunk of data completes, the UI thread updates and > sends a message to the network thread for more data. This is working > very well for me, but causing problems when the screen is rotated, as > the original series of messages continues, and a new one is started. > On top of this, a Progress dialog gets created and never dismissed, > rendering the view useless. I've tried several ways to terminate the > initial process to no avail. Has anybody experienced similar > problems? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
