Strange behaviour OOP Cohesion Dots

[Richard_Ha]

Is anyone able to explain the behaviour I'm seeing in the attached images.

When Class B isn't wired through the VI, the A2 class (a child of A1) is shown with a cohersion dot.

[James.M]

What the heck, didn't you already post this? I'm looking through your history and mine, though, and I can't find it. Did the admins delete your last post?

[Richard_Ha]

The previous post didn't have the correct images in so the question wasn't clear!

[James.M]

Oh, gotcha...

Anyways, now that you have both images shared, you've got me stumped. A class input has a coercion dot or no coercion dot based on how the VI wires its owning class, which has no inheritance link to the other class input.

It's weird, yes, but is this causing you trouble? Maybe someone who knows how LVOOP manages class wire-through can explain the behavior.

[Richard_Ha]

I don't think it's causing me any problems, tooka  while to find out what th cause of the dots on some VI's was and not on others. Just curious to see if anyone could explain it.

[James.M]

Ah, here's your solution. It's basically there just to show whether or not automatic downcasting was occuring. No performance hit like normal coercion dots, they just needed a way to show the difference and didn't have much room.