joesinger12
commented
6 years ago 8/22/17 DR - I am going to commit a new rule file that has all of the TreeDescrip rules in it, and put it at the end of compilation so those get refreshed to the final result of a complete rule eval. That should address the discrepancy between object status and what is shown in the tree.
As for the issue of the Win:Status remaining 'New' after switching over to ExistingAddorAlt, I think it is because Win:DefaultStatus rule looks at Proj level inputs before looking at the status of the parent wall.
LH any issue with just always defaulting to the status of parent wall/roof for fenestration?
RH, are your wall/rook status rules reliable enough for the fenestration to always just inherit those values?
In any case, as best I can tell, it just takes 1 default rule eval for the statuses to fall inline with each other
Original comment by: joesinger12
8/22/17 NK - I just noticed that the status on the objects is not refreshing after I change the compliance type. I used our Standard Model for small office and changed to Existing Addition Alteration.
The space status says Altered even though everything says existing. This because the Window status has not refreshed to Existing – only after doing some changes or reopening the project.
Reported by: joesinger12
Original Ticket: cbecc-com/tickets/2469