Thanks for the responses. My current implementation, is not bold(read
stupid) enough to go out in the high waters and test a 100k timers. What I
do essentially is to keep a single timer, have it's timeout at hcf of
required and .. you get the idea.
To have the individual objects manage it sounds ea
Prashant spaketh:
> , However, QTimer documentation states that
> "If Qt is unable to deliver the requested number of timer clicks, it will
> silently discard some."
> I don't know how to interpret this statement. Does it mean that if a timer
> has a very low resolution, some clicks are neglected.
6, 2012 6:45 AM
To: interest@qt-project.org
Subject: Re: [Interest] Scalability of QTimer or QObject::startTimer
Den 26-10-2012 11:18, Prashant skrev:
Hi.
I intend to have quite a few QObject inherited classes each implementing a
couple of timers. The resolution of these timers is expected t
Den 26-10-2012 11:18, Prashant skrev:
Hi.
I intend to have quite a few QObject inherited classes each
implementing a couple of timers. The resolution of these timers is
expected to be around 1000ms. However, QTimer documentation states that
"If Qt is unable to deliver the requested number of t
Hi.
I intend to have quite a few QObject inherited classes each implementing a
couple of timers. The resolution of these timers is expected to be around
1000ms. However, QTimer documentation states that
"If Qt is unable to deliver the requested number of timer clicks, it will
silently discard some.
