Dynamic component challenge - DashLine, Line thickness, fill scaling and holes


I am trying to create a dynamic component that I will use in exploded view’s.

The sample here is a collection of issue’s that I don’t know how to handle it correctly.

In this sample, I have a folie that f.e will be glued to a wooden frame.

The folie has a glue area and holes.


How do I create holes that will be have the same size even after a scale operation?

Lets say I have info about the hole size in a formula, how do I repeat those hole’s vertically?

If I have some items in a sub component, how can I connect a formula to the parent or child?

How can I hide certain lines from sub components or groups?

How can I stick a thickness to a line? Of course Styles are nog copied over when placing a new component into my drawing.

Component Layers. I am using a few ‘internal’ layers inside the component. Is there a way to hide the layer entry’s in the layer list when the component is imported?

Best way. using a Component work file? If I create a drawing and save that as a Component with right click and ‘save as’ then I got a component at the toplayer, however if I save the workfile the the component sits inside a container. Wat is the best way to have a component saved en ready to edit it? If I keep a work file the I have two files to maintain. Any tips on workplan?

Scale and material on face Now when I scale a plane in a direction the material is scaled too. How can I avoid that? Is there a way to just resize a plane.

Is there any problems or bad working method in here?

Workfile - Component_Work_FoilAndGlue.skp (228.8 KB)

Saved as Component from workfile - GlueLayer.skp (174.5 KB)

Sample File Use - sampleGlue.skp (709.5 KB)

fix any objects size by making the size value equal the required ( = 6) without any metric units

in the position Z value use a formula like copy*distance, where “copy” is the read only attribute visible in the actual copies (observe in out liner) and has a value equal to the copy number

attributes (values) can be clicked in to a cell like one does in most spreadsheets without the need to write (spell) them. Groups will except values from the parent and siblings whereas Components will moreover, except values from children

you hide the connections via right click context menu, hide. In this case as per your example attached, you would make three parts.

You would make a template to contain the styles, data (maybe a global DC, common used components), scenes, etc… that is typical for the workflow.


The template? then right click save the DC. If the DC is not cannibalized or reused then any file will do to alter then saveas, otherwise use a common file, make each new alternative unique after using “parent!” in lieu of its parent label title when required.

Use a scaler, this is a small hidden DC swatch with its size set, placed inthe component concerned A method introduced by Tig.
Or another using a child to reference a parents position, thus forcing an update

It is recommended only to use components, however groups can be used with care, as they do not populate the file with lots of redundancy. Groups can have copy issues in that their DC properties can behave like components and are hard to become unique, for simple methods okay, but changing sizes of copies is buggy, However quite easy to change a group to a component if it plays up!

With regards to copying a hole and having the hole maintain its cutting ability, one places the hole DC within another cutting DC. Example make a hole, use the copies formula and create another, select both and make a cutting DC, change copies to zero to reset, then from thence it will work to require number of copies.

sampleGlue.skp (805.5 KB)

1 Like

Note that there is a bug somewhere: If you use subcomponents that are set to cut a hole, copies placed using the copies attribute don’t cut.

thats why you need to place them within another cutting component or group, once established it does cut as per example attached above. Sorry did not make that clear at the second answer, but on the end of the reply