Vladimir Nesterovsky wrote:
> If you realy need to measure short time use rathe
> QueryPerformanceCounter
> and QueryPerformanceFrequency instead of GetTickCount.
> --
> Vladimir Nesterovsky
> e-mail: vladimir@nesterovsky-bros.com
> home: [url]http://www.nesterovsky-bros.com[/url] [/B]
Thank You, That is a good solution yes, and I have to test if th
behaviour is ok (when I get to my computer at work). GetTickCoun
resolution is not good, but i just has to measure if a hardware devic
respond or not, and I do not need high resolution, a brute fix for m
problem was to insert Sleep(10) between two tickCount query. What i
realy bother me is god old GetTickCount can trigger such problems (on
of my programs returned with serious bugreport, I search and tested i
any circumstances, the bug does not apear, after that I get a ne
computer to be in the same condition like the client, and the bug wa
there... (somethime negative elapsed time) ... :(...
ERROR - 28 Oct 2004 15:01 GMT
try Enviroment::TickCount also...:)
> Vladimir Nesterovsky wrote:
> > If you realy need to measure short time use rather
[quoted text clipped - 21 lines]
> Posted via http://www.codecomments.com
> ------------------------------------------------------------------------