1

I am using Qt to build a ray tracer with GUI. The ideal effect is to paint a pixel immediately after computing the RGB value of that pixel, as in most professional renderer. But I find out that my tracer could only display the entire rendered image after the loop below:

for(int i=0; i<row; ++i)
    for(int j=0; j<column; ++j) {
        compute pixel value;
        painter.drawPoint(i, j);
    }

I am drawing to the central widget of the mainwindow. I reimplemented QWidget paintEvent function and put the loop above in this function. It seems that paintEvent only display the whole screen after being executed once and in the process it gives me this:

enter image description here

I don't know if this is just how paintEvent works or I am doing something wrong.

Anyway, it cannot display pixel in real time. And this is very unsatisfying for an interactive tracer. I hope you guys can provide some explanations and/or solutions. A million thanks!

eyllanesc
  • 235,170
  • 19
  • 170
  • 241
PhoMan24
  • 13
  • 5
  • provide a [mcve] – eyllanesc Apr 17 '18 at 01:52
  • Use a `QPixmap` as back buffer. Render your result into this pixmap, and render this pixmap in `paintEvent()`. From time to time, you can force an update (e.g. after a certain time has been consumed, or, may be, even after each rendered pixel). To force an update, you may use [`QWidget::repaint()`](http://doc.qt.io/qt-5/qwidget.html#repaint-1). Alternatively, you could call the [`QWidget::update()`](http://doc.qt.io/qt-5/qwidget.html#update-1) and then [`QApplication::processEvents()`](http://doc.qt.io/qt-5/qcoreapplication.html#processEvents) to empty the event queue. – Scheff's Cat Apr 17 '18 at 08:03
  • Please, note that `QApplication::processEvents()` is `static` - hence no instance is needed to call it. – Scheff's Cat Apr 17 '18 at 08:05

1 Answers1

1

The OS is giving you the "not responsive" alert because you are doing all the calculation in the GUI thread.

This means that the event loop is stuck at doing your havy calculations and can't process other events.

On a Windows system, this means it won't react to Windows messages. That's why after a certain time the OS tells you that the application is not responsive.

You should perform your heavy calculations in a separated thread, pass the results to the GUI thread when you want to update the GUI and let the GUI thread perform the rendering.

Apart from that, you should consider painting to a backbuffer, as suggested in the comments (although please note that QPixmap is not thread safe).

QPainter::drawPoint() is very slow and it is an unefficient way to paint the whole central area.

Please have a look at the documentation here for more details on how to keep the GUI responsive.

Sergio Monteleone
  • 2,776
  • 9
  • 21
  • thanks so much, your suggestion really works, though i choose qimage instead, but the idea is the same – PhoMan24 Jun 13 '18 at 02:41