Re: [Interest] QImage, multithreaded app.

Hi, as Thiago already stated there are no limitations using QImages inside multithreaded apps. Why do I know this? Because I'm developing and using an industrial image processing framework with massively multithreaded image processing based on QThread and QImage. So I fear that you have some seri

Re: [Interest] QImage, multithreaded app.

Each object is of type event_analizer. Each such object contains a QImage buffer (non-static). The event_analizer sends signal need_screenshot(event_analizer*) where the receiving object uses the pointer to store the made screenshot. Thuse, no, not on the same QImage object. Each thread is storing

Re: [Interest] QImage, multithreaded app.

On sexta-feira, 27 de setembro de 2013 23:13:44, Alexander Syvak wrote: > This is the code of the function saving screenshots. This code is used in > threads analizing screenshots. > Debugging the app. when one thread has been paused inside QImage save > method and other thread wake up invoking th

Re: [Interest] QImage, multithreaded app.

This is the code of the function saving screenshots. This code is used in threads analizing screenshots. Debugging the app. when one thread has been paused inside QImage save method and other thread wake up invoking the lines below QFile screenshot_iodev(mk_screenshot_path(screenshot_idx++)); re

Re: [Interest] QImage, multithreaded app.

On sexta-feira, 27 de setembro de 2013 16:12:37, Alexander Syvak wrote: > Hello, > > the method save_screenshot() is used to save a QImage object using > bool QImage::save ( const > QString& > *fileName*, const char * *format* = 0, int *quality* =

[Interest] QImage, multithreaded app.

Hello, the method save_screenshot() is used to save a QImage object using bool QImage::save ( const QString& *fileName*, const char * *format* = 0, int *quality* = -1 ) const Howver, it appears that QImage is working with one I/O device and retur