Fixed Step_CheckOffIndex beyond 9

Fixed logic for determining Transition Text
This commit is contained in:
Rich 2014-10-16 11:43:51 +00:00
parent 03fdd0e613
commit eae4e95c0a
2 changed files with 15 additions and 10 deletions

View File

@ -173,15 +173,20 @@ namespace VEPROMS.CSLA.Library
// a 0 if found. The dataloader was fixed (6/8/12) to not migrate the
// bad character, but this was added, in case there are some other conditions.
int tst = 0;
try
{
tst = int.Parse(s);
}
catch (Exception ex)
{
return 0;
}
return int.Parse(s);
if(int.TryParse(s,out tst))
return tst;
tst = (int) s[0];
tst -= '0';
return tst;
//try
//{
// tst = int.Parse(s);
//}
//catch (Exception ex)
//{
// return 0;
//}
//return int.Parse(s);
}
set
{

View File

@ -738,7 +738,7 @@ namespace VEPROMS.CSLA.Library
{
// if this section has the DSS_AddDotZeroStdHLS, then we need to account for this when
// concatenating text onto the tabs.
bool hasDotZero = (item.MyDocStyle.StructureStyle.Style & E_DocStructStyle.DSS_AddDotZeroStdHLS) == E_DocStructStyle.DSS_AddDotZeroStdHLS;
bool hasDotZero = !item.IsProcedure && (item.MyDocStyle.StructureStyle.Style & E_DocStructStyle.DSS_AddDotZeroStdHLS) == E_DocStructStyle.DSS_AddDotZeroStdHLS;
if (item == null) return "";
string sret = "";
switch (item.MyContent.Type / 10000)