Why is there a parent/child structure? could any of the 'child' aggregates become the 'parent' on demand?
Why is there a parent/child structure? could any of the 'child' aggregates become the 'parent' on demand?
@brunopostle said:
Why is there a parent/child structure? could any of the 'child' aggregates become the 'parent' on demand?
This would be even better. :)
This is being addressed. I expect to share some news about the refactor soon.
@theoryshaw said:
Just another thought. It might be a good idea that if an object inside an aggregate is duplicated (shift+d), that it removes the `BBIM_Aggregate_Data' pset. Similar to how the 'BBIM_Array' pset is removed when an object from an array is duplicated (shift+d).
Could you please add feature requests here: https://github.com/IfcOpenShell/IfcOpenShell/issues/3068
The pset will not be necessary anymore, since now I'm working with IfcGroup, but the "unlink" option should still exist.
ᕕ( ᐛ )ᕗ
Login or Register to reply.