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

Selecting a script in the Scene tree dock should not display the Script resource in the inspector #77791

Closed
ghost opened this issue Jun 3, 2023 · 1 comment · Fixed by #84284

Comments

@ghost
Copy link

ghost commented Jun 3, 2023

Godot version

v4.0.3.stable.official [5222a99]

System information

Windows 11, AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx 2.10 GHz

Issue description

Is there any way to get the inspector to display information for the selected node(s) in the scene dock only ? Every time I press a "script" icon, add a signal connection or CTRL + mouse click on a user function in the script editor (to go to the script with that function), the inspector displays the properties of the script which in all cases I've experienced amounts to pretty much nothing. It interrupts the workflow because I have to keep clicking on the scene dock selection again to get the inspector to display the information I actually want. I'm wondering whether you could add a property to "Project Settings" that allows user control over whether this sort of hijacking occurs or not ?

Steps to reproduce

N/A

Minimal reproduction project

N/A

@Calinou Calinou changed the title Scene dock selections. Selecting a script in the Scene tree dock should not display the Script resource in the inspector Jun 9, 2023
@Calinou
Copy link
Member

Calinou commented Jun 9, 2023

Closing in favor of godotengine/godot-proposals#247 (specifically, wyattbiker's proposal in comments), as feature proposals are now tracked on the Godot proposals repository.

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.

1 participant