Forcing a value when moving a dynamic component

digby dart · 4 Dec 2008, 02:43

Sometimes setting a value (eg. Position X = 0cm) for an embedded component doesn’t hold when later moving the overall Dynamic Component around the SketchUp virtual world. The Dynamic Component part of SketchUp seems to prefer values it calculates. One solution then is to force a calculation (eg. Position X = 1-1). This works for me.
Hope this helps someone else.

Chris Fullmer · 4 Dec 2008, 08:13

But a subcomponent set to x=0 should stay put in reference to its parent component only, not in relation to the real world axis. Are you saying this if you make a subcomponent have an x=1-1 that it will then stay at real world 0, even if you move its parent component? That seems problematic. Maybe I'm just misunderstanding.

Chris

digby dart · 4 Dec 2008, 16:02

Most probably my explanation was a little cryptic.

For some reason occasionally a subcomponent that is meant to reference to parent component X=0 and stay there does not (main parent component X=0).

The problem only becomes apparent when the main component is moved.

The sub component which is meant to stay fixed on the main component X=0 axis moves within the overall component space to an arbitrary X location when the main component is moved.

I am not sure why this happens. The X=1-1 to define X=0 (parent component space) seems to correct the problem.

ps. I have only seen this X Axis mix up when building components but never when changing the values in the user dialog boxes on a built component.

Chris Fullmer · 4 Dec 2008, 21:03

Huh, I tried to duplicate but couldn't.

If I make the parent component x=0 then that component stays put on the world x=0 axis. Then if I make the subcomponent x=parent!x (which is =0), then the subcomponentalso stays put on the zero of te parent, which is stuck to the zero of the real world. So far I haven't seen aynthing fishy.

Do you have a component to check out that's doing this?

Chris

EDIT: I should be more clear. I have had issues with something along these lines in a component I was working on. But its not quite the same problem. So I do have a feeling there is something possibly screwy with how position is happening, I just can't duplicate your experience yet.