Component Heirarchy
-
ok im making a whole heap of kitchen cabinets and im making it with parts of components like side panel back panel rail and so forth, my problem is that sometimes when i try to make a new component with the same name it starts to screw up.
what i want to know is how the naming of components works so that i can better use them...
see i created a lft panel on one component and another on another component but they didnt cause an error, but when i did a vertical kick component the same size as the original it gave me an error, so does the geometry have anything to do with the heirarchy??
-
No, the size has nothing to do with it. If you have components of identical size, they won't interfere with eachother.
What can interfere is if you copy the subcomponent and have 2 instances of the same subcomponent in the model, and try to configure them differently. If you do copy subcomponents, and want to set each on up differently, right click on the copy and choose "Make Unique". Then they will no longer be instances of the same component.
I don't remember if names work into the equation. It seems like they dont? But there are others who might remember the answer to that better.
Also, if you keep running into problems, upload the model again and we can look at it again,
Chris
-
What if I want to make a dynamic component that consists of 10 (or more) instances of the same subcomponent that behave independently? Do I still need to "Make Unique" 10 more times, or is there another way around?
In an Object Oriented Programming Language, we know that we can have as many instances of a class as we like, which can behave differently. Is it NOT true for a subcomponent in SketchUp?
Is it true that all instances of the same subcomponent maintain exactly the same size and shape?
-
Hi
each instance will work independently, but a problem occurs when you change the reference within the child to different parents or update a formula (all are updated), this can be overcome by making the component unique or by using parent! instead of the named parent component that way you can have many parents, But by using parent! you lose the automatic update reference function within the component. So depending on your requirements pick the technique to suit.
cub!lenY , cubby!lenY, big!lenY can all be replaced with parent!lenY
Note when editing or updating latter a specific reference will overwrite the parent! in all the children
cheers
Advertisement