Remove the currentScaleValue getter from PDFViewerApplication (issue 6158)
#6182
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
…sue 6158) *The next step towards fixing issue 6158.* We can just as well access `pdfViewer.currentScaleValue` directly in `PDFViewerApplication`, instead of having a helper function which just acts as a wrapper for it.
|
/botio-linux preview |
From: Bot.io (Linux)ReceivedCommand cmd_preview from @Snuffleupagus received. Current queue size: 0 Live output at: http://107.21.233.14:8877/247e16fc4a29d5c/output.txt |
From: Bot.io (Linux)SuccessFull output at http://107.21.233.14:8877/247e16fc4a29d5c/output.txt Total script time: 0.65 mins Published |
timvandermeij
added a commit
that referenced
this pull request
Jul 9, 2015
…on-get-currentScaleValue Remove the `currentScaleValue` getter from `PDFViewerApplication` (issue 6158)
|
Good, thanks! |
Snuffleupagus
deleted the
remove-PDFViewerApplication-get-currentScaleValue
branch
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 next step towards fixing issue #6158.
We can just as well access
pdfViewer.currentScaleValuedirectly inPDFViewerApplication, instead of having a helper function which just acts as a wrapper for it.