Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The comment is wrong. My experience has been that the multimedia timer does not affect the .NET timers. That is, it doesn't change their minimum supported time period, which appears to be about 15 ms. It <em>might</em> improve their accuracy. That is, if you ask for 16 ms, you might actually get 16 ms and not "somewhere between 15 and 30 ms."</p> <p>Why the .NET timers are limited to 15 ms is not clear to me.</p> <p>There's some information about it in the accepted answer <a href="https://stackoverflow.com/q/3744032/56778">here</a>.</p> <p>If you're looking for a higher resolution timer for .NET, you probably shouldn't use the multimedia timers. Those have been deprecated in the Windows API. Use the Timer Queue Timers. See my articles:</p> <ul> <li><a href="http://www.informit.com/guides/content.aspx?g=dotnet&amp;seqNum=815" rel="nofollow noreferrer">.NET Timer Resolution</a></li> <li><a href="http://www.informit.com/guides/content.aspx?g=dotnet&amp;seqNum=816" rel="nofollow noreferrer">Exploring options for better timers</a></li> <li><a href="http://www.informit.com/guides/content.aspx?g=dotnet&amp;seqNum=817" rel="nofollow noreferrer">Using the Windows Timer Queue API</a></li> </ul> <p>Another option is to use the <a href="http://www.devsource.com/c/a/Languages/Waitable-Timers-in-NET-CSharp/" rel="nofollow noreferrer">Waitable Timer</a>. Full source for that is available at <a href="http://www.mischel.com/pubs/waitabletimer.zip" rel="nofollow noreferrer">http://www.mischel.com/pubs/waitabletimer.zip</a></p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload