F2024-006 Fixed pagination logic to that step text at the bottom of an Alarm Point page does not print on top of the bottom continue message
This commit is contained in:
@@ -569,9 +569,22 @@ namespace Volian.Print.Library
|
||||
KeepStepsOnPage = false;
|
||||
}
|
||||
}
|
||||
// B2023-116: Vogtle alarm pagination - sub-steps are separating from their HLS even if there is room for some (not all). See comment above for setting of
|
||||
// 'alarmPageKeepHighWithSubs'.
|
||||
if (KeepStepsOnPage && !alarmPageKeepHighWithSubs && ySizeIncludingFirst > (yWithinMargins - ySizeBtmCtnMess1 - ySizeBtmEndMess1)) KeepStepsOnPage = false;
|
||||
if (KeepStepsOnPage && ySizeIncludingFirst > (yWithinMargins - ySizeBtmCtnMess1 - ySizeBtmEndMess1))
|
||||
{
|
||||
// B2023-116: Vogtle alarm pagination - sub-steps are separating from their HLS even if there is room for some (not all).
|
||||
// See comment above for setting of 'alarmPageKeepHighWithSubs'.
|
||||
if (alarmPageKeepHighWithSubs)
|
||||
{
|
||||
// F2024-006: Vogtle Alarms pagination - compare the size of the step and its first sub-step with what we think we have left on the
|
||||
// page. if not enough room with a continue message then set KeepStepsOnPage to start this step on its own page.
|
||||
// This solved an issue where the last line of step text was printing on top of the bottom continue message
|
||||
float myFirstPieceSize = GetFirstPieceSize(true);
|
||||
if (myFirstPieceSize > yWithinMargins)
|
||||
KeepStepsOnPage = false;
|
||||
}
|
||||
else
|
||||
KeepStepsOnPage = false;
|
||||
}
|
||||
if (!KeepWithHeader && !KeepStepsOnPage && mySize - SixLinesPerInch + yEndMsg - tableSpaceAvailable <= yPageSizeNextPage) // if the entire step can fit on one page, do a page break
|
||||
{
|
||||
// Don't want extra line before step
|
||||
|
Reference in New Issue
Block a user