It doesn’t help that you have your axes upside down in the model you uploaded - blue pointing downwards when I open the file.
That confused me, and makes it harder for you to understand which way a given rotation will go.
I turned things right side up first.
Keep your axes consistent, and usually if you want to rotate a component, it’s easiest to do this around an axis - the blue axis pointing upwards, in the case of the door and handles.
You’ve set the two-handle component at position X = 4cm
which is to the right of the origin of its parent component. That brings it in from the left hand edge of the door when the handles are on the left, but moves it out from the right hand side when you select Right, and Apply. And the door at 85cm wide is (I think) 5cm too wide for the opening, which puts the handle further right.
Is there any reason to have the extra level of component Usa (Threshold) in your model? It contains the door and the pair of handles, but not the sides and top of the frame which its name would suggest it could (but isn’t needed there either).
Why not make the handle pair a subcomponent of the door itself (Blat - though Google translates this as Countertop from Romanian, if that is the language of your DC).
And give Component#1 its a proper name (Door
, or better, Doorway
in English), and all the parameters that the subcomponent formulae refer to which aren’t present.
All the formulae in the subcomponents are showing in red, which indicates some referencing error. For example:
I thought that using parent
instead of door
might fix things, but it doesn’t - you don’t seem to have a component name door
so an attempt to reference its properties like height, width, can’t work. And although Component#1 is the ‘parent’ of the Usa component, it doesn’t have height or width properties defined.
The door itself is too wide for the frame - you can see it poking through to the outside of the frame here.
Either the right hand upright in the frame is in the wrong place, or the door is too wide for the designed opening.
I’m not an expert on Dynamic Components, so I can see some of the problems, but not how to fix them. But maybe you can use what I’ve commented on to see how to fix it yourself?