Volian/SourceCode
8
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Get data into memory for approval generation so that page number transitions resolve

Browse Source 
Fixed B2014-025:If not master/slave, load all data into memory for page number transitions. Present dialog if there are errors in page number transitions so that user can resolve.
Added a property to determine if page number transition has incorrect page number caused by length of step’s text/wrapping & pagination
Set property to determine if page number transition has incorrect page number caused by length of step’s text/wrapping & pagination
Add tracking of inconsistent page number transitions; if pdf already open, don’t run 2nd pass for page number transitions (resulting pdf had unresolved page numbers);
This commit is contained in:
Kathy Ruffing
2014-03-04 17:36:02 +00:00
parent 63acad915d
commit 622717ba1a
7 changed files with 61 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
PROMS/VEPROMS.CSLA.Library/Extension/TransitionExt.cs
View File

@@ -808,6 +808,7 @@ namespace VEPROMS.CSLA.Library
if (tb._ToItem.PageNumber != 0 && tb._FromItem.PageNumber != 0)
{
int pgoffset = tb._ToItem.PageNumber - tb._FromItem.PageNumber;
tb._ToItem.PageNumberUsed = tb._ToItem.PageNumber;
switch (pgoffset)
{
case 1:
@@ -831,7 +832,7 @@ namespace VEPROMS.CSLA.Library
tb.Append(" (Page ~)");
}
return true;
}
}
private static bool AddStepNumber(TransitionBuilder tb)
{
// If we're on a step put out the step number.