LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

coerce input sometimes fails

Hi LVers:
I am building an executable with LV8.6.1 that is doing something I don't understand.  I have 6 controls that are used to set some percentages for calculations, so they should only be allowed to take values from 0 to 100.  I set the input limits for these 6 controls to coerce, but in the built executable running on WinXP, 5 of them don't restrict the user inputs.  The 6 controls (SGL type) are all adjacent on the panel, all seem to be set identically, but only the one that shows its label works and the 5 others with hidden labels don't.  I am at a loss to explain this.  Has anybody else seen this happen?
bjlv
0 Kudos
Message 1 of 5
(2,941 Views)

Hey,

 

Do you have the 8.6.1f1 patch installed?

For me it sounds similar to one of the problems fixed there.

 

Christian

0 Kudos
Message 2 of 5
(2,925 Views)

Hey bjlv,

 

Just to walk through how you are setting the user input limits; Are you right clicking on the control and going to Properties»Data Entry and then setting these parameters there?

 

Does this same behavior occur with other data types? Does this same behavior still occur if you use property nodes to programmatically set the various properties? Does everything seem to work as it should in the development environment?

 

Sorry to answer a question with a series of questions. But perhaps, if nothing else, a work around can be found.

Hope this helps.
-Ben

WaterlooLabs
0 Kudos
Message 3 of 5
(2,905 Views)

Q

 

This only happens in the built app or do you see the same thing in the development environment?

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 4 of 5
(2,899 Views)

Hi All:

I was out dealing with a sick daughter on Friday, but I have had a chance to work on this enough to now know that I was seeing the 8.6.1 bug referenced by the patch Christian_M said I needed.  I actually implemented the property node workaround first, and I will test the patch next, as that is a faster way to ship a program minutes from its deadline.  Anyway, thanks all for the assistance on this, and I will have to also look into why my search of NI.com didn't turn up this problem when I looked last week.  I suppose I didn't use just the right keywords in my search.

bjlv

0 Kudos
Message 5 of 5
(2,863 Views)