The bug is just in the sample application: it should call mProgressHandler.sendEmptyMessage(previousProgress) after an orientation change and if the progress dialog is showing. There is no cleanup problem or conflict or anything like this.
On Thu, Sep 4, 2008 at 9:58 AM, blindfold <[EMAIL PROTECTED]> wrote: > > For my own use I do not care if the progress dialog continues from > where it was or starts all over, so I need no save/restore of its > state. However, the fact that the progress bar does not start at all > after changing screen orientation suggests a bug. The impression I got > is that the progress dialog upon dismiss does not get cleaned up > before the activity restarts and attempts (and fails due to a conflict > with the lingering previous progress dialog) to recreate that same > progress dialog. As an application developer I have no control over > the asynchronous dismiss handling, and I cannot see what happens under > the hood that makes it fail, so the above is just my conjecture. > > On Sep 4, 6:18 pm, "Romain Guy" <[EMAIL PROTECTED]> wrote: >> It's actually easy to circumvent. On orientation change, the activity >> should save the current progress value in its Bundle (in >> onSaveInstanceState().) Then, when the activity is recreated, it >> should read this value back and resume the progress from where it >> stopped. > > > > -- Romain Guy www.curious-creature.org --~--~---------~--~----~------------~-------~--~----~ 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 Android 0.9 SDK beta! http://android-developers.blogspot.com/2008/08/announcing-beta-release-of-android-sdk.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
