Fixed issue where word section page size was being used for the duplex foldout on the preceding page. B2016-135
This commit is contained in:
parent
40cb4a8983
commit
aab71bdd7e
@ -449,9 +449,16 @@ namespace Volian.Print.Library
|
|||||||
// , nextSection == null ? "" : nextSection.DisplayNumber + " " + nextSection.DisplayText
|
// , nextSection == null ? "" : nextSection.DisplayNumber + " " + nextSection.DisplayText
|
||||||
// , sectionChange, wordMargins,_PageCountOfWordSection);
|
// , sectionChange, wordMargins,_PageCountOfWordSection);
|
||||||
}
|
}
|
||||||
MyContentByte.PdfDocument.SetPageSize(rct);
|
// Bug Fix: B2016-135 when using a large page size word section, that large page size was being used for the foldout page
|
||||||
|
// save this for the next section which will be the large page size word section.
|
||||||
|
if (_MyFoldoutReader.Count > 0)
|
||||||
|
MyContentByte.PdfDocument.SetPageSize(NxtRCT);
|
||||||
|
else
|
||||||
|
MyContentByte.PdfDocument.SetPageSize(rct);
|
||||||
|
NxtRCT = rct;
|
||||||
MyContentByte.PdfDocument.NewPage();
|
MyContentByte.PdfDocument.NewPage();
|
||||||
}
|
}
|
||||||
|
private iTextSharp.text.Rectangle NxtRCT = PageSize.LETTER;
|
||||||
private SectionInfo GetNextSection(SectionInfo currentSection)
|
private SectionInfo GetNextSection(SectionInfo currentSection)
|
||||||
{
|
{
|
||||||
if (currentSection.Sections != null)
|
if (currentSection.Sections != null)
|
||||||
|
Loading…
x
Reference in New Issue
Block a user