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

Don't open the bottom panel when selecting nodes (such as Shader or AnimationTree) #1509

Open
vitorbalbio opened this issue Sep 14, 2020 · 2 comments

Comments

@vitorbalbio
Copy link

Describe the project you are working on:
Space Tactical RPG https://twitter.com/ZeroPointGame

Describe the problem or limitation you are having in your project:
This proposal is part of a much more complete UI/UX overhaul and should be considered with this view about Godot Editor problems and possible solutions: #1503

Screen Setup is Arbitrarily Changed by Clicking in Objects

JvhqC7hham

There's something that is quite annoying with the current Godot editor design and is the bad habit of change the screen. I see the good intentions of it, but it's childish and annoying as hell!
Currently everytime you click in a Shader it opens the shader editor, everytime you click in a AnimationPlayer it opens the animator, you click to play it shows the Output even if i just closed it right now! At first it can look great but it's not, once you start to configure the window for the user he loses agency about how he want to see his screen and what is the most important for he now. It get's worse. It's not even currently consistent. E.g when you click in some file in the FileSystem it do not show the Import Option. When you click in any audio element in the Scene it do not open the Audio settings in the bottom panel. It's totally arbitrary and a design decision not compatible with modern softwares.

This behavior is also not fully compatible with a more customized UI as proposed here: #1508

Describe the feature / enhancement and how it helps to overcome the problem or limitation:
Describe how your proposal will work, with code, pseudocode, mockups, and/or diagrams:

Disable this behavior by default and add a option to enable it in the editor settings or vice versa.

This is partially addressed here: godotengine/godot#40438 and the Output setup Panel can already be disabled as noted by @Calinou in #1503 "You can disable this in the Editor Settings: Run > Output > Always Open Output On Play"

So there's no point in not extend this to all panels not only those selected ones.

If this enhancement will not be used often, can it be worked around with a few lines of script?:
Will be used Often

Is there a reason why this should be core and not an add-on in the asset library?:
It's a core editor feature.

@vitorbalbio vitorbalbio changed the title Stop Changes in Active Panels when Selecting Objects. Stop Changing Active Panels when Selecting Objects. Sep 14, 2020
@Calinou Calinou changed the title Stop Changing Active Panels when Selecting Objects. Don't open the bottom panel when selecting nodes (such as Shader or AnimationTree) Sep 14, 2020
@KoBeWi
Copy link
Member

KoBeWi commented Sep 14, 2020

Maybe Godot should just remember for each panel if it was expanded or not. I for example want to edit Shader every time I click it in the inspector, so I'd like the panel to be expanded. Adding a project setting for each sub-editor sounds like overkill.

Animation is especially annoying. When you accidentally click an AnimationPlayer it might cause changes to your scene that you can't undo.

@vitorbalbio
Copy link
Author

vitorbalbio commented Sep 14, 2020

Maybe Godot should just remember for each panel if it was expanded or not. I for example want to edit Shader every time I click it in the inspector, so I'd like the panel to be expanded. Adding a project setting for each sub-editor sounds like overkill.

Hi @KoBeWi . I think it would be much easier to implement if it was just one boolean in the editor settings to keep the current behavior or disable it and never change any panel at all.

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

2 participants