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

Display Autoloads in the inspector node selection window #6927

Closed
thornySoap opened this issue May 21, 2023 · 2 comments
Closed

Display Autoloads in the inspector node selection window #6927

thornySoap opened this issue May 21, 2023 · 2 comments

Comments

@thornySoap
Copy link

Describe the project you are working on

A simple beginner Flappy Bird fake with an SettingsHandler-Singleton of type ResourceHandler autoloaded. I want to add a settings screen, for which I use a ResourceElement-UI element. ResourceElement has a variable of the type ResourceHandler exported.

Describe the problem or limitation you are having in your project

I want to assign the Autoload to the settings-ResourceElement. But for this simple thing I need to create an extra script for it which seems weird to me:

extends ResourceElement

func _ready() -> void:
    resource_handler = SettingsHandler

Describe the feature / enhancement and how it helps to overcome the problem or limitation

Since Autoloads are always "there" no matter if running the main or any other scene alone, they could be shown in the "Select a node" popout in the inspector:
Screenshot 2023-05-21 17:00:55
__

Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams

The Autoloads could be shown above the root node.

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

Yes

Is there a reason why this should be core and not an add-on in the asset library?

N/A

@theraot
Copy link

theraot commented May 21, 2023

Related: #4993

@thornySoap
Copy link
Author

Related: #4993

Thanks, if this gets implemented my issue would be fixed as well

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