I hope I have posted this in the correctly and in the correct area of the form.
I have been working on building a cabinet library that i can quickly pull from my components list, edit sizes etc with the options menu and produce a cutlist from that extension.
I am pulling my hair out with not understanding why I seem to get errors once I use that model in a new project. I will build the cabinet in it own file and save out to my local collection. So when i have the model reference XYZ for changing sizes and the coding will change to something else that may be in a different component.
You need to make the child components unique. Philip @pcmoor has posted a bunch on this subject and dynamic components in general if you search the forum. You can see in the screen shot the shelf component is the same in both cabinets. Select the child component, right click and then make unique, then rename the definition to something else. I added the prefix WC for Wall_Cabinet.
Your formula errors are coming from using spaces in naming the component Wall Cabinet, use the _ instead of a space, Wall_Cabinet. Also in your child components use the generic Parent! reference to avoid mistakes and make re-use of the child components easier.
Thanks for taking the time to look at this issue Im having. So I believe I had made the changes you had suggested. The two models worked fine when independent but the moment i bring one into another it goes awry.
When you said to ref. the parent, am I doing that incorrectly?
All that is highlighted in RED was not doing that when on their own. What is the simple coding problem am i missing?
Im not sure why the component Upper aka WC is taking on the formulas of the Lower aka BC when I use those components in the same file.
One other thing I just did was to go in and just it apply within the component attributes and those red errors seem to resolve
Hey. Take a look at the modified wall component I gave you, I added the proper Parent! references. Don’t reference the parent, use the Parent! generic reference instead of the component name. In your photo you are referencing bc! the parent component is WC (not bc), use Parent! instead of bc! in your formulas. This way if you change any component names everything still works.
Also you have only made the shelf component unique, all of the other children (sides, base, top and back) are still instances of the same component definition.
Thanks for that insight. Just so I understand moving forward with these kind of things, how does the component know what the Parent is? or is it once I select all my Child components and make those Components one, That now becomes the Parent of those.
Honestly I have only taught myself with the input of youtube tutorials. Thats where I learnt the = (then select the ref ex.LenX) which I asume i can still do but will have to remove the component name and replace with Parent!
Appreciate the help greatly Ryan
One of the next things I will be working on is a dynamic drawer box and a door. I am hoping to have them snap to the boundary of the cabinet box and this will allow me to create door order lists to minimize ordering errors.
NP, glad to help. So the parent is always one level of nesting up from the child. Children can see the Parent but the Parent can not see it’s Children. Seriously, if you want to learn about this stuff search @pcmoor and start reading.
or just start flipping through the dynamic components category, Philip responds in like every thread so its almost the same list .
I just realized I am behind, got a few threads to catch up on myself. You can always post here when you are stuck, try to be clear and post a model for us to look at like you did, lots of people who like to help around. The learning curve with DCs is pretty steep, and they are a lot of fun.
.