The overall behavior is the same -- the value of the control is updated.
The benefit of the value property is that you can set the value at the
same time as other properties and you can set it from other VIs.
The down side of the value property is that it can cause debugging
confusion when you have too many of these remote value changes. The
other downside is that value property is new and doesn't have as many
optimizations as the local or terminal. So for now, there are cases,
such as writing the same value over and over that are slower to the
property node than to the local.
My guideline is to use the terminal first. It is the most efficient and
it makes the diagram easiest to read in my opinion. If the UI requires
that you set the value on a
control, such as when you are initializing
the values, use a local or a property node depending on whether it
happens in the local diagram or in a remote subVI diagram. Do not use
either locals or property values as you would variables in another
language. They are for the UI and for subVI parameters. The rest
should be done with wires and shift registers, otherwise the LV compiler
has no choice but to make lots of buffers and buffer copies and this
will greatly affect your performance. I won't go into the details as to
why, since I'm not sure if this is in anyway relevant to what you were
asking, but ask again if you would like more info.
Greg McKaskle
