I initially thought about the same: Using onConfigurationChanged().
However, this is only called for the configuration changes that are
mentioned in the manifest file:
http://developer.android.com/reference/android/app/Activity.html#onConfigurationChanged(android.content.res.Configuration)
...
Hi Mark,
On Jun 4, 5:57 pm, Mark Murphy mmur...@commonsware.com wrote:
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
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
I have not tested it but if you register for orientation configChange,
perhaps onConfigurationChanged() will be called prior to onSave..()?
Though if indeed you feel like 99.9% of the situations
onSaveInstanceState() is called is for orientation changes, then why
don't you just use onRetain..
4 matches
Mail list logo
