D
Drooxy
Guest
Hi everyone,
I am reading this (good) article :
http://code.hootsuite.com/orientation-changes-on-android/
and because I've been struggling handling configuration change in my code, it seems to me that using android:configChanges (on activity) and setRetainInstance(true) (on fragment) could be a simple way to avoid "problems" (or at least confusion) when a screen orientation change occurs.
In the above article, I read that it is better not to use this solution but I do not read (or I do not understand) good reasons not to to it...
Could someone help me ?
Thank you !
Drooxy
I am reading this (good) article :
http://code.hootsuite.com/orientation-changes-on-android/
and because I've been struggling handling configuration change in my code, it seems to me that using android:configChanges (on activity) and setRetainInstance(true) (on fragment) could be a simple way to avoid "problems" (or at least confusion) when a screen orientation change occurs.
In the above article, I read that it is better not to use this solution but I do not read (or I do not understand) good reasons not to to it...
Could someone help me ?
Thank you !
Drooxy