Is there a bug in the API which does not regenerate the Rooms in a FamilyInstance?
When i have two Rooms, which overlap. We get a message that one Room is redundant etc etc. All fine. Now i run a Addin which places a wall / seperator between these two rooms. Call Document.Regenerate() but a element which was in room A, because of the wall now is in room B, but the FamilyInstance of the Element still has a instance of Room A.
It is only after the whole transaction is committed and the Addin is done, only than is the Element's FamilyInstance Room changed. Is this a known issue?
Do we have to commit every time when working with Rooms? I am using one transaction and subtransaction at this moment for better performance.
