I know that by default a screen orientation change destroys and recreates an activity, so the activity can load new layout, drawable, and string resources.
I also read about using onRetainNonConfigurationInstance() to save an Object before rotating and getLastNonConfigurationInstance() to restore it after. But realistically, what are the special cases when an app would use android:configChanges="orientation|keyboard|keyboardHidden" to avoid activity recreation during orientation change? Are there any gotchas involved in using configChanges? http://developer.android.com/reference/android/app/Activity.html#ConfigurationChanges --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
