Value (Signalling) call on a non-strict table reference causes error 1058 in LabVIEW 8.5

[Jaegen]

There appears to be a bug with the "Value (Signalling)" property for a non-strict table in LabVIEW 8.5.

In the attached VI, the first call does not generate an error, but the second (after casting the reference to be non-strict) does.

Am I missing something?

Jaegen

[Darren]

If you right-click on the Table control reference and choose Create > Constant, you'll get a "Table (strict)" reference constant, which, when used with To More Specific Class (instead of the "Table" reference constant), causes the code to work ok.  If you're looking to create a control reference control that you can use in a subVI to pass in the control reference, check out this nugget, where I show how to create one on the front panel that uses the correct datatype for the control.

Good luck,
-D

[Ben]

Did someone leave the door to ivory tower open again?

Thanks for visiting stanger.

Ben

[Darren]

Notice the time stamp on my response...I had spent so long last night playing Guitar Hero III, I needed something to bring me back to reality before going to bed.  So I picked LabVIEW...  😉

-D

[Jaegen]

---

@Darren wrote:

If you right-click on the Table control reference and choose Create > Constant, you'll get a "Table (strict)" reference constant, which, when used with To More Specific Class (instead of the "Table" reference constant), causes the code to work ok.  If you're looking to create a control reference control that you can use in a subVI to pass in the control reference, check out this nugget, where I show how to create one on the front panel that uses the correct datatype for the control.

Good luck,
-D

---

Darren,

I understand all of this - the problem is that I have an existing GOOP class that uses a non-strict reference, and works fine in LV 7.1.1.  Also, everything else works fine except the "Value (Signalling)" property.  The work-around is simply to cast it to a strict reference before calling the property (see the attachment), but isn't this still a bug???

Jaegen

[Darren]

Ok, I verified that the behavior doesn't happen in LabVIEW 7.1.  It does happen in 8.0 and later, though.  I have filed CAR 4F1A1BF2 regarding this issue.  For now, the workaround of using a strict control reference should be sufficient.

-D