-
-
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
Revert backport of 2D transform and camera snapping options #46657
Conversation
If we're going this route, I'd ask to make the commit message a bit more explicit, e.g.:
|
Yup sure, will do. 👍 |
8a5ca82
to
8f33928
Compare
Yes, just to make clear, this should be a good move because we can make the in progress functionality available in an addon in the meantime, so no one should miss out, and we should have a far more polished version for core. 👍 |
More work is needed to make sure that those options actually solve users' issues, so we prefer to remove the options for 3.2.4 and revisit for a future release.
8f33928
to
bf1de6b
Compare
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.
As discussed on the Godot chat, there's still more work needed to make these reliable if we want them to be in the core engine. We'll keep working on these use cases and revisit for 3.2.5 and/or provide relevant addons/documentation on how to achieve what these snapping settings aim to provide.
Thanks! |
As discussed in #46615 (comment) I think there are a number of problem with
transform_snapping
currently and we should leave this until 3.2.5.We can either mark the existing functions as experimental or revert, personally I'm in favour of reverting for 3.2.4, because I'm not keen on having broken functionality in stable release. Some might argue that the existing functions were helpful but we have to weigh that up against user confusion and expectations.