Thanks the info.
Tr3w
On Tue, Feb 4, 2014 at 4:23 PM, Lopes Yoann wrote:
> I think this is simply bad API design... It should be
> QAbstractVideoSurface::present(QVideoFrame &frame) instead.
> It's absolutely safe to ignore the const-ness of the video frame.
>
> Yoann Lopes
> Senior Software E
I think this is simply bad API design... It should be
QAbstractVideoSurface::present(QVideoFrame &frame) instead.
It's absolutely safe to ignore the const-ness of the video frame.
Yoann Lopes
Senior Software Engineer - Digia, Qt
Visit us on: http://qt.digia.com
_
Hi,
I started a new application which will do image processing on the
frames captured from the camera.
For grabbing the frame data, I followed what the documentation says:
I derived a class from QAbstractVideoSurface and set it with
QCamera::setViewFinder.
So far so good, the camera calls my Vid
