Save view state with onSaveInstanceState #661
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Does not work properly for configuration change
Finish state-saving api.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The PDFView now automatically and accurately saves its view state (position, zoom) on configuration change and process destruction.
Additionally it provides apis to manually save and restore state in case you'd want to keep states of previous documents the user might return to.
The application developer has to make sure the same document is loaded after the restoration as before. The view has no ability to save and restore whole documents so relies on the host activity calling
load()with the same source as before the save.The automatic behaviour can be disabled with
setSaveEnabled(false);Close #330
Close #607