No coercion using value signaling

[Jörn]

Why does no coercion takes place when using the value signaling property?

I understood, that LabView will react as if the user had interactively changed the value of the object. Thus, I would also include coercion (and use it for convenience in my project).

Please find attached an example VI. Pressing the "Set Numeric to value" allows to exeed the limits of the numeric object "Numeric".

Best regards

Jörn

[andre.buurman@carya]

In addition: It only seems to affect the value signalling an not the value property.

[StevenD]

Interesting. I also got it to set a value outside the bounds with a local.

Guess it's something we will have to be careful of.

[tst]

This behavior is by design.

In the past, the coercion would also work when programmaticaly setting the value, but in more recent versions, the limits only refer to what the user explicitly does. All programmatic access (including the value properties) can be coerced using the In Range and Coerce function.

I suppose this change was made because it gives more power to the user, but I don't know the exact reasoning.

[Jörn]

That this behavior is by design is not entirely satisfying. I hoped that LabView can do the job "looking after variables to be in range" for me. Using the In Range and Coerce function need some little programming effort for each variable to be controlled. Now it would be interesting to understand the reason for this design.

To André: With LV 8.5 also the value property does not coerce the value.

Regards

Jörn

[TCPlomp]

It also applies to VI connectors, I thought that was the main reason to make a distinction between a 'user' and 'code'

Ton