> onSaveInstanceState() is called in cases other than screen rotations >> (e.g., activity is being closed up due to low memory), and in those >> other >> cases, onRetainNonConfigurationInstance() is not used at all. > > yes, but wouldn't it be more clever to have > onRetainLastNonConfigurationInstance() be called *before* > onSaveInstanceState(), because then one could determine whether it's > necessary to have the latter actually do something.
I would phrase it more as "it would be good if onSaveInstanceState() knew whether a configuration change is in process", so it knew whether onRetainLastNonConfigurationInstance() would be doing its thing. There might be a way to achieve that today, though off the top of my head I can't quite think of how. -- Mark Murphy (a Commons Guy) http://commonsware.com _The Busy Coder's Guide to Android Development_ Version 2.0 Available! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
