Test limits in numeric field in case value is written by property node

[SR_]

Hello, maybe its possible to integrate this feature: If I have an numeric input field with defined limits (e. g. 0 = minima, 5 = maxima, step = 1, coerce all on). Now I write a number in this field and Labview correct the input into the limits. In case I write a number by property node "value", the limits doesn't matter. I have to test the limits manually before writing in the numeric field by read out the limit properties and so on....

[tst]

This has already been suggested - http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Complete-Min-Max-handling-for-numeric-controls/idi-p/1...

See the comments there to see why it is unlikely that NI will do this.

[chris_d754]

Similar behavior happens when using local variables. This feels like a bug to me, but maybe those protections are only for user input? Not sure.

[Manzolli]

I figure out that when the value is changed using the property "Value", the coercing process work as expected. For the property "Val(Sgnl)" the limits are ignored. This is on purpose?

I made a small program to test it. If the "input" is placed in a value out of range and "Signaling" is turned on and off couple times, the "output" stays or of range! Or i'm missing something or there something really strange here.

[tst]

I would say that they should probably all behave the same way for consistency. Of course, since NI made the decision to ignore these limits, it's more likely that the change would be to set the Value property to ignore them too. Personally, I can't say I care too much either way.

[Intaris]

I wish we could add a value change or even data input filter event for controls, so that we could implement our own callbacks for exactly these kinds of scanarios.

[Darren]

Duplicate of http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Complete-Min-Max-handling-for-numeric-controls/idi-p/1...