Skip to content

Library screen - Recyclerview repositioning issues [Sir Black Energy, Cat Knight] #452

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
RobbWatershed opened this issue Jan 16, 2020 · 2 comments
Labels

Comments

@RobbWatershed
Copy link
Collaborator

RobbWatershed commented Jan 16, 2020

Current behaviour
Variant 1
On some phones, the library activity will be killed while the user uses the image viewer (brutal memory optimization ?).

As a consequence, when going back to the library activity, the list may not remember its position (item 0 of current sorting is displayed on top of the screen).

Variant 2
When going back to the library screen from the image viewer, the main list sometimes "teleports" to position (number of books per page x2).

Expected behaviour
Even when killed under pressure, the library activity should remember its exact position of the list when going back from the page viewer

See https://stackoverflow.com/questions/52587745/how-to-save-and-restore-scrolling-position-of-the-recyclerview-in-a-fragment-whe

RobbWatershed added a commit that referenced this issue Jan 17, 2020
…y far without reason after going back from the image viewer
@RobbWatershed RobbWatershed changed the title Library screen - Recyclerview position resets [Sir Black Energy] Library screen - Recyclerview repositioning issues [Sir Black Energy] Jan 18, 2020
@RobbWatershed RobbWatershed changed the title Library screen - Recyclerview repositioning issues [Sir Black Energy] Library screen - Recyclerview repositioning issues [Sir Black Energy, Cat Knight] Jan 18, 2020
@RobbWatershed
Copy link
Collaborator Author

Part of the issue --> mikepenz/FastAdapter#861

@RobbWatershed
Copy link
Collaborator Author

Codename Liza

RobbWatershed added a commit that referenced this issue Jan 20, 2020
- Use commons-lang3.ImmutablePair instead of Pair to avoid null check warnings
RobbWatershed added a commit that referenced this issue Jan 21, 2020
… to the screen after LibraryActivity has been destroyed and recreated (#452)

- Cleanup
@RobbWatershed RobbWatershed moved this to Done - Ready for next release in App roadmap May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

No branches or pull requests

1 participant