[Interest] CPU load in busy indicator widget based on Q(Variant)Animation

René J.V. Bertin rjvbertin at gmail.com
Wed Oct 16 15:33:55 CEST 2019

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?


More information about the Interest mailing list