Thanks for the idea Kyle, but your suggestion adds some extra work to the other work-around : simply adding a numeric control ref in the cluster, it doesn't create any problem and lets me use the event structure in a "normal" way.
We have two ears and one mouth so that we can listen twice as much as we speak.
I just tested the demo VI with LabVIEW 2016 and there is no error in connecting two latched booleans to the value change registration (see attached VI snippet). LabVIEW 2015 SP1 still gave me the error.
So in my opinion this is an error that is already fixed and there is a workaround for older versions that Kyle97330 thankfully explained nicely.
Any questions left open?
Shouldn't it work whatever the mechanical action? I think it should.
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
The logic seems to be on the Last element, it's not allowed to be latch. Do the 2016 release notes mention it?
The error in connecting two latched booleans to the value change registration still exists in LabVIEW 2020 (see attachment). The above mentioned work around (wiring a non-boolean to the last cluster elements) still works.