The PM apparently records the call backs triggered by Mstn's tools that manipulate / modify the cutting / cut elements for each Penetration object.
When the user triggers an Update, the PM dialog is updated and the PO is updated in the model. It would be good to manage any knock on callbacks that this triggers. For example, any associative dimensions or annotation objects, constrained geometry.
Overlaps with Step by Step update idea.
Also overlaps with global update option. Maybe the PM should track any failed orphan associative elements.
| How frequently will feature be used? | Several times a day |
| How much time will you save? | Lots. Penetrations are involved not only between Arch / Structures: MEP but Arch: Structures and Arch: Arch |
Thank you Dominic for this valuable idea. We will further check them and wait for other user feedback and votes.