Why, after copying a component I configured, did I see that they are somehow linked, and changing one component also changes part of the other? I think it’s either because I’m using dynamic groups within groups, or Parent!, but I’m not sure, because one group may work fine, while another may not. Please explain!
Doors.skp (2.1 MB)
Did you make it unique? Are all the sub components unique? Using groups instead of components can also cause this to happen. Try using @eneroth3‘s DeepUnique extension to avoid this behaviour.
I use dynamic subgroups, not subcomponents.
I use dynamic subgroups, not subcomponents. They are unique
Dynamic groups are notoriously problematic, they do not behave the same as components. Try making them components and see if your problem persists. Try DeepUnique first maybe and see if that fixes it, it’s free.
But, there will be a lot of components in model.
Yeah, it’s unfortunate. You can try using the Outliner to navigate model components instead of the components window. Name instances appropriately so you can search them.
That’s sort of the point…
I have dynamic window and door components - all with subcomponents. I don’t even notice them when modeling… I just work.
And if you set things up correctly when you copy dynamic windows and doors around and you need to change their color / texture - the subcompnents that are not unique will all update as needed.
“deep make unique” makes groups unique as well, when you copy a group it will behave as a copy until you edit it. Using “deep make unique” via context menu, straight after a copy resolves this issue.
Groups are instances of the component “group” and become unique on change of geometry. Thus DC “groups” when copied behave as you have observed, as a copy does not change the geometry and thus does not become unique
The advantage in using sub groups (lowest level only as groups within groups are unpredictable) are they automatically cleanup on delete and do not show on OpenCutList
As mentioned, use mainly components, use generic component names and specific instance names. They will update the option, attribute dialog and be shown with label when changed) use this in reports. However, if using OpenCutList, need to use Name attribute, which overwrites the instance updates. I use a combination of OCL and the report writer.
