A thought: What would be the proper way to implement something that behaves like a QTimer with delay 0 (= fire as soon as the event loop becomes available) but with an interval (= fire as soon as the event loop becomes available after at least X msec of pause)? Add a QThread::msleep() call inside the timer callback? Or does that method use QTimer() internally, leading to some kind of interaction leading to an implementation that still keeps updating faster than would be good when something more useful is actually busy? Either way I suppose that this has little to no benefit in case the actual work task runs independently from the eventloop, right?
R. _______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
