QObject::killTimers() warning after timer stopped from its own thread

[wysota]

So let me understand. You run this app. Before the count gets to 100, hit the brakes with the Cancel button. You're telling me no message like "QObject::killTimer: timers cannot be stopped from another thread"?

Nope. The last thing I get is a number. Maybe I should wait an hour for the message to appear

That library has functions that are called for each timer tick and have to perform tasks in the background that would otherwise tie up the UI.

It doesn't yet mean you need to do any threading.

I created this to perform a task (a loop counter in this case) and update a progress bar. I find it incredible that this test app loaded on a host PC and on a virtual machine and on my own laptop all perform exactly the same - that is, the killTimer warning is displayed in the debug window after the Cancel button is clicked and before the counter gets to 100, except for you.

Do you want me to shoot a video? Maybe the thing is that you're using Windows and I'm not (however I doubt it).

I feel that background tasks belong in another thread so as to keep the UI responsive.

You can always delegate the task to an external process and talk to it using QProcess or QLocalSocket. However I still think threading is not required here, especially if it's a source of some problems. Nevertheless I think the code you have is easy to fix to work within a thread. Maybe you just need to restructure the code.