Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 5.1
-
Fix Version/s: 5.1.1
-
Component/s: Core/Parsing
-
Labels:None
-
Environment:All
-
Support Case References:Support Case #13093 - https://icesoft.my.salesforce.com/5007000000ovMdt
Description
With the provided PDF, there are pages that are shown in different orientations. If the last two pages (11, 12 landscape orientation) are access directly from the first page (portrait orientation) a section is cut off.
If the pages are navigated to via the scrollbar/wheel or the up/down buttons, the pages render without any issues.
If the pages are navigated to via the scrollbar/wheel or the up/down buttons, the pages render without any issues.
When we load a large document we only calculate the actual size of the first 10 page when building a view, if there are more then ten an average sized is used for remaining pages if any. What appears to be happening is that we are not calculating the page size until we paint the page which is to lake for the page panel to recalculate it's layout. As a result the pageComponent is clipped until the a repaint is triggered.
I've update the PageViewComponentImpl to calculate the page size on a call to validate() for the current zoom, rotation and page boundary.