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

Wrong node in inspector after drag&drop in tree and a delay #93935

Closed
Hilderin opened this issue Jul 4, 2024 · 1 comment · Fixed by #94105
Closed

Wrong node in inspector after drag&drop in tree and a delay #93935

Hilderin opened this issue Jul 4, 2024 · 1 comment · Fixed by #94105

Comments

@Hilderin
Copy link
Contributor

Hilderin commented Jul 4, 2024

Tested versions

  • Reproducible in 4.3 master (e6448ca)

System information

Test Godot v4.3.beta.mono (6a13fdc) - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 (NVIDIA; 31.0.15.3742) - 11th Gen Intel(R) Core(TM) i5-11600KF @ 3.90GHz (12 Threads)

Issue description

When drag&dropping a node over a container, sometimes, the inspected node is still the container in the inspector.

I think it's a follow up of #91254

godot.windows.editor.dev.x86_64.mono_xxVPIJqE8o.mp4

Steps to reproduce

  • Drag a node over the bottom of a container
  • Wait for the highlight to appear on the destination node
  • Drop the node
  • In the inspector, the combo with the name correspond to the dragged node but the properties are the properties the container node. I think it should display the properties if the dragged node (the select node)

Minimal reproduction project (MRP)

test-godot-crash-drag-drop.zip

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

Successfully merging a pull request may close this issue.

3 participants