Currently loaded card reloads when screen changes orientation

[ankidroid]

Currently loaded card reloads when screen changes orientation

[hssm]

Fixing the bug regarding the problems to write on all the surface of the Whiteboard
when the orientation changes I have already fixed this bug too.

When Android detects a change in orientation, by default exectues onCreate again.
This behaviour it's not desirable because we only want to change the UI, not reopen
the deck and reload the cards. If onConfigurationChanged(Configuration newConfig is
overridden Android will execute this function instead of onCreate, when the
orientation changes, so it solves the problem.

Reported by edu.zasu on 2009-10-23 09:38:54

• Status changed: Fixed

[hssm]

Great :-)

Reported by nicolas.raoul on 2009-10-23 09:43:33

[hssm]

I had a different solution in place here locally to fix this problem, but this one might
be better. I will try it 
out and see if it also fixes the problem with the crash on screen orientation change
while a deck is loading 
after it has been chosen in the deck picker.

Reported by daniel.svard on 2009-10-23 10:18:30

[hssm]

I don't know if I completely understood how to provoke this crash you are talking
about but I tried it and I think it works just fine.

Let me know if something it is not working!

Reported by edu.zasu on 2009-10-23 10:33:06

[hssm]

This is how I made it crash before:
1. Pick a new deck in the deck picker screen.
2. Rotate the screen while the "Loading deck. Please wait..." progress dialog is displaying.

It was a problem with the thread that is loading the deck trying to write to Ankidroid.currentCard,
but 
since the activity got restarted on the configuration change, that reference was not
valid any more. 
From reading the documentation on onConfigurationChanged, it seems that it prevents
the activity from 
being restarted and thus this problem would be solved too.

My solution involved using the onRetainNonConfigurationInstance() and getLastNonConfigurationInstance()
methods, as well as keeping a reference to the currently active 
activity and using a lock to limit the thread's access to it. 

Reported by daniel.svard on 2009-10-23 10:47:30

[hssm]

I didn't manage to reproduce this :-/
I have the country-capitals deck and a ~15000 cards deck, maybe they load too fast?
Both take less than a second to load.
I am using my master branch.

Reported by nicolas.raoul on 2009-10-23 10:54:44

[hssm]

Then you probably fixed it too. :-D Don't worry.
I just pulled Nicolas' master branch and I'll try it out. 

I think it was present at this commit at least: bec770b0e1b04831b538b044deb116451023a76d
(in Nicolas' 
branch)

Reported by daniel.svard on 2009-10-23 11:05:49

[hssm]

Thanks, Daniel! We'll be waiting your feedback on that ;D

Reported by edu.zasu on 2009-10-23 11:11:59

[hssm]

Tried it now and the bug doesn't seem to exist anymore. It also feels a lot more responsive
than my 
solution.
Great job Edu, thanks!

I'm thinking we should do something similar to the DeckPicker activity to not make
it reload all the deck 
data on an orientation change.

Reported by daniel.svard on 2009-10-23 11:21:52