LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Index Values property of TABLE won't accept negative numbers

You are correct, I did contradict myself. I should have prefaced this post by saying this technique was used successfully when the indicator was an array, but the problem was all columns were the same size on the front panel, so I changed it from Array indicator to Table indicator so I could change the column widths, and created the Table Index Value property. I see now that the Array Index Value property coerced the negative numbers to 0 and the Table Index Value property does not. That explains why my changing the representation of the cluster from U32 to I32 makes it work, but doesn't explain how leaving it as U32 and adding an error indicator DOES make it work.

Thank you for your patience.

0 Kudos
Message 11 of 14
(489 Views)

Ah, that explains the mix up.  Arrays don't mind negative index values tables only like -1 (its the header index and how the header is diferentiated from the rest of the table )


"Should be" isn't "Is" -Jay
0 Kudos
Message 12 of 14
(483 Views)

And adding the error terminal just makes LabVIEW think that the error is being handled and therefore the auto error handler doesn't come into play.  But you are just masking your problem by doing that.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 13 of 14
(469 Views)

Note that you don't actually need an error indicator on the front panel; you can just wire the error wire to the "Clear Error" function, or any other bit of code that accepts the error as an input and doesn't have that error as an output. But as crossrulz notes, that's merely hiding the error rather than handling it, although in some situations that's the right thing to do.

0 Kudos
Message 14 of 14
(453 Views)