Why AtomReference does not use AtomBaseVariable as Constant? about unity-atoms HOT 7 CLOSED

@icaro56 I added the option to use a Constant in Atom References in commit 299dc19. Use the latest canary version if you want to use it.

from unity-atoms.

it is such that you can provide your level designers the oportunity to put a fix number in there without the need of creating an asset.

note: IntConstant derives from AtomBaseVariable also IntVariable does so. this means: you can put a AtomConstant into the AtomVariable option of an AtomReference

The architecture is based on this talk: https://www.youtube.com/watch?v=raQ3iHhE_Kk

from unity-atoms.

Ok, thank you by explanation.

from unity-atoms.

But by some reason the StringConstant is not aceptable on StringVariable field when I use the StringReference

from unity-atoms.

Ah okay i see.

@AdamRamberg

References use "hardcoded" the variable like here: public class StringReference : ScriptableObjectReference<string, StringVariable, StringEvent, StringStringEvent> { }

"StringVariable" in the generic argument. I think this "should" be ScriptableObjectVariableBase<string> ¹ but I'm unsure whether or not this would still be serializable.
I'll try to test it this evening, but maybe you're faster than I am

[¹]: because AtomVariable and AtomConstant have the same common ancestor (VariableBase), this would be needed to use both in there

from unity-atoms.

I understand. Thank you. Your plugin is fine! I am using the canary version. May the force be with you!

from unity-atoms.

"StringVariable" in the generic argument. I think this "should" be ScriptableObjectVariableBase 1 but I'm unsure whether or not this would still be serializable.

okay, you can't use a generic argument at this position - it will not serialize anymore.
thats a bummer .

we could add a third option to reference to also allow a AtomConstants option.

when 2020.1 hits this can be restructured altogether with SerializeReference

from unity-atoms.