3 ms·

Rotation issues are usually to do with the activity being recreated (i.e. onCreate is called again) as the screen size has changed. There is a config to disable

by RossM 14y ago

Rotation issues are usually to do with the activity being recreated (i.e. onCreate is called again) as the screen size has changed. There is a config to disable this however: http://developer.android.com/guide/topics/resources/runtime-changes.html http://developer.android.com/guide/topics/resources/runtime-...

veeti 14y ago
If you mean configChanges, I would strongly recommend against it because it is a bad practice and it probably wouldn't work in this case anyway (no activity recreation = no multi-panel layout on a 7-inch landscape screen).
- RossM 14y ago
  Ah, sorry I haven't done Android dev in a while; would a better way be yock's onSaveInstanceState/onRestoreInstanceState then?
  - veeti 14y ago
    Yes, something like that in combination with carrying over the existing list data with an retained fragment.
yock 14y ago
It's usually better to implement onSaveInstanceState and onRestoreInstanceState. http://stackoverflow.com/questions/3542333/how-to-prevent-custom-views-from-losing-state-across-screen-orientation-changes http://stackoverflow.com/questions/3542333/how-to-prevent-cu...