LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Thread Callback is never called - CVI bug?

This part of code should be enough to grasp what I was writing about. Commenting CmtWaitForThreadPoolFunctionCompletion will eventually make callbacks fail.

0 Kudos
Message 11 of 13
(2,043 Views)

I am looking at your code, it's rather complex to understand due to the extended use of references to structured variables you are making, but at some point I realized that your main function is NOT calling RunUserInterface () at any time Smiley Surprised

That is: the initial assumption we made that the main thread is processing events is NOT TRUE at all! This explains why TSQ is not reading data and adding CmtWaitForThreadPoolFunctionCompletion with event processing option was "solving" your problems.

 

 



Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
0 Kudos
Message 12 of 13
(2,003 Views)

Hello Chris, is there any update on this subject?



Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
0 Kudos
Message 13 of 13
(1,934 Views)