LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Holding parallel loops until a certain state is reached - what is best practice?

I see, thanks. I think I'd need a QMH instead, since I need to know which event needs to be triggered. I was hoping that wasn't the case because wiring the queue everywhere is a real pain through all of the relevant loops etc.

0 Kudos
Message 11 of 13
(452 Views)

Hi VPI,

 

I was hoping that wasn't the case because wiring the queue everywhere is a real pain through all of the relevant loops etc.

Use named queues: no need to wire "through all loops"…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 12 of 13
(436 Views)

@GerdW wrote:

I was hoping that wasn't the case because wiring the queue everywhere is a real pain through all of the relevant loops etc.

Use named queues: no need to wire "through all loops"…


Another option are Action Engines to store the queues and then a libraries to make actual APIs around those AEs.  This is what I do.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
Message 13 of 13
(432 Views)