{"push_id":900585880,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"a0a12f5d7034ab4fc06771dcf922f00c098847aa","before":"b6dadffc02b81ceada5efbe69aba6f6e19dd9032","commits":[{"sha":"1a41cd599f7f4ecd708e60d0d0360398cc9373a7","author":{"email":"49e1b79a332af2756c1e3d95dda72d230ab67998@outlook.com","name":"Frank Davidsen"},"message":"Removes scroll offset from saved bundle during activity restarts.\n\nUp to this point, the app used getFirstVisiblePosition() / setPosition() to recall the rough scroll position and getTop() / scrollBy() to recall the precise scroll position. Using scrollBy() to restore the initial scrolling position of the poster grid view turned out to be problematic. Black areas sometimes appearing on top and the scrolling experience that was not fluid.\n\nI attempted to use an alternative approach by saving the entire grid state with grid.onSaveInstanceState() and grid.onRestoreInstanceState(). It makes sense -- who better to know how to save and restore its internal state than the grid itself? It turned out that this alone does not restore the scroll state, indeed by design. In general, switching between screen orientations with different number of columns are problematic because switching back and forth is not a stable operation.\n\nHowever, an approximate restore by index only is better than no restore (it's annoying to be thrown back to the top of the list due to an accidental orientation change) so I keep that part, and remove the problematic offset.","distinct":true,"url":"https://api.github.com/repos/fdavs/nanomovies/commits/1a41cd599f7f4ecd708e60d0d0360398cc9373a7"},{"sha":"a0a12f5d7034ab4fc06771dcf922f00c098847aa","author":{"email":"49e1b79a332af2756c1e3d95dda72d230ab67998@outlook.com","name":"Frank Davidsen"},"message":"Movie data is stored and retrieved with onSave/RetrieveInstanceState(). Saved movie data expires and is reloaded after one hour.","distinct":true,"url":"https://api.github.com/repos/fdavs/nanomovies/commits/a0a12f5d7034ab4fc06771dcf922f00c098847aa"}]}