Controls[] Property don't give a right refnum of a type def LV2010 OK, LV2012 BAD

[CFiset]

Same code. Into LV2010, the answer is TRUE and in LV2012, the answer is FALSE.

This cause me trouble.

[RavensFan]

It would be better to attach the actual VI's or use the Code Capture Tool.  The built-in LabVIEW snippet maker mangles references.

In both cases, you are indexing out the 0th control.  Perhaps when the VI was recompiled for LV 2012, the order of the controls was changed and the 0th control is no longer the zeroth.

Instead of using Index Array, compare your reference to the entire array of controls to get an array of booleans.  See if one of the other indices comes up as a match.

[P@Anand]

Ignore this.

[CFiset]

Sorry for the confusion. Even this example give me different answer into LV2010 and LV2012

Please, try this attachments

[RavensFan]

LabVIEW 2011 seems to behave just like LabVIEW 2012.

I found this thread.  http://forums.ni.com/t5/LabVIEW/Control-reference-bugs-LV2011/m-p/1893991 which seems to discuss the same issue regarding control references and typedefs.

Also:

http://forums.ni.com/t5/LabVIEW/typedef-and-strict-typedef-control-vi-server-reference-issue-LV/td-p...

It looks like CAR# 323101.

[CFiset]

This is also true form a reference comming from the ctrlref on an event case??? I will need to test that tomorrow because if this is the case, I may jump over the ugrading to labview 2012 and wait for this issues to be solved.

[CFiset]

The CtrlRef Value form Event Structure is equal to the reference of Numeric Value.

Example in LV2012

[CFiset · Accepted solution]

Do you think this can be a workaround ?

[RavensFan]

That should work as long as you have unique labels for all of your controls.  No unlabeled controls and no controls that have the same label such as two called "Temperature".

[CFiset]

Thank you