11-01-2016 01:51 PM
Hi all,
Can anyone explain the broken wire in the attached vi?
LV2014SP1 64b
It seems that LabVIEW won't accept to register a value change event on a cluster containing more than 1 boolean control ref, unless there is also a non boolean control ref in the cluster.
Weird, no?
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus
Solved! Go to Solution.
11-01-2016 02:08 PM
I was able to duplicate on LV 2015 32 bit.
Also, it seems to have something to do with the order of the cluster. See:
11-01-2016 02:21 PM
The Mechanical Action plays a role here.
Change to "switch" rather than "latch" and all variations work.
steve
11-01-2016 02:26 PM
Try adding a cluster to array in the broken case as a work around
11-02-2016 02:45 AM
Hi!
OEM_Dev seems to be right. Using a build array instead of a build cluster function helps to workaround.
I will look a little closer at the issue and file a CAR if necessary.
Regards,
Christoph
11-02-2016 03:03 AM - edited 11-02-2016 03:04 AM
Steve,
Shouldn't it work whatever the mechanical action? I think it should.
And :
1 switch : ok
1 latch : ok
1 switch & 1 latch : ok
2 switch & 1 latch : not ok
2 switch & 2 latch : not ok
2 switch & 2 latch & 1 num : ok
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus
11-02-2016 03:09 AM - edited 11-02-2016 03:15 AM
Christoph,
Replacing the build cluster with a build array confuses me... how do I do then to set my event structure to catch each separate value change?
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus
11-02-2016 04:23 AM
> Steve,
> Shouldn't it work whatever the mechanical action? I think it should.
Agreed. I just wanted to add a data point for investigators.
steve
11-02-2016 07:15 AM
I don't use dynamic events much, but my understanding was that either an array or a cluster would be used to run a single event frame when the specified event happens on any of the specified controls.
11-02-2016 11:32 AM
Use the "CtlRef" output inside the structure to find out which one was pressed. Here I use a "Search 1D array" to find the index, but you could also get the label text or use any other property node you feel like.