Gentlemen/ladies,
I cannot "hold my right hand on the Bible" about it, but I might have found a bug in the IMAQ software.
It seems dangerous to do 'imgSessionStopAcquisition' while the callback function supplied in 'imgSessionWaitSignalAsync2' is executing.
This can happen if, as in my application, 'imgSessionStartAcquisition', 'imgSessionWaitSignalAsync2', 'imgSessionStopAcquisition' are done by control from threads that are running with THREAD_PRIORITY_HIGHEST or THREAD_PRIORITY_TIME_CRITICAL.
At least I got rid of the program-hang problems with a flag-handshake scheme so that, at stop, the callback returns 0 so that it will not be called subsequently, and that 'imgSessionStopAcquisition' is surely not done while the callback is executing.
Best regards
Staffan Cronstrom
