LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Can we use an XControl Reference in a Class?

Solved!
Go to solution

LabVIEW help states that "A private data control cannot contain an XControl or an XControl refnum", while previous comments have shown that problems occur in a built application, but not in the development environment: http://forums.ni.com/t5/LabVIEW/X-Control-Distribution-Bug/td-p/1132058  This issue appears to have been given the CAR #210033 http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Allow-X-Control-X-Control-Reference-as-a-Class-Data-Me... with the note that it only relates to the XControl Reference, not the XControl itself, as a member of the Class private data.

 

I've just tried a simple application with a XControl Reference inside the Class private data, and it seems to work without any errors both in development and in the built app (LabVIEW 2012 SP1 f3 (12.0.1f3) 32-bit).  I've looked through the last few lists of Bug Fixes, and cannot find this CAR in any (2011 or 2012), though the documents do say they only list a "subset".

 

Can someone confirm for me whether CAR #210033 has been corrected?  I don't want to go too far down this track if it will introduce problems at some unknown stage.

 

0 Kudos
Message 1 of 6
(3,364 Views)
Solution
Accepted by topic author GregSands

According to the CAR database, this CAR was fixed in LabVIEW 2010.

Message 2 of 6
(3,362 Views)

Thanks - I didn't check back far enough.

0 Kudos
Message 3 of 6
(3,351 Views)

Having said that, perhaps the Help page http://zone.ni.com/reference/en-XX/help/371361J-01/lvhowto/defin_priv_data_class/ should be updated.

0 Kudos
Message 4 of 6
(3,337 Views)

I have filed CAR 415298 to have the documentation updated.

Message 5 of 6
(3,307 Views)

I am using LV 2013 and am unable to add an xcontrol to my class' private data. Should I be able to do this?

 

Edit: saw this response from AQ

 

"An XControl defines an appearance, not a data type. The data inside a private data control is never visible. It does not make any sense to put something appearance based into the class definition. They were deliberately ruled out.

 

Ruling out an XControl Reference is not intentional."

0 Kudos
Message 6 of 6
(3,211 Views)