Syntax for Preloading Exported Variable

marty

If you are using EXPORT to expose a variable in the inspector panel, how can you also preload it?

Is there any way to preload an exposed variable?

[Edit for succinctness]

marty

Something like this would be great, but sadly, it makes the parser cry:

onready var explosion_res = preload(export (PackedScene))

TwistedTwigleg

I think preload returns a PackedScene, so in theory the PackedScene you pass in through the editor should already be pre-loaded, or at least that is what I thought until I did some looking around.

I looked through the documentation, and did some quick Google searches, and I could not finding anything on preloaded exported variables. I also couldn't figure out if exported variables are preloaded or not either. Now I'm not really sure, and my guess is the best way to know for sure would be to poke around at the source code.

Out of curiosity, is there any reason you need to preload a exported variable?

marty

Heya, TT!

I want to export the variable so that it is populated via the inspector. I always prefer linking resources via the inspector because they are less likely to break (ie. when renaming linked nodes, etc.) and when they do break, you don't have to go digging into scripts to fix them. Inspectors rock. ;-)

But, I need to explicitly preload because the asset that I'm having trouble with doesn't appear to be preloading. Like you, I thought export-linked resources were inherently preloaded, but apparently not so, as I have one now that clearly hiccups the project the first (and only first) time it is instanced.

Ace_Dragon

Are you using Godot 3.0.6 or a build of Godot 3.1?

The inspector in Godot 3.0.6 lacks some capabilities that the redesigned inspector in 3.1 has (among them is some features related to variable export).

marty

Yup, 3.0.6. 3.1 sounds like a helluva upgrade. Sure would be nice if it helps here too.

So, I gather exported variables cannot be preloaded?

TwistedTwigleg

@marty said: Heya, TT!

I want to export the variable so that it is populated via the inspector. I always prefer linking resources via the inspector because they are less likely to break (ie. when renaming linked nodes, etc.) and when they do break, you don't have to go digging into scripts to fix them. Inspectors rock. ;-)

Hey Marty!

Thanks for explaining the use case!

I was just wondering because I have never needed to preload any exported assets before, but part of me was wondering if I am doing things the 'wrong' way so I never came across it.

(Side note: Not to say that I think there is no 'wrong' way, just different ways with different pros and cons, but I am always trying to learn new things)

I do generally rely on having exported variables for the very same reason: They are easy to fix if they break, and you do not have to change hard coded values when/if they break.

Another added bonus I found with exported variables is you can easily make a bunch of variation on a bunch of different scenes just by changing the values, which is super handy when you have multiple things that all (more or less) act the same with small variations as you can use on script for all of them. :smile:

But, I need to explicitly preload because the asset that I'm having trouble with doesn't appear to be preloading. Like you, I thought export-linked resources were inherently preloaded, but apparently not so, as I have one now that clearly hiccups the project the first (and only first) time it is instanced.

Perhaps a issue/feature-request should be opened on GitHub to add this functionality?