Unintuitive UI behaviour on configuration change about easer

[renyuneyun]

Wow, seems I need to look into unpredictable human behaviors :P

Thanks for letting me know. It's due to the fact that I didn't explicitly save the state of every UI component, so when you rotate the screen they will be lost (because UI will be redrawn/reloaded).

I'll fix that in the near future, hopefully this week.

[trikaphundo]

Hahaha, rotating the screen is a good test to see whether an app is robust before configuration changes, a phone call while the activity is showing is pretty unlikely but possible, as other changes :)

Activities manage added fragments and their state, to a certain extent.
I have cloned your project, the problem is that EVERY TIME the main activity is created (onCreate(Bundle)), all fragments are removed and the "FRAGMENT_OUTLINE" is added to the activity. This can be solved by simply checking whether the app was abnormally terminated by the system: (if(savedInstanceState == null)...)

[renyuneyun]

Hmm, I didn't read those materials talking about how states are preserved / need to be preserved (though I know they can and need to be preserved). That's another reason why I didn't add that part in the code in the first place.

Thanks for your pointing out.
Are there any general rules / behaviors about what states will be preserved by runtime / Android and what states need to be explicitly saved by developers? Then I can give a quick check over other components.

[trikaphundo]

I recommend reading the Android documentation; as a starting point activity life-cycle
Essentially it says that the Android system will save and restore most of the state of the view hierarchy.

Fragments added to an activity are stored as part of the activity state by the android system. Also, their life-cycle is closely tied to the host activity's life-cycle and their handling is very similar to that of the activities

[renyuneyun]

Closed as of patch #11 (which is squashed to commit 9e9f051).

Thanks for you work and recommendation :)