Skip to content
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 some mixups between 2D/3D in documentation #79781

Merged
merged 1 commit into from
Jul 24, 2023

Conversation

AThousandShips
Copy link
Member

@AThousandShips AThousandShips commented Jul 22, 2023

Unsure if there are other cases but seems to mostly have caught all

If the changes are considered too minor compared to the impact on translation I can limit it to only cover the incorrect links, which I think should be fixed at minimum as they will throw people off

@AThousandShips AThousandShips added this to the 4.2 milestone Jul 22, 2023
@AThousandShips AThousandShips requested a review from a team as a code owner July 22, 2023 09:50
@@ -230,8 +230,8 @@
- [code]type[/code]: Always [constant NavigationPathQueryResult3D.PATH_SEGMENT_TYPE_LINK].
- [code]rid[/code]: The [RID] of the link.
- [code]owner[/code]: The object which manages the link (usually [NavigationLink3D]).
- [code]link_entry_position[/code]: If [code]owner[/code] is available and the owner is a [NavigationLink2D], it will contain the global position of the link's point the agent is entering.
- [code]link_exit_position[/code]: If [code]owner[/code] is available and the owner is a [NavigationLink2D], it will contain the global position of the link's point which the agent is exiting.
- [code]link_entry_position[/code]: If [code]owner[/code] is available and the owner is a [NavigationLink3D], it will contain the global position of the link's point the agent is entering.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confirmed from the code

@YuriSizov YuriSizov merged commit 3ca4943 into godotengine:master Jul 24, 2023
13 checks passed
@AThousandShips AThousandShips deleted the doc_dim_fix branch July 24, 2023 17:43
@YuriSizov
Copy link
Contributor

Thanks!

@AThousandShips
Copy link
Member Author

At least some of these changes needs to be cherry picked for 4.1

@AThousandShips
Copy link
Member Author

AThousandShips commented Aug 24, 2023

It does seem to be trivial to cherry pick for 4.1, tagged, remove if it isn't correct.

@AThousandShips AThousandShips added the cherrypick:4.1 Considered for cherry-picking into a future 4.1.x release label Aug 24, 2023
@YuriSizov YuriSizov removed the cherrypick:4.1 Considered for cherry-picking into a future 4.1.x release label Sep 21, 2023
@YuriSizov
Copy link
Contributor

Cherry-picked for 4.1.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Page on 3D feature describes it as 2D
3 participants