-
-
Notifications
You must be signed in to change notification settings - Fork 21.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix issue where set_global_position(global_position)
in Control
resulted in a different result than global_position
#87432
Merged
YuriSizov
merged 1 commit into
godotengine:master
from
Rindbee:fix-set_global_position-in-control
Jan 24, 2024
Merged
Fix issue where set_global_position(global_position)
in Control
resulted in a different result than global_position
#87432
YuriSizov
merged 1 commit into
godotengine:master
from
Rindbee:fix-set_global_position-in-control
Jan 24, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Can we please port to 4.2 branch also. |
Rindbee
force-pushed
the
fix-set_global_position-in-control
branch
2 times, most recently
from
January 22, 2024 13:04
64cd788
to
a2221b9
Compare
kleonc
reviewed
Jan 22, 2024
Rindbee
force-pushed
the
fix-set_global_position-in-control
branch
2 times, most recently
from
January 22, 2024 15:59
ec8220c
to
d327b5f
Compare
YuriSizov
added
the
cherrypick:4.2
Considered for cherry-picking into a future 4.2.x release
label
Jan 22, 2024
YuriSizov
reviewed
Jan 22, 2024
…esulted in a different result than `global_position` Previously, the case where the pivot point was not at the origin was ignored.
Rindbee
force-pushed
the
fix-set_global_position-in-control
branch
from
January 22, 2024 16:05
d327b5f
to
0c6b6fe
Compare
kleonc
approved these changes
Jan 22, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AFAICT it works fine now (I've done some testing).
Thanks! |
This was referenced Mar 15, 2024
kleonc
removed
the
cherrypick:4.2
Considered for cherry-picking into a future 4.2.x release
label
Mar 15, 2024
Shouldn't be cherry-picked, it introduced a regression: #89497. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, the case where the pivot point was not at the origin was ignored.
Fix #87354.