Looks like there is some new documentation for configChanges specifically referring to HONEYCOMB_MR2 release. Maybe you can try using orientation|screenSize|smallestScreenSize see if that changes behavior. Hope that at least leads you in the proper direction.
Looks like there is some new documentation for configChanges, specifically referring to HONEYCOMB_MR2 release. Maybe you can try using orientation|screenSize|smallestScreenSize, see if that changes behavior. Hope that at least leads you in the proper direction.
Indeed the combination of "orientation|screenSize" did the trick (smallestScreenSize does not seem to matter). Thank you very much for pointing me in the right direction. – StefanK Aug 5 at 23:11.
It appears that API level 13 has ("silently" as far as I can tell) introduced a change to how android:configChanges attribute is handled. In my particular case, when "targetSdkVersion" in the app manifest is set to "13" any activities that are configured to internally handle orientation changes (e.g. Should not be restarted on screen rotation) are being always restarted regardless of the android:configChanges="orientation" attribute in their declarations. A simple switch of the "targetSdkVersion" to "12" restores the expected behavior.
I searched the API 13 release notes and could not find any mention of such change. Does anyone know if API 13 (and possibly later APIs) will by design not support android:configChanges="orientation", or if there is another approach to achieve this.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.