I have a minimal LVOOP code, which manages a number of qualitatively similar tasks, depending on user input. Each selectable task is a child class of one main parent class.
Overwriting the "do" method of the parent class with specific child classes works.
However, each child class requires potentially different input variables to properly work (and thus have different connector panes).
My current (non-working) approach was to use an enum with a case structure that calls the correct initialization function and input variables for each child class. However, there is an error on the wires connecting to the initialization subvis. It states:
"You have connected a refnum of one type to a refnum of another type and both types are members of some class hierarchy, but there is neither a simple up cast nor type cast between the two classes."
So my questions are:
0) Is having child classes with differing private data incompatible with LVOOP? Is it better to get rid of the classes again?
If not:
1) How can I get rid of this error?
2) Should I use a different approach? (I would prefer to not bundle all possible private data clusters into a "supercluster", so that I have identical input to each child initialization method.)
3) Should I use a variant datatype to exploit polymorphic class methods?
4) Something else?
Attached is a minimal working example (LV 2018 64 Bit, Win10)
EDIT:
If casting to more specific type is necessary, should I wonder about any performance/memory issues?