[Live-devel] How to implement non-blocking fashion in custom doGetNextFrame()

[Cristiano Belloni]

Ross Finlayson wrote:

> If your 
> capture device is a socket, then you can easily do this using 
> "TaskScheduler::turnOnBackgroundReadHandling()".  If, however, your 
> capture device is not a socket, then you can instead signal the 
> arrival of new data by writing a new event loop (e.g., by subclassing 
> "TaskScheduler"), or perhaps more simply by using the existing 
> "watchVariable" feature (see the FAQ).
>   
My capture device is not a socket, and I'd like to write a new event 
loop. I see that my doGetNextFrame is called anytime a 
DelayQueue::HandleAlarm calls AlarmHandler::HandleTimeout (which in turn 
calls handleTimeout, and so on).

Please note I can only see *if* a frame is ready. When / where in the 
code should I check that, in order to get my doGetNextFrame called?

Regards,
Cristiano
-- 
Belloni Cristiano
Imavis Srl.
www.imavis.com <http://www.imavis.com>
belloni at imavis.com <mailto://belloni@imavis.com>