Dynamic component children issues

Hello,
I have a problem with dynamic components.
When I import a component, and then a second one, the second change some of his children’s name according to the first component that has been imported. (by exemple demi cloison vitrée)
Have you ever encountered this kind of “bug”, or did I do something wrong during the developement?
Herer are two file to test it.
BPA-8-0-F.skp (12.0 MB)
SDR-0-8-F.skp (8.1 MB)

Can you be more precise? A screencapture will be wonderful…

1 Like

Hello
In the case of nested sub-component share in different components. It’s better to use the generic word « parent » in the attribute address.
=parent!attributename
When the address is hard wrote when the component is rename or make uniq and if the name of the parent change in the dialogue
The references don’t works well and join the other component values !

Have a nice afternoon

En français je capterai peut être mieux…
je dois rajouter parent! avant chaque nom d’attributs?
Ca résoudra le problème?

1 Like

partly

The term parent! instead of a component name will cover any name changes to parent, how ever refences to other children or formula will require uniqueness

I use Eneroth’s extension “deep unique” (conveniently works from right click menu) directly after making a copy of a DC in same working file before altering to extend or form a new version. This assures all unique and no so “cross talk” or automatic updates to first installed definition

This works on group subs as well, many do nor realize copies of groups can share same definition (groups are important for OCL bits)

1 Like

Hi, after several try it seems to work with the “parent” tips, I don’t have any replacement in the attribute names, so my formulas are not red anymore. But unfortunately it still replaces the component definition name. But I’ll deal with it.
Think the topic can be closed.
Thx

1 Like