There must be something I did not get right about DC.
When I change the value of an attribute in my DC (Ok, it’s a special DC, I will describe it later), a new component is created. So, the bottom line would be: don’t loose your time with DC, just create new components! I guess I am wrong, but where ?
My not-so-special component is a component that includes another one (see definition below).
I first create the child component (named “Squarre” in my sample). LenX and LenY are the two attributes of it.
Then, I create the Parent component (named “Parent”). It includes an instance of “Squarre”. It has 1 custom attribute named “Side” that is linked to LenX and LenY.
I create a second instance of “Parent” by drag-and-dropping from the component list.
Finally, I change the “Side” value of one “Parent” instance, and bouuum … a new component is created.
My concern is: in my real project, I have a bunch of instances of such DC. I cannot afford as many component copies as instances with specific value for an attribute.
And finally, for the non-believer, the skp file: DC.01.skp (78.5 KB)
Thank everybody for your mind time!