PdfStructureTreeRoot update - fixing Page linking #1145
Merged
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.
Description of the new Feature/Bugfix
A follow-up / bugfix for PR #1127
/NUMS
array viaPdfStructureTreeRoot.addExistingObject
, we need to save correct array entry into Page's/STRUCTPARENTS
field.Previously this reference was populated with
id = pageNumber
which was broken by PR PdfStructureTreeRoot update - allowing to save Object References #1127PdfWriter.getCurrentPage()
is madepublic
as far as bothgetPageReference()
andgetCurrentPageNumber()
are public. So this method can be used instead ofwriter.getPageReference(writer.getCurrentPageNumber())
Unit-Tests for the new Feature/Bugfix
Compatibilities Issues
PdfWriter.getCurrentPage()
was changed from default to public, no compatibility issues expected.Testing details