For reference: rust is perfectly happy now:
#Why can I declare a type in one file, but not an identical type in another file?
worn basin
but, on another file, suddenly, this is not ok:
scratch that- even in the same file, it's not happy. Is there some rule that the Handle<T> cannot be owned by a struct?
scratch that- even in the same file, it's not happy. Is there some rule that the Handle<T> cannot be owned by a struct?
peak notch
Apparently, Assets are required to implement Uuid. so like, somewhere you're presumably using those structs as an asset? try making a new struct you don't use anywhere and it should be able to own a Texture / Handle<Texture> no problem
worn basin
Apparently, Assets are required to implement Uuid. so like, somewhere you're pre...
Yes, I have done this, in screenshot 3
peak notch
to be clear, this is the part that i think is saying assets must implement Uuid
--> ~\.cargo\registry\src\github.com-1ecc6299db9ec823\bevy_asset-0.8.0\src\handle.rs:106:8
|
106 | T: Asset,
| ^^^^^ required by this bound in `bevy::prelude::Handle`
this is the definition of that Asset by the way
worn basin
oh i see, it's a Handle that makes it an Asset
am I understanding that by adding Handle into my struct as a member, it is now using a trait?
peak notch
yep, that's what that says, T must be an Asset
and the other one says that Asset must implement TypeUuid. so if Texture doesn't implement that, it can't be an asset.
worn basin
looking at the source, there is no mention of Asset in the texture.rs file- but implementations can exist outside of the same file the struct was defined in, right?
even though that would be mean and nasty?
peak notch
i imagine on the Bevy side, you probably need some other type that like holds a texture and implements Asset
that's my guess tho, i have very little bevy experience
worn basin
i imagine on the Bevy side, you probably need some other type that like holds a ...
well, that's what is shocking me, is this same type is somehow valid:
peak notch
that is weird