-
-
Notifications
You must be signed in to change notification settings - Fork 21.3k
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
Clarify the results of VectorN.normalized()
in the docs
#92707
Merged
Merged
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
RedMser
reviewed
Jun 3, 2024
AThousandShips
added
enhancement
documentation
cherrypick:4.1
Considered for cherry-picking into a future 4.1.x release
cherrypick:4.2
Considered for cherry-picking into a future 4.2.x release
labels
Jun 3, 2024
GrahameGW
force-pushed
the
vector_normalized_docs
branch
from
June 3, 2024 15:10
a0d3b67
to
bbf1a7f
Compare
AThousandShips
approved these changes
Jun 3, 2024
Fixed space typo and adjusted vector format to (0, 0) from (0,0)-- thanks guys for the review |
AThousandShips
changed the title
Clarify the results of VectorN.normalized() in the docs
Clarify the results of Jun 3, 2024
VectorN.normalized()
in the docs
Could you please update the commit message to match the PR title? |
GrahameGW
force-pushed
the
vector_normalized_docs
branch
from
June 3, 2024 21:17
bbf1a7f
to
0560e89
Compare
Yep, all set |
Thanks! And congrats for your first merged Godot contribution 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
cherrypick:4.1
Considered for cherry-picking into a future 4.1.x release
cherrypick:4.2
Considered for cherry-picking into a future 4.2.x release
documentation
enhancement
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.
The current documentation for
VectorN.normalized()
does not explicitly state what happens if you normalize a zero-length vector. As there are at least two logical outcomes (a divide by zero error orVectorN.Zero
), it is worth it to specify how godot handles this case; something which is potentially further confused by the note RE potential odd behavior when the vector length is very small.This change simply adds the clarifying note that normalizing a zero-length vector will return
(0,0)
,(0,0,0)
, or(0,0,0,0)
, depending on the vector size normalized.