> For simplicity's sake, lets say I have a cluster with one boolean
> control named "OK". Is there a way I can set it up so that the event
> for OK->value changed is executed whenever I write the entire cluster?
> I'm only interested in executed that event when one particular element
> of my cluster has changed. I have tried to wire a cluster wire to a
> local variable of the cluster and to a property node with
> value(signaling) property selected. Neither of these signal the event.
> Is there a way?
You really don't want to go down this road. The signaling property is
there to make a few simple things easy, but it is not the cornerstone
you want to design your application around. If you have code you want
to execute, place it into a subVI and cal
l the subVI. If it difficult
to put in a subVI, you can also leave it in your top VI and make it
conditional. In the cases you want it executed, send out the TRUE
condition.
I know this may sound way to rigid, but as your app grows, and as you go
away from it and come back, you will find that the magical side effects
of writing to controls and indicators will surprise you in the most
unpleasant of ways. If you make a subVI, you get to decide all of the
params, and the order of execution.
In otherwords, events are cool for dealing with the UI, and for
asynchronous notifications, the user events give you an alternative to a
queue and notifier that can be handled in the same structure if that is
what you need. But try not to use them when a function call is what you
really want.
Greg McKaskle
