Re: timeSetEvent() wraps after inteval of 429496
- From: "Chris P. [MVP]" <msdn@xxxxxxxxxxxx>
- Date: Sat, 4 Jun 2005 10:59:55 -0400
On Fri, 3 Jun 2005 22:06:05 -0700, Alexander Grigoriev wrote:
> Looks like the internal math to convert miliseconds to 100 ns units is using
> 32 bits. This means anything more that2^32 / 10000 ms gets truncated.
Yep, that's definitely what it's doing. What's strange though is that the
one shot timer using the same function works correctly, so it must use a
different timing mechanism.
.
- Follow-Ups:
- Re: timeSetEvent() wraps after inteval of 429496
- From: Alexander Grigoriev
- Re: timeSetEvent() wraps after inteval of 429496
- References:
- BUG: timeSetEvent() wraps after inteval of 429496
- From: Chris P.
- Re: timeSetEvent() wraps after inteval of 429496
- From: Alexander Grigoriev
- BUG: timeSetEvent() wraps after inteval of 429496
- Prev by Date: Re: timeSetEvent() wraps after inteval of 429496
- Next by Date: Re: timeSetEvent() wraps after inteval of 429496
- Previous by thread: Re: timeSetEvent() wraps after inteval of 429496
- Next by thread: Re: timeSetEvent() wraps after inteval of 429496
- Index(es):