You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if I use the rectangle tool and just click on my layer to create a random rectangle, then use the 'resizing' bars on that created rectangle to adjust the size, properties for the rectangle do not reflect the actual dimensions it was resized to. So basically the numbers entered into the 'rectangle' properties are not in sync with any dragged modification of the rectangle. Likewise if I enter specific numbers into the properties dialog to change the sizing, and then modify the rectangle dragging the 'resizing' bars , the resulting size is not accurately reflected in the properties.
@scr8tum resizing with the rectangle tool will add a transform node with a scale.
But then there's a disconnect with actual data shown. The properties should always be accurate. How would anyone be able to calculate the combined outcome of the properties value and the 'scale' in transform nodes?
I thought we had an issue filed for this but I cannot seem to locate it. The goal for this behavior is that the Select tool's transform cage and GRS transformations will apply special-cased transformations back to their original geometry generators (Rectangle, Ellipse, etc.) instead of editing the scale parameter of the Transform operation. This is one of the polishing steps I have in mind for the next few months prior to 1.0.
The mismatch is in the node graph. Drawing the rectangle writes width and height on the Rectangle node. Resizing then puts a scale on the Transform node and leaves the Rectangle numbers alone. The canvas shows the rectangle size after that Transform. With the layer selected, the properties panel lists both nodes, so the rectangle size and the Transform scale are both visible, but neither one is the size on screen. You have to combine them yourself. Typing a new rectangle width and then resizing leaves that typed number in place and changes the Transform scale again.
What I would change is that a plain rectangle or ellipse, when its size inputs are literal values, should get the new size written back onto the generator. The Transform node would still hold position and rotation, and a resize would still move that position when the opposite side has to stay put, but the size change would not be stored as scale. If a size input is connected to another node I would leave that wire alone.
Activity
scr8tum commentedon Sep 16, 2026
But then there's a disconnect with actual data shown. The properties should always be accurate. How would anyone be able to calculate the combined outcome of the properties value and the 'scale' in transform nodes?
Keavon commentedon Sep 16, 2026
I thought we had an issue filed for this but I cannot seem to locate it. The goal for this behavior is that the Select tool's transform cage and GRS transformations will apply special-cased transformations back to their original geometry generators (Rectangle, Ellipse, etc.) instead of editing the scale parameter of the Transform operation. This is one of the polishing steps I have in mind for the next few months prior to 1.0.
Siddhartha-singh01 commentedon Sep 26, 2026
@Keavon I can take this.
The mismatch is in the node graph. Drawing the rectangle writes width and height on the Rectangle node. Resizing then puts a scale on the Transform node and leaves the Rectangle numbers alone. The canvas shows the rectangle size after that Transform. With the layer selected, the properties panel lists both nodes, so the rectangle size and the Transform scale are both visible, but neither one is the size on screen. You have to combine them yourself. Typing a new rectangle width and then resizing leaves that typed number in place and changes the Transform scale again.
What I would change is that a plain rectangle or ellipse, when its size inputs are literal values, should get the new size written back onto the generator. The Transform node would still hold position and rotation, and a resize would still move that position when the opposite side has to stay put, but the size change would not be stored as scale. If a size input is connected to another node I would leave that wire alone.
If that is what you want, I will start there.
Keavon commentedon Sep 26, 2026
That's a correct understanding @Siddhartha-singh01, feel free to open a PR once it's built and well-tested. Thanks.
Siddhartha-singh01 commentedon Sep 27, 2026
@Keavon Noted Sir
Thanks !