LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

tab refnum coercing dot

Solved!
Go to solution

Thanks for the explanation, I think I get it. I also understand now, why I could not reproduce the class conflict with my example test.vi:

I had two identical TAB controls there. If you add an additional page with different name to one of them, and if you set "Include data type", here it comes the "class conflict error" with broken wire.

 

So I just ignore the coercion red dot in this case, thanks again for the clarification!

0 Kudos
Message 11 of 11
(232 Views)