When I perform an orientation flip, I see the following methods called in the following order:
onSaveInstanceState onPause onStop onRetainNonConfigurationInstance ...then... onCreate onRestoreInstance onResume I specifically want to use onRetainNonConfigurationInstance to *avoid* saving a large complex data set from memory to storage (sdcard) and reading it back in again. I realize doing so is necessary when the app might not come back, such as when it goes to the background or the phone sleeps or something like that. Under such circumstances, I must go to the trouble of saving in onSaveInstanceState and restoring in onRestoreInstance. But for an orientation flip I just want to keep everything in memory and react as quickly as possible. As I understand it, this is the primary purpose of onRetainNonConfigurationInstance. BUT, onRetainNonConfigurationInstance is the very last method that is called as the process is shutting down. So how do I know at onSaveInstanceState time whether to save the entire data configuration to storage or not? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
