OK, here's a puzzlement. Just playing with this, made a little demo. I take a child class object and cast its parent object onto it. I then use it to call a Dyno-Dispatch method to see what happens. This method only has any functionality at the child level - methods 'above ' the child level are empty shells.
What puzzles me is this: double-clicking on the child method gives the 'Choose Implementation' dialog box. It shows my child level method, yep yep, but its parent ("Stepper Controller Class" in this case) is grayed out. The magic arrow glyph points to my child class' grandparent, "Motion Controller Class". The Help tells me:
"The arrow glyph indicates the implementation that executes if the run-time data type on the wire is the same as the edit-time data type on the wire. Because a LabVIEW class wire can carry data of its own type or data of any child type, this glyph indicates that the implementation LabVIEW executes at run time will be at the glyph level or below in the class hierarchy.
LabVIEW lists all classes in the LabVIEW class hierarchy. If a class inherits the dynamic dispatch member VI from an ancestor class but does not have its own implementation, LabVIEW dims the class in the Select VI list."
Now, I verified that the child class method functions as expected. All class methods 'above' the child are just empty shells. So I know that the method actually run at run time is that of the child's. But the magic glyph points to the grandparent class. So does that mean that the compiler, at edit time, doesn't yet know which implementation to use, but 'figures it out' at run-time? Am I overthinking this? Still puzzled, paul
