How to cleanup timers properly?

[high_flyer]

jpn:
My comment about the design in the code you posted is not directly connected to the problem you raised with the cross thread communication.
And since its a design issue, it really has nothing to do with the size of the code, but on it functionality.
Its a bad practice to mix view and functionality.
It is good practise to use encapsulation when programming C++ (OOP).
I offered it as a constructive comment, its ok if you don't agree with it.
And, it *could* be that with a correct design your inter thread communication problem would be solved or easer to handle.

While I don't mind if you agree with my above comment I do mind the following since its missleading others:

You cannot emit signals or post events ACROSS THREAD to a QThread descendant object.

This is not true.
From the docs:

It is important to keep in mind that the event loop may be delivering events to your QObject subclass while you are accessing the object from another thread.

And :

When using signals and slots, the slot will be executed in the main thread and when posting event's, the event gets posted in the main event loop.

No - when you send signal across threads its execution depends on what kind of a connection you made:
If its a direct connetion the slot will be executed in the thread in which the signal was emmited, that does not have to be the main thread.
If the connection you made is a qued connection then the slot will be executed in the thread in which the object that has the slot lives in, again, does not have to be the main thread.

I would advise you to read the chapter about threading in the Qt4 docs.

[jpn]

No - when you send signal across threads its execution depends on what kind of a connection you made:
If its a direct connetion the slot will be executed in the thread in which the signal was emmited, that does not have to be the main thread.

The issue is not about the connection type. I have used a queued connection. The "problem" is object's owner thread. As if you know, queued signals are delivered as events underhood. If the QThread object lives in the main thread as well, the stuff gets queued but later sent directly, not posted across thread. One could easily believe that queued signals and/or posted custom events would get delivered to the qthread object's own event loop. But that is not the case and I'm glad to know it now.

If the connection you made is a qued connection then the slot will be executed in the thread in which the object that has the slot lives in, again, does not have to be the main thread.

You are missing the point. I was talking about two objects both living in main thread. Regardless of fact that one of the objects is a QThread object and the connection is queued, the slot will be executed in the main thread since that's where the QThread object lives in.

Go ahead and test it by yourself:
http://qtnode.net/pastebin/800

[jpn]

jpn:
My comment about the design in the code you posted is not directly connected to the problem you raised with the cross thread communication.
And since its a design issue, it really has nothing to do with the size of the code, but on it functionality.
Its a bad practice to mix view and functionality.
It is good practise to use encapsulation when programming C++ (OOP).
I offered it as a constructive comment, its ok if you don't agree with it.
And, it *could* be that with a correct design your inter thread communication problem would be solved or easer to handle.

I simply couldn't resist to comment this furthermore. You are just judging pretty hard without knowing anything about the subject..

What if everything shown in the GUI is highly dependant on a network flow receiving tons of data items all the time. The network flow must be adjusted once in a while so that only required data items are ordered, otherwise the connection would get obstructed. Mostly anything done by the user causes also a change in the network flow. It's not that I'm having any freaking widget with a direct pointer to some thread object. There is a separate module handling all the network stuff. As I said, the example was just to illustrate the inter-thread communication problem I had.