We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Tested in Godot Engine v4.4.beta2.official.a013481b0
Godot v4.4.beta2 - Linux Mint 22.1 (Xia) on X11 - X11 display driver, Multi-window, 2 monitors - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4060 Laptop GPU - AMD Ryzen 7 8845HS w/ Radeon 780M Graphics (16 threads)
When using renamed signal from Node in @tool script it will be emitted twice on single rename operation from Scene dock.
renamed
@tool
CustomNode
RENAMED
When project is running there should also be button to change node name. It will trigger this Output message only once, but logic stays the same.
issuewithrename.zip
The text was updated successfully, but these errors were encountered:
Can confirm, also happens in 4.3 and 4.2.2
Sorry, something went wrong.
This is due to this code:
godot/editor/gui/scene_tree_editor.cpp
Lines 1574 to 1575 in 0b6a717
Related to:
No branches or pull requests
Tested versions
Tested in Godot Engine v4.4.beta2.official.a013481b0
System information
Godot v4.4.beta2 - Linux Mint 22.1 (Xia) on X11 - X11 display driver, Multi-window, 2 monitors - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4060 Laptop GPU - AMD Ryzen 7 8845HS w/ Radeon 780M Graphics (16 threads)
Issue description
When using
renamed
signal from Node in@tool
script it will be emitted twice on single rename operation from Scene dock.Steps to reproduce
CustomNode
.RENAMED
message in Output dock twice, but it is expected to show only once.When project is running there should also be button to change node name. It will trigger this Output message only once, but logic stays the same.
Minimal reproduction project (MRP)
issuewithrename.zip
The text was updated successfully, but these errors were encountered: