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

Connecting signal from Node panel deselects node #46035

Closed
bmolyneaux opened this issue Feb 14, 2021 · 3 comments
Closed

Connecting signal from Node panel deselects node #46035

bmolyneaux opened this issue Feb 14, 2021 · 3 comments

Comments

@bmolyneaux
Copy link
Contributor

bmolyneaux commented Feb 14, 2021

Godot version:
3.2.3.stable

OS/device including version:
Windows 10 Pro

Issue description:

Godot automatically deselects the node when connecting signals in a scene. See reproduction steps.

When connecting several signals through the Node panel, it's tedious having Godot automatically deselect the node, since you have to reselect the node after connecting each signal.

I don't care for Godot automatically opening the text editor when you connect a signal, but I don't see any reason why deselecting the node is desireable. There's nothing useful in the Node or Inspector panels for a .gd file. I think this is just a bug.

Steps to reproduce:

  1. Connect a signal from the Node panel
  2. Godot automatically opens the gdscript in the text editor for the node signal was connected to
  3. The original node selection is replaced with the .gd file being selected
@Calinou
Copy link
Member

Calinou commented Feb 15, 2021

I suppose the inspector for the script is opened because the editor technically "edits" the script to make it open in the script editor. I'm not sure if we can prevent that without significant refactoring.

@wjl
Copy link

wjl commented Jun 14, 2023

Just to ping on this, I'm using Godot 4.0.3 in 2023 and came here to report this bug today, but found this was already reported for Godot 3.2.3 more than 2 years ago.

This is a significantly annoying issue when you have multiple signals to connect from a node.

Please consider fixing this, it's very surprising and disconcerting behavior that significantly affects usability.

@YuriSizov
Copy link
Contributor

This is a duplicate of #21950, so consolidating there. #54071 would fix it.

@YuriSizov YuriSizov closed this as not planned Won't fix, can't repro, duplicate, stale Jun 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants