LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Bundled dynamic event registration

Solved!
Go to solution

OK, I follow this (very nice) presentation, but I get stuck on the first Post -- why would you take a Boolean Reference and make a single-element Cluster out of it for the purpose of registering it for an Event?  Why not use the first formulation where you register the References directly?  What advantage does "clustering" the reference provide?  [I feel like I'm missing something obvious, but it's been a long day of removing three versions of LabVIEW from my Work Machine and reinstalling them because of a weird "feature" of NIPM 2019, you don't want to know ...  I think a CAR will be filed.]

 

Bob Schor

 

 

0 Kudos
Message 11 of 12
(482 Views)

@Bob_Schor wrote:

OK, I follow this (very nice) presentation, but I get stuck on the first Post -- why would you take a Boolean Reference and make a single-element Cluster out of it for the purpose of registering it for an Event?  Why not use the first formulation where you register the References directly?  What advantage does "clustering" the reference provide?  [I feel like I'm missing something obvious, but it's been a long day of removing three versions of LabVIEW from my Work Machine and reinstalling them because of a weird "feature" of NIPM 2019, you don't want to know ...  I think a CAR will be filed.]

 

Bob Schor

 

 


I like to mix User Events with DAQmx events. However, I need to modify my DAQmx Events on the fly. Not sure if this is a bug or intended use, but if I registered my events like below,

Snap10.png

in a cluster, I was able to dynamically change the Event Refnum inside the Event Case, like so

Snap11.png

If I did not use a cluster. I would get an error every time I tried to change the DAQmx event. Again do not know if this is intended behavior or not; I was just glad that something worked.

 

mcduff

Message 12 of 12
(478 Views)