LabVIEW Idea Exchange

About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see in a future version of LabVIEW!
cancel
Showing results for 
Search instead for 
Did you mean: 

Allow X-Control/X-Control Reference as a Class Data Member

As per LabVIEW Help (pointed out by Jim_S - cheers) you cannot add an X-Control or X-Control Reference as a Class Data Member.

Well I found out (the hard way) that technically you can in dev time but at run time your build will be broken.

 

E.g. I would like the ability to add an X-Control Reference as a Data Member of a Class so that I can encapsulate display state changes whilst enjoying the benefits of Classes etc...

 

 Cheers

  

-JG

 

X-ControlReferenceAsClassDataMember.png

 


Certified LabVIEW Architect * LabVIEW Champion
9 Comments
Active Participant

This has been CAR'd as #210033 as per this thread

Certified LabVIEW Architect * LabVIEW Champion
NI Employee
Status changed to: Declined
Moved to CAR database. CAR#210033
Grant H.
National Instruments
LabVIEW Product Marketing Manager
Member

Man, declining this option really breaks my balls. No way of having a workaround?

Knight of NI

Okay Harlequinade.  Please try to use appropriate language for a public forum.

 

If you read the previous messages, you'll know why it was declined.  It's because it was determined to be a bug that had a Corrective Action Request assigned to it.  That actually gives it a higher probability of being fixed then if it was just a new idea to be implemented on how to improve LabVIEW.

Active Participant

Just stumbled upon this one today! Broke my code in a massive way. (but yesterday it was working perfectly!).

 

Bug fix does not seem to have made it into 2011 SP1 Smiley Sad

nrp
CLA
Proven Zealot

Ruling out an XControl is intentional behavior, and not a CAR.

 

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.

Active Participant

I just scanned the release notes for the recent versions and did not see this mentioned anywhere.  Safe to say the XControl Reference bug has not been fixed yet?

 

 

--
Tim Elsey
LabVIEW 2010, 2012
Certified LabVIEW Architect
Proven Zealot

Not only has it not been fixed, it has been flagged as "will not be fixed." Priority is just too low compared to all the other work to be done. Workaround listed: store a general Control refnum and use To More Specific to cast it to the specific type when you need to access specific properties. You can wrap that cast in a data accessor VI.

Active Participant

Got it.  Thanks, AQ

--
Tim Elsey
LabVIEW 2010, 2012
Certified LabVIEW Architect