On Fri, Sep 10, 2010 at 9:46 AM, Romain Guy <romain...@android.com> wrote:
> Option #1 is a lot more intrusive. You lose the ability to > automatically switch layouts, drawables, etc. It might be fine now but > it might come back to bite you in the future. It should always be your > last resort. Saving and restoring an AsyncTask is not difficult. > For example, I was just answering a StackOverflow question where someone's app was breaking when the device was inserted into a dock, because in 2.2 there is a new "dock" configuration that changes at that point. You should *always* write your app to work correctly across a destroy/create. android:configChanges is only for optimization of certain very special cases; it is not an excuse to have a broken app. -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. 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 android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
