Thanks Stoyan, Is it a case of declaring the activity with android:configChanges in the AndroidManifest.xml, and then implementing what to reload in the onConfigurationChanged(Configuration) of that particular activity?
On Mar 11, 11:23 am, Stoyan Damov <[email protected]> wrote: > It's not an issue - restarting your activity when the configuration > changes is by design. > You can mark your activity in the manifest file as one which deals > with configuration changes (hiddenkeyboard, etc.) itself, handle the > configuration change yourself and it won't be restarted. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
