Android activities have a pair of methods onRetainNonConfigurationInstance()/getLastNonConfigurationInstance() for keeping objects expensive for load during configuration changes. What should be a nice behavior for fragments in such case? Is setRetainInstance() a solution? What about usage of configuration- specific resources after setting it to true? Thank you.
-- 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

