Qwt and thread question

Hi,

I understand QwtPlotcurve needs to run in the main thread. My plan is to use Qwt for writing out images and have no need of showing images on screen. The image below gives a schematic of my problem.

My main program has a 'qwt function' to generate images. The file names of these images come from a secondary thread and are sent to the main program via signal/slot mechanism. Once the secondary thread finishes, the list of these filenames are send to a 'write Report' function which uses the filenames and the generated images to write out the report.

The problem i am facing is that the 'qwt image generating' function is much slower compared to secondary thread. Thus by the time the control reaches to 'write Report' function, the images havent all been generated. Is there any way i can make the secondary thread wait until the 'qwt image generating' function in the main thread has processed all the images.

Any ideas?

Add a simple signal from main thread that will report when processing has finished and make the secondary thread emit 'finished' only after receiving that signal.

Or cache the list of file names and trigger generating of the report only after all images have been processed.

Thanks I followed your signal approach, and it seems to have solved the problem. However, I have found that 'QwtPlot' method in the main thread is slow and thus blocks the main thread. Is it possible that the plot building is done in the main thread but the plot saving is done in a secondary thread.

Specifically, I want to want to move the following code from the main thread to a secondary thread.

Code:

---

QwtPlotRenderer renderer;
    renderer.setDiscardFlag(QwtPlotRenderer::DiscardBackground, true);
    renderer.setLayoutFlag(QwtPlotRenderer::KeepFrames, false);
    renderer.renderDocument(plot, pngfile, "png", QSizeF(300, 200), 300);

---

Will Qwt let me do that?

In general you can render to a QImage in a extra thread, but:

QwtPlot doesn't have a clean separation between a scene and the paint device ( = widget ) , so that many attributes are stored somewhere in the widget or even deeper in its members. For rendering to a different paint devices - with different geometries - a couple of attributes of the widget are temporary modified and reset later. So you might ( probably will ) have races when you try to render to one ( or several images ) and the widget in different threads. ( To support the completely new graphic stack ( = scene graph ) of Qt 5.x I will have to introduce something like a QwtPlotScene anyway - but this won't happen in the next weeks. )

But at least what you can do is to save the rendered images in extra threads, when you render the plot to a QImage and store it yourself - instead of using QwtPlotRenderer::renderDocument. Check the API of QwtPlotRenderer and have a look into the implementation of renderDocument how they are used.

Uwe

PS: better render PDF documents instead of PNGs - scalable vector graphics are preferable in many ways.