tab refnum coercing dot

[Blokk]

Hello,

I have created a simple subVI (attached), what I would like to use whenever I need to enable or disable states of any TAB control.

However I can see there is a coercing dot when I connect a reference to the TABcontrol refnum input terminal. I am not familiar with labview classes, could someone give me a brief explanation, and tell me, is this a problem, or not? And how I can do a proper reference pass into a subVI.

(I do not have such a problem if I just use directly created property nodes on the top VI, however, I like to hide such a elements into subVIs)

Thanks!

[P@Anand]

Please post your code in 2011 version

[Blokk]

here it is

[P@Anand]

Right click the Tab control refnum and Enable the Include data type. I don't have a good explanation for this.

[Blokk]

If I enable the Include data type, the wire between the TAB (I use two different TAB controls in my main VI with this subVI) reference, and the subVI input terminal gets broken. If I check it with help, I get this info:

Strange, because I made a test VI to reproduce this behaviour, with only including one TAB control. With this test VI, your solution works.

Can be the problem that, I try to set the state of two different TAB controls? And one of them is inside the other?

[Blokk]

I try to reproduce the problem, but even if I put 3 TAB controls into each other, the solution works.

But it gives me class conflict in my main project VI.... 😞

[RavensFan]

Attach the VI or VI's that show the problem.

What you attached earlier doesn't show a problem, nor a coercion dot.  Your image in your first post doesn't show a coercion dot either.

[JÞB]

Have I even mentioned that I avoid Tabs.  (Yes, often! that was a rhetorical question)

We call them "Tab Controls" and they have a value BUT, they are containers.  like panes and panels. (they have values too.)

Tabs have some uses.  but they have a few challenges they inherit from the OS too.

[Blokk]

Hello,

I am not in the lab anymore, I will try to extract the problematic part from my main VI, and I will post it here tomorrow.

Regards,

[altenbach · Accepted solution]

Tab controls are similar to enums (e.g. if you wire them to a case selector, you can create cases for each tab), so each tab control is different in exact type. Your subVI is for a generic tab control, not a specific instance.

You can safely ignore the coercion dot, it just alerts you to that fact.

(Similarly, if you wire two different tab terminals to an equal funcion, you get a coercion dot on each input.)