Posts made by pcmoor

You could create a group or component called kitchen, then build or place components in this environment. "Kitchen" would hold the global attributes. So newly inserted cabinet DCs will read with attributes =parent!.... and update. You could save this file as a template.

2D will work, but an error on the original seems unfixable, other than making it 3D
So redoing with just 2D elements with no use of lenY works okay

---

2D.skp

Hi

a bit of a challenge, then discovered thickness of the DC is zero (2D?) whereas lenY for the picket was given a value of 1cm, decided to push pull some volume and it fixed it. Set it to 0, but option to change. Had to add the Y scale as well as at thickness=0, the z scale was hidden (another DC bug)

Cheers

---

file containing an instance of the component

You use the scale tool to scale any number of entities, whether raw geometry, groups and/or component instances
The menu option you are referring to is to set a scaled instance as the definition to this scale.
If say the instance had been scale to twice the original size, then one can set the definition to this scale so that all new instances would be at this size and existing would some scale factor of it
When a group or component(instance) is scaled one also has an option to reset the scale, this would return the instance to the definitions size. scale = 1
If the component(instance) has not been scaled these menu options would not be available (grey)

Without the file, I can't be sure, but is the child label "group" as well as the parent? if so then there is a reference to the same. Double click one of the labels and change the name

the next
example3.skp

examples 2.skp

should have known better......
version 8

using onclick formula with groups

1. rotation with cumulative angle

2. multi movement with a timeline called num

example1.skp

zoom all?

did you apply options?

You could upload a model with some commentary on how it should work

facearea returns inches, therefore you need to convert it, 2.542.54 gives sq inches to sq cm then sq cm to sq m then /10000

open the component, select the raw geometry and make another component, set its axis in the direction you require, close
the nested component that holds the geometry is the one you will rotate. If you want to rotate in another direction as well, then you would nest it again so that the rotations are independent

The onClick can not run run concurrently with the scene animation. either one must proceed the other. You can create a timeline animation using the the "animatecustom" function, to trigger events, but onClick only allows one scene change, meaning you would have to click again to move to the next scene. So you probably need to invest into an extension,

refer to https://sketchucation.com/forums/viewtopic.php?f=323&t=68975

@unknownuser said:

I try to reason how this works but it doesn't come easy to me.

It isn't easy. there are a few bugs to get your head around.
Perhaps it's helpful to understand that the dynamic part is a ruby script add on, it's not hard wired and as such has to work within the limitations of the ruby language and the developer's understanding when it was conceived. There are disconnections between what an attribute reports and the updated SU view, for example changing the rotation attribute will cancel out a previous input in any one of the others. Rotations involving groups can affect the size, the change seems to follow the changing boundary box.
Components seem to be more stable, but again misbehave when more than one axis is considered,

Despite the updates in Ruby there seems to be little done to fix these bugs, however there are workarounds to achieve the results you require.

The first important point, I would like you accept is that all onclicks need to be on the same level of nesting, there's no point placing an onclick event in a lower nesting than the other.

I generally use nested groups only for parts of an object, like an "I beam" made of top flange, web and bottom flange. Then the object (I beam), the sum of its parts, is then a component. Collections of components may be then held in a group.
So the second is that using dynamic groups can be more problematic, unless they are simple

So any animated object(s) should be a component and it is better to nest animated component(s) within another component, otherwise the rotation formula can be overridden when swapped or inserted.

At this point you may need to understand why attributes can be overridden, if they were not, then swapping a mouse with a elephant would mean their sizes would always match, etc. However you can match them, if the values are passed one level down and "current" is used in the parent if you want to, say have beam lengths to always match after a swap.

I am still trying to rationalise DCs intricacies myself. so most times I plug in data / methods until it works

Anyway, feel free to add any more problems, then can add some more observations

A Merry Christmas too
First
as foot is a child of bed, then need to choose either as onClick point, not both. The parent or the closest child "onclick" will always trigger before any lower nested "onClick"

I made the bed a component, this fixes the size issues one has to account for if using groups and rotation.

If still want to use groups then you need to use a separate attribute to pass the value to the nested rotation and fix any sizes affected by the rotation.

attached two files, one using groups, other where I converted the group "bed" to a component

cheers for the new year
Philip

---

Loft160_2017.skp

---

Loft160_2017_componemts.skp

could you upload a 2017 version? not intending to update this time.

generally each rotation needs to separate with its own nesting (world axis), however the example on https://forums.sketchup.com/t/rotating-more-than-one-axis-with-a-dc/54350 may work, but best to work your example

a bit of junk, sorry can be deleted, can't recall why I started it.....sign of age?

card trick.skp

I choose generic red and black, rather than add a pallet, use SET("attribute",state1,state2,...stateN) for onClick in parent and reference the child material, named colors have to be text.

http://ruby.sketchup.com/Sketchup/Color.html
lists the standard colors that DCs (ruby) interprets

P.S.
I removed your existing materials replaced with default

in any sketchup version, select the underside of the wall, reverse this face, paint with a pattern, reverse face back, when cut it will show the pattern

David, author of Click-Cuisine ... IKEA. Has been searching for a similar solution. John may have the solution you are looking for:-
https://forums.sketchup.com/t/select-all-sub-components-in-a-selection/54361/35