You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is based on the staging branch and PR #183. I'm noticing the following things:
I can load a script using an asset path, e.g., "nano9://main.lua" using AssetServer. (This uses an additional source like this example.)
Then to make it run, I have to use only the path "main.lua" on ScriptComponent, which is ambiguous.
Is it expected to reference the script in ScriptComponent and load it? If it's expected that I must load and retain a Handle<ScriptAsset> it would be nice if ScriptId could be an asset path Cow<'static, str> or a Handle<ScriptAsset>.
The text was updated successfully, but these errors were encountered:
Generally yes script ID's are supposed to be asset paths, however they are derived from the asset path itself without the source. I can change this behaviour so path mappers can have access to the source as well, this way you could set a custom AssetPathToScriptIdMapper which will retain source information in the path
This issue is based on the staging branch and PR #183. I'm noticing the following things:
AssetServer
. (This uses an additional source like this example.)ScriptComponent
, which is ambiguous.Is it expected to reference the script in
ScriptComponent
and load it? If it's expected that I must load and retain aHandle<ScriptAsset>
it would be nice ifScriptId
could be an asset pathCow<'static, str>
or aHandle<ScriptAsset>
.The text was updated successfully, but these errors were encountered: