I understand now, you cannot reference the top level, only the level above or below and any within the same level.
So, need to pass the data through
You can use parent! as a generic reference which is handy for reusing a DC (note make unique if reusing)
@JNL
Subgroups work on the lowest level, they are convenient as stated. But should not be used in intermediate levels, unless used in conjunction with "deep make unique" or similar extensions.
Can drive from parent, the red may show a non-initiated attribute. Though shows "0" in grey, the value in parent is null. So, enter a value.
Otherwise, the formula is incorrect or sometimes disconnected.
Please upload any problem DCs
amended to include position so can change base width
divide into 3 solid groups, groups are good as subs as will not show on OCL, and if required can union or outer shell with no residue
hide the adjoining planes
fix the thickness and formula for base and leg
please up load your model
however a simple method is to split a counter into sections with if statements
A component file is created is created via the right click menu "saveas"
If you open this file you see its contents not the parent, so saving leaves a parent with the groups as per your file,
You need to import the file as done and explode then via right click "saveas" to overwrite or drag and drop. then the parent data is destroyed
It was okay until I sat on it! the joints were quite good, but not for 80kg
@rich o brien said:
No, we are trying to get MSPhysics updated but it won't be for a bit yet.
32 bits ?
but glad something is happening
Open Cut List is a free one
What are you reporting? parts? hardware? whole building? cupboards?
deleted one door
used series of steps and conditions as trigger points
wrapped the door in another component to preserve the axis, then copy, move, flip
Match the X-axis to the grain (default), making one board with OCL attributes as well as DCs
This simple board has a scaler so as to make unique on change, moreover it redefine the material scale (this can be used as a swatch and alternative code sorter)
Saveas this to start the collection, building from the basic within the same file, if you build them separately it can lead to cross contamination.
One creates a carcass by rotating, position and rename the boards(although they should automatically become unique, check that they are )
I include a board example and carcass
the board has one edge, typical of a basic part, from this one can use groups to create more complex boards (use solids, so can make whole when required)
the example is set to definition, change it to none so as use the instance names, the generic parent! is used or latter swapped to, for DC reuse and any name changes
Initially I use the instance method to define the members then switch to the Name attribute later using the dropdown option.
The OCL is set to show DC Names
This normal file shows two separate components that reference each other, so the onclick triggers the action in the door which in turn is read by the switch.
its likely you have tagged the raw geometry, but loading the file will help to resolve
from appdata, find the plugin folder in your version of sketchup and drop the file there
it will load with the rest the next time you open sketchup, so close if already open
groups when used as DCs, can retain connections when copied, they do not automatically become unique. plus scaling can easily become out of sync. The build is in sync if there is no mix of scaled and unscaled items.
to fix, remove the copies
then
you could explode the group then regroup it (thus the new group will not be scaled)
or
you could convert the group to a component then "scale definition", from right click menu
I believe the DC part of this design choice should be components. So method 2. and a rebuild
you can string simultaneous actions with semicolon
Animate Slow("Unlock",22,-1);Animate Slow ("PushPin!Push",-1,0)
Eneroth Decrease Component Number on extension warehouse
