F2023-015 logic to insure the correct pagelist is used for sub-sections that start on their own page
F2023-015 logic to make sure the section text on the sub-section that starts on its own page starts printing at the top of the page
This commit is contained in:
@@ -1778,6 +1778,10 @@ namespace Volian.Print.Library
|
||||
//_MyLog.InfoFormat("NewPage 10 {0}", cb.PdfWriter.CurrentPageNumber);
|
||||
if (MyItemInfo.IsSection && MyParent != null && MyParent.MyItemInfo.IsSection && (MyItemInfo as SectionInfo).IsSeparatePagination())
|
||||
{
|
||||
// F2023-015 for Beaver Valley as two sub-sections that are printed continuously followed by a third sub-section printed
|
||||
// with separate pagination. This section type uses a different pagelist for the pages after the first page.
|
||||
// Needed to call ResetDocStyleAndValues to set the new page with the other pagelist sytle.
|
||||
ResetDocStyleAndValues(ref yTopMargin, ref yBottomMargin);
|
||||
RefreshDocStyle();
|
||||
yTopMargin = PDFPageSize.PaperSizePoints(MyItemInfo.ActiveFormat.PlantFormat.FormatData.PDFPageSize.PaperSize) - (float)MyItemInfo.ActiveSection.MyDocStyle.Layout.TopMargin; // C2018-003 fixed use of getting the active section // C2020-002 paper size is now set in the format files
|
||||
yBottomMargin = Math.Max(0, yTopMargin - (float)MyItemInfo.ActiveSection.MyDocStyle.Layout.PageLength); // C2018-003 fixed use of getting the active section
|
||||
|
Reference in New Issue
Block a user