Thats good enough, thank you

Thank you PCMOOR

Maybe, but there are other components that apply the same attributes based on different inputs that aren't creating unique instances. I would think both would be affected if an attribute was the cause.

Wrong answer : value1==value2 will return TRUE or FALSE Correction : this was for ruby, not for dynamic components

No, but I didn't spend much time on it.

@toddbg said: Thanks Jim - In what way could the axes be better positioned. I'm mor than happy to clean this up so that it becomes a useful model. Actually, it looks good. Not sure what I meant at the time... and thanks to you I learned some new tricks playing with this DC.

Thanks Jim for the work-around. I've definitely commanded the pieces to the "0" position using XYZ "=0". I essentially fixed the problem with Cotty's method of re-doing the local origins of the components. However, not that the pieces are back I wonder if you guys can offer info for scaling. I'd like to door to be able to scale & move pieces to fit a cabinet. Meaning, if I change the width of a cabinet, I want to tell the program to move the left & right stiles, and the scale the rails to fit the new width. Similarly, if I change the height I want SketchUp to move the rails to fit & scale the stiles to their new heights. Could use some genius on this issue!

Dave, thanks for the reply. That's exactly what I'm trying to accomplish is the move/scale balance on the doors. Do you happen to have a door template with formulas for how to achieve that? PC, thanks for all the detailed attachments & template file. I've imported a door to try out the features in our Mozaik program, but when I render it back out to SketchUp the rails and stiles are all stretched instead of staying at their constraints. Thanks though, nice work if I was only drawing cabinets in SketchUp!

You can only reference attributes a distance of one component away. Parent -> Child, Child -> Parent, Sibling -> Sibling. So if you need deeply nested DC's then you need to repeat the attribute at each level.

Hi guys. Here's my take for a scalable component. It also would rely on a Outer Shell being run on each stick, but this could be automated easily enough with a script. This could be used for both the vertical and horizontal pieces I think, but I didn't have time to try. dc_lattice_part.skp

@twdant said: ... What am I doing wrong? After the change of the material you do Redraw ?

You will need to use a component with 2 child components - one for the board and the other a small triangle at the end of the board to control the angle. I thought we had some examples posted but I can't seem to find one at the moment. [image: GOVt_2014-05_08.png]

Absolutely. That problem is fixed and I've moved on to another problem with a different component. If you get a chance, take a look at my "Help close the gap" thread. I'd sure appreciate any help you might be able to offer.

Hi Philip My fault - I thought that components where more 'smart' than it seems (to me). I think I'll still have to do some manual work. Thanks Jorgensen

i have a rollar door on warehouse you can use and improve, drum rotates, sections hid @ given height. models under "pcmoor" philip

Hi David you probably sorted the concept out by now however if not... Each group or component has its own origin axis, usually left bottom side. If you right click on the axis you can change its position, but at this point, probably best to leave it. if you double click to open a group/component within a group/component you will likely notice a shape defined axis and a dull smaller axis. This gives an idea of the relationship between the two objects. The formulas and process is similar to a spreadsheet application, you can click the cells in to build the relationships rafter than typing I find it convenient to build an object with known size and positions then figure first the lengths and then the positions Philip [image: ogFx_toggleformulaview.JPG] [image: zYFa_axis.JPG] fixed glass

Thanks alot Jim! You just saved me from wasting a lot of time. That's exactly what I was looking for.

The behavior of the COPIES attribute failing to also copy the Layer would be considered a bug in Dynamic Components.

Dynamic Component does'nt have any Symmetry tool, only position, rotation and dimension (lenght). If you put a negative value in the lenght attribute, you get the same result as the positive, it use the absolute value. So, I don't see any way to solve your problem with Dynamic Components...

@pcmoor said: for doors use flip along axis instead of using a left and right component. i understand the "flip along axis" concept you speak of, but i have no idea how to implement it in the sub-component of a dynamic component (such as the door on a dynamic cabinet). for instance, i'm currently using the latter method you mentioned (i have two door components, one left and one right, and the left door stays hidden when the cabinet is "hinged right," and vice versa). i would love instead to use a single door that can be hinged either left or right. but when i try to do that, i get door rotation and door location issues. W1D.skp above is a single door wall cabinet (designed by Exitenz) that i found in the 3D Warehouse, and it uses only a single door component that can be hinged left or right (as opposed to using two door components like i did, and keeping one of them hidden at any given time). the door position and rotation formulas make sense to me when i look at them in the component attributes window, but only if the door's component axes change when the hinging changes from left to right or from right to left. in other words, his door must work as hinged left and hinged right b/c it flips along an axis whenever the hinge selection is changed...and this is what i'm having trouble with. the only way i know how to perform such an action is to right-click on a selected component and use the "flip along component's red/green/blue" function. Exitenz's wall cabinet does this automatically when the hinging gets changed from right to left or vice versa...play with his model and see for yourself. anyways, the reason i get door position and rotation problems in my own model is b/c my door's component axes don't reposition (due to a flip along a particular axis) upon a change in door hinging. how do i go about this? here is my model so you can see what i've done so far: W1D_one_door_swing_both_ways.skp @pcmoor said: for rotating function, you need to place an extra component wrapper to protect contents i'm not entirely sure what you mean by this. are you saying that component that is meant to rotate (such as a cabinet door) must be a grandchild to the main component (the cabinet itself)? Exitenz's model above had a component wrapper <F_W1D> around the actual door component <DRBB#1>, making <DRBB#1> a grandchild of the actual cabinet <W1D>, and i don't quite understand why that's necessary... @pcmoor said: don't hide different types of doors,knobs or other components; swap them instead. what do you mean by "swap them instead?" are we talking about the use of layers, or perhaps adding and/or removing parts from an external library into our model? TIA, Eric