[Development] Windows Timer Resolution: The Great Rule Change

Konstantin Tokarev annulen at yandex.ru
Thu Oct 8 11:00:13 CEST 2020



08.10.2020, 11:46, "Philippe" <philwave at gmail.com>:
> On Wed, 7 Oct 2020 17:34:43 -0700
> Thiago Macieira <thiago.macieira at intel.com> wrote:
>
>>  Now, the question is how WaitFor{SingleObject,MultipleObjects} are affected.
>>  Does this mean that asking for a timeout of 2 milliseconds could result in
>>  being 13 seconds too late?
>
> I just did a test, and yes, both WaitForSingleObject and
> WaitForMultipleObjects wait at least 15 milliseconds when the events are not
> signaled :(

Is resolution of QElapsedTimer limited to 15 ms as well? If it's more find grained
you can try busy-waiting until required time elapses.


-- 
Regards,
Konstantin


More information about the Development mailing list