[PBLD192] Fix for vertex snapping to self-object vertices #578
+96
−30
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
lopezt-unity
requested review from
gabrielw-us,
modrimkus-unity and
katherinesheridan
modrimkus-unity
approved these changes
Jan 8, 2025
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.
Purpose of this PR
This PR fixes the Move tool behavior when using Vertex snapping.
The user now has a setting to activate/de-activate in order to enable vertex snapping on the object itself.
This is a settings in the tool settings toolbar, also assignable using a shortcut.
Leaving that as a settings as using vertex snapping on really complex objects, it might not be desired by users to snap on the object itself :P
https://jira.unity3d.com/browse/PBLD-192
@gabrielw-us : I would need a new icon for that settings in the toolbar
Links
Jira: https://jira.unity3d.com/browse/PBLD-192
Comments to Reviewers
[List known issues, planned work, provide any extra context for your code.]