Add documentation for Physics2DDirectSpaceState.intersect_point_on_canvas
#35988
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
I've added a description for Physics2DDirectSpaceState.intersect_point_on_canvas() that reflects its current behaviour but I strongly suspect that its current behaviour isn't its intended behaviour. Should this change be committed?
seenloitering
force-pushed
the
doc-Physics2DDirectSpaceState
branch
from
b3d586f
to
ff5d05e
Compare
|
Fixed a typo preventing compile. |
akien-mga
changed the title
akien-mga
changed the title
Physics2DDirectSpaceState.intersect_point_on_canvas
|
Sorry for the delay reviewing this. It seems like in the meantime this was superseded by #54577. Thanks for the contribution nevertheless! |
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.
I've added a description for
Physics2DDirectSpaceState.intersect_point_on_canvas() that reflects its
current behaviour but I strongly suspect that its current behaviour
isn't its intended behaviour. Should this change be committed?