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

Always look for unique node names in owner if not found in owned nodes #89686

Merged

Conversation

kleonc
Copy link
Member

@kleonc kleonc commented Mar 19, 2024

Makes unique node names work consistently for subscene root nodes.

Resolves #66536.

If this will be approved I'll follow up with with docs (in manual) update etc. later.

@kleonc kleonc added this to the 4.3 milestone Mar 19, 2024
@kleonc kleonc requested a review from reduz March 19, 2024 21:21
@kleonc kleonc requested a review from a team as a code owner March 19, 2024 21:21
Copy link
Member

@reduz reduz left a comment

Choose a reason for hiding this comment

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

This makes sense, I guess it was an oversight on my part

@kleonc
Copy link
Member Author

kleonc commented Mar 20, 2024

Marked for cherry-picking to 3.x (3.6), not sure whether should be done for 4.2, 3.5 etc.

@akien-mga akien-mga closed this pull request by merging all changes into godotengine:master in 06abc86 Mar 24, 2024
akien-mga added a commit that referenced this pull request Mar 24, 2024
…hen-in-owner

Always look for unique node names in owner if not found in owned nodes
@akien-mga
Copy link
Member

Thanks!

@kleonc kleonc deleted the unique-node-names-check-owned-then-in-owner branch March 24, 2024 08:37
@akien-mga
Copy link
Member

Cherry-picked for 3.6.

@akien-mga akien-mga added cherrypick:4.2 Considered for cherry-picking into a future 4.2.x release and removed cherrypick:3.x Considered for cherry-picking into a future 3.x release labels May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug cherrypick:4.2 Considered for cherry-picking into a future 4.2.x release topic:core
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Getting scene unique node from subscene's root fails/succeeds if subscene has any/no unique nodes itself
3 participants