Skip to content

Conversation

@akoch-yatta
Copy link
Contributor

Similar to #870, the x/y value of PrecisionRectangle#getLeft and PrecisionRectangle#getRight can return a different x or y value in comparision to the behavior of the other directional methods in PrecisionRectangle as #getBottomLeft. This PR overrides #getLeft and #getRight in PrecisionRectangle.

The x/y value of PrecisionRectangle#getLeft and PrecisionRectangle#getRight
can return a different x or y value in comparision to the behavior of
the other directional methods in PrecisionRectangle as #getBottomLeft.
This commit overrides #getLeft and #getRight in PrecisionRectangle.
@ptziegler
Copy link
Contributor

How critical is this change? There is little chance to respond to any side-effects that might be introduced by this change, given how close we are to the RC2.

@akoch-yatta
Copy link
Contributor Author

We currently don't have any issues with that, but you could get into a similar situation we had with PrecisionRectangle#getBottom. Still, I would not consider this critical.

@ptziegler
Copy link
Contributor

Hm... This edge-case has already existed in the previous release so it wouldn't be a regression. It also shouldn't be relevant to the scaling, when translating the bounds of a figure through the scalable layers. So in that regard, I would prefer to merge this for the M1 and not the RC2.

@ptziegler ptziegler added this to the 3.27.0 milestone Dec 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants