Hi Angus,

> You can implement a blocking 2ms delay using QueryPerformanceCounter
> which returns a 64-bit counter, and QueryPerformanceFrequency which gives
> you ticks per second for the counter.
I know, but since there are a lot of very short instructions to send, this 
increases the cpu load a lot.
> There may be multi-media APIs with better accuracy.
I'll check this.
> But another process may preempt your thread so the delay could be longer.
> There may be multi-media APIs with better accuracy.
That's std Windows behaviour unless you claim the cpu for your process for a 
short period.
But this is not the problem, I just want a more reliable short delay and if 
possible without increasing the cpu load.



To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Reply via email to