Beginner
Appropriate QFuture use?
I have a camera grabbing frames at it's own fixed rate.
The camera API uses a C lib and a 'C' callback function when each new frame arrives.
it's a bit tricky to use the 'C' callback with Qt and signals so I thought of putting the camera into it's own thread, blocking on each new image and signalling the Qt app when there is a new frame to display.
Is QFuture appropriate for this?
It's not typical because it has no end, but it does have a continuously updating current 'result'.
The "Q"
Re: Appropriate QFuture use?
No, it's not.Originally Posted by mgb_qt
Your biological and technological distinctiveness will be added to our own. Resistance is futile.
Please ask Qt related questions on the forum and not using private messages or visitor messages.
Beginner
Re: Appropriate QFuture use?
So QFuture/QConcurrent is only for 'map-reduce' type = throw a problem at N processes, wait for the answers?
Back to the traditional threading/mutex/semaphore/debugging then .... ;-(
The "Q"
Re: Appropriate QFuture use?
No, it's not
Your biological and technological distinctiveness will be added to our own. Resistance is futile.
Please ask Qt related questions on the forum and not using private messages or visitor messages.
Posting Permissions
Reply With Quote
Bookmarks