LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

In Range & Coerce not passing coerced LV2020


@richjoh wrote:

On a second look at the description, I know why this function threw me out to left field.  The icon description labels the output numeral as "coerce".  Yet the text explicitly says the numeric is not coerce only the bool, (In Range?).  Need to be changed to reflect the instructions.

 

coerced-NoItIsNot.PNG


But it is coerced! Just not with observing if the limits should be included or not! They always are included. If you pass in a value that is bigger than the upper limit, you get the upper limit as coerced output. And accordingly with the lower limit.

Rolf Kalbermatter
My Blog
0 Kudos
Message 11 of 13
(362 Views)

I edited my response, the check box feature is the issue, not whether it coerces.  I lost count on the amount of time I have to go back and put in the -1 because I want a loop index to stay within a range.

 

I agree with you post.  The context menu checkbox to include upper/lower should be removed.

0 Kudos
Message 12 of 13
(356 Views)

@richjoh wrote:

 

I agree with you post.  The context menu checkbox to include upper/lower should be removed.


That's not an option. This would break existing code when upgrading to the newer version that does not have this feature anymore.

Rolf Kalbermatter
My Blog
0 Kudos
Message 13 of 13
(347 Views)