-
-
Notifications
You must be signed in to change notification settings - Fork 69
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
Add ResourcePath to refer to a resource without preloading it #9216
Comments
Check ResourcePreloader node. |
I've had a look, let's see how well ResourcePreloader fulfills the proposal...
So...none of those. Okay, perhaps I need to reword this proposal? |
What does that even mean?
But the ResourcePreloader meets this point. Also currently the editor is not able to update resource paths if said resources are not listed in scene dependencies. And if they are dependencies, they are loaded with the scene. If you want auto-updating paths without loading, it would require some new system. |
Well say you need a referenced for a PackedScene. You specify it as ResourcePath[PackedScene] so when you select it in the inspector, it doesn't show all derived from Resource, it only shows type of PackedScene
Yes, that's what this proposal is about. |
Looking through the source at how much would need to be changed, I think an annotation would work better than a dedicated type like |
This issue was referenced on mine, i have a nearly identical problem and opened the same issue. Did you manage to prototype some code to add the feature? |
Describe the project you are working on
N/A
Describe the problem or limitation you are having in your project
There's no project-friendly way to reference resources without preloading them. There's a plain string with
@export_file
tag, but that's fragile and ineffective.Describe the feature / enhancement and how it helps to overcome the problem or limitation
A new type called ResourcePath that the editor will track as if it were tracking an actual Resource.
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
If this enhancement will not be used often, can it be worked around with a few lines of script?
No.
Is there a reason why this should be core and not an add-on in the asset library?
It's a simple and obvious way to manage resource loading. It should be a core feature.
The text was updated successfully, but these errors were encountered: