Ticket 602 implemented a rule that when the run scope setting was set to "newly constructed", that any status in the file should either be reset to new, deleted so it can be defaulted, or ignored in the standard design.
This was missed on ducts. Attached are two TDS files to illustrate the issue. U12R01 has the status set to "existing" and it was assumed that this would get reset because the scope in "newly constructed". The second one is the revised one with all the status' set to "new". A file compare of the two standard designs will show that the only difference is the duct R-value. Even though it was not a good idea to have the status set to "existing" in the test files, this needs to be fixed to avoid cases where the user starts with an addition and/or alteration and switches to newly constructed where the status field is not visible.
Update to rules for this issue have been committed on r827
This update includes:
This update cause change on standard design of model U12R01, which is newly constructed project with existing duct.
Also, the updated logic employed to reset the status fields is detailed in the attached excel workbook.
Updates commited to trunk at rev827