Multiple timers in single Application

[Santosh Reddy]

Then you have seriouly re-consider your structure / architectrue of using timers.

1. Either simply the logic so that it can fit into the time
or
2. Try moving the heavy logic into a thread. (as other poster suggested)

Some how I feel you can do this with using 6 timers or more, one important rule to follow is all the slots should complete with in time. Try re-structing your timers, and what they do.

[Robbie]

@mahi6a1985

Do you really need 6 QTimers? I see from your code that there are two QTimers linked to the footer() slot.

I would seriously consider moving your processing to different threads.

When a QTimer emits the timeout signal, it gets put in the message queue and the slot is called by the event posting mechanism. Since all your QTimers are in the same thread, their timeout signals all get processed one after another.

If, by chance, all the QTimers timeout at exactly the same time, then, the footer() slot will be called at least 925ms after update_HMIScrLvl4(). That's assuming that each of the slots instantaneously returned and called the subsequent timeout slot.

I would suggest that you put each of your timer slots into its own thread, or group the processing by timeout interval. By this I mean that, because failure_display() and footer() are triggered every 250ms, their code could be executed in the same thread, if you like.