Every time you rotate the screen, the cached list of skills etc. gets thrown away & reloaded, which kind of blows the point of caching it. You may need to make the configuration & repository objects (and everything they contain) Parcelable & store them in onSaveInstanceState()/onRestoreInstanceState().
Related to this, the currently-selected skill doesn't get saved across onDestroy()/onCreate(), probably because you're dynamically building the list of skill-name UI components. (But aren't you also doing something similar for the adventurer name? That gets persisted correctly.)
Every time you rotate the screen, the cached list of skills etc. gets thrown away & reloaded, which kind of blows the point of caching it. You may need to make the configuration & repository objects (and everything they contain) Parcelable & store them in
onSaveInstanceState()
/onRestoreInstanceState()
.Related to this, the currently-selected skill doesn't get saved across
onDestroy()
/onCreate()
, probably because you're dynamically building the list of skill-name UI components. (But aren't you also doing something similar for the adventurer name? That gets persisted correctly.)