-
-
Notifications
You must be signed in to change notification settings - Fork 20.8k
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
Node Dock is not cleared when deleting selected node #84530
Labels
Milestone
Comments
I reproduced this in Macbook pro (2019) Ventura 13.3.1. |
Was this solved previously? I'm working on v4.0.3.stable.official [5222a99] and I can reproduce this: |
I think I have an idea of how to fix this issue, I'll look into coming up with a solution in the next week or two. |
guerro323
pushed a commit
to guerro323/godot
that referenced
this issue
Dec 13, 2023
YuriSizov
pushed a commit
to YuriSizov/godot
that referenced
this issue
Jan 25, 2024
Fixes godotengine#84530. (cherry picked from commit da84489)
GuybrushThreepwood-GitHub
pushed a commit
to GuybrushThreepwood-GitHub/godot
that referenced
this issue
Jan 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Godot version
4.2 beta4
System information
Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 (NVIDIA; 30.0.15.1403) - Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 Threads)
Issue description
When you select a node, the Node dock's signals and groups will point to that node. When you unselect it, the dock is properly cleared. If you instead delete the node, the dock content will stay and you can still make changes, which will go into the void (there is no way to restore the node without undoing the changes). What's worse, if you make a new scene and do the same to root node, it will result in editor crash.
Related is that the inspector does not fully clear either. The node header stays, the content is empty:
Steps to reproduce
Minimal reproduction project
N/A
The text was updated successfully, but these errors were encountered: