Awesome,

Thanks for your help.

Woo It works hats off....Thanks
And yes i appreciate you guidelines and the ways you explain next time i will take care of it.

Thanks & Regards
Shaan

Thanks Cotty, I got what i want.

@pcmoor Thanks!

These might take me some time to go through and understand, and certainly I'll likely have some questions for you, but I really appreciate you taking the time to build something like this.

Phillip:

But of course! Lovely! Thank you SO much!

~Susan

Thank you Philip! Really appreciate you taking the time to help me out!
~Susan

@shaan36 said:

hi jim i wanna ask you one question i this footing component when i open this file all the every element is different but when i insert this file it is come correctly and also it show the green arrow symbol as DC symbol i could i do that check my file...in same file it shows all parameter but when i insert it in different the file i can't see the parameters.

please guide

You are seeing the difference between Importing the file and Opening the file.

When working with a DC like this which has many sub-components and requires the top-most component to have attributes, you should keep a separate "master" model. I sometimes use WIP (work-in-progress) in the master filename: "dynamic-footing-wip.skp"

Then when you are ready to use or share the DC, you right-click the DC and select "Save As" giving it the proper name for the DC.

Or you can upload directly to the 3D Warehouse for use in the Component Browser by right-clicking the component and selecting "Share Component."

If you try to import the master model, you need to explode it once to get to the parameters. SketchUp automatically "wraps" the imported file in a Component.

well the reason "e1_" is part of that's attribute's name is to control where the option appears in the component options window. with the exception of the predefined size attributes (LenX, LenY, & LenZ, which always appear at the top of the component options window), all other attributes, predefined or custom, get ordered alphabetically in the component options window. if i didn't care where the "back type" option showed up on the list of component options, i'd do away w/ the "e1_" prefix in the name.

but this still doesn't explain why my B2D's "e1_back_type" attribute name is changing to "back_type" upon importation after having imported another cabinet that actually has an attribute named "back_type"...i mean it does and it doesn't. obviously there's a link here, but it doesn't make any sense to me, and i feel like its happening in error.

likewise, the opposite is true - if i were to import the B2D first, i could open the component attribute window and see for myself that there is in fact an attribute named "e1_back_type"...and if i subsequently import a B1D (or any other cabinet with an attribute named "back_type"), all the instances of "back_type" in its formulas will change to "e1_back_type."

No worries....

SU8

....perfect! 😉 tank you so much!

I'm not sure if this will do what you need but there's a 15 day free trial...http://extensions.sketchup.com/en/content/oob-layouts
Otherwise why not make the pattern from within a CAD program. I'd imagine most packages have a pattern function.

I Got it again...it was just the matter of how i upload the DC.

Regards,
Shaan

Hi

One way is to input into a text attribute, then convert the contents using the value and string functions

updated,,,
Attached a component with a calculation group (no size, could set hidden) for lenX,lenY,lenZ
(better labels than last)

Philip

updated

DareDevil, thank you

common problem fixed by putting the attribute within quote marks, "RotZ"

animate("RotZ",-RotationExample!RotationAngle,0)

the case is same for using Current("LenX")

is like using absolute and relative references in a spreadsheet

I dont know the explaination of this behaviour, only the fix

Philip

Hi Shaan
some ideas....

Suggest that all composite components be made of solid groups, thus can use "outer shell" to make one solid and explode all the contents.

Recommend a component like wrapper to protect axis contents and show attributes you want the report writer to see. The next level down should be a group that drives its sub groups and takes reported data from the wrapper. At this level all attribute changes should be made.
Thus this level can be then "outer shelled and exploded" leaving solid geometry behind. ideal for the report writer.

If at a later date you want to change then one can place the original working component within this one after deleting the geometry, explode to expose the inner group then escape back to the model and force a redraw to update the outer component wrapper.

This approach would assure a smaller file, with good reporting on complete shapes rather than a host of little bits

Hidden geometry should be placed where it can be absorbed where possible, or collected at a bin point for deleting

Voids or openings can be created by attaching cutting faces within the component, however they can only work after exploding the outer component, so attribute data need to located with rim maybe set in a lower sub group, so can be reattached later

I notice you are using "parent!" which is required for this type of swapping

cheers
Philip

single leaf opening.skp

it is a pity the videos are not in english. they could at least be subtitled the way fredo6 does his videos.

Thank you.

I didn't know about the imperial bug so I didn't look for it...
Solved that point.

Solved the other poinnt too:
I used the quotes but not far enough. I thought it should be used only for the name or input entries. But not as far as the !X too: ANIMATESLOW("28P6 kompleet!X",0,(-81.5/2.54))

Hi

With regards ruby it would pay to post your enquiry in the developers' forum to get more responses

Personally I am in a similar position, learning ruby, building DC to be used with code, interest is framing

With regards swapping, and cut list
consider the example again with a group of Right end components
if you copy the side DC and replace the geometry within one of the Right ends with it, set the DC to required parameters, then right click, outer shell then explode, all updated and can be seen as complete in cut list

Cheers
Philip

sides.skp

It's a matter of 6 of 1, half a dozen of the other. If the component files were saved as a component within a file then they wouldn't work properly when opened directly in your model, they would have a second top layer. A container within a container. It's not just dynamic components.
If you select some geometry and save as a component, it will create a component that you can use happily via the component browser, but if you open the file itself it will be loose geometry. If you open an empty model and insert the component then save that model and upload it to the warehouse, it will then get a second coat if you download it again into another model.
So you have a choice, one way you are over dressed the other way you are naked.