I'm trying to figure out how to use timers in Win32 so that I can time certain events, such as fade-ins. I currently use a for(x,x,x) loop, but even though that works great on our old p1/200mmx, it is un-noticeable on the p3/500. I would like to time it to about 500ms intervals for the next shading. Any help would be greatly appreciated. Thanks for your time!<br>
<br>
-Seph

Hey Seph,<br>
<br>
Try this code<br>
<br>
// wait for 500 ms<br>
DWORD dwTime = GetTickCount();<br>
while( ( GetTickCount() - dwTime ) > 500 );<br>
<br>
If you want a very accurate timer, check out the multimedia timer functions in MSDN, I think I posted something about that in here a while ago, or maybe the C++ board. Cant remember!<br>
<br>
: I'm trying to figure out how to use timers in Win32 so that I can time certain events, such as fade-ins. I currently use a for(x,x,x) loop, but even though that works great on our old p1/200mmx, it is un-noticeable on the p3/500. I would like to time it to about 500ms intervals for the next shading. Any help would be greatly appreciated. Thanks for your time!<br>
: <br>
: -Seph<br>
: <br>
<br>
<br>
<br>

Should be<br>
while( ( GetTickCount() - dwTime ) < 500 );<br>
<br>
: Hey Seph,<br>
: <br>
: Try this code<br>
: <br>
: // wait for 500 ms<br>
: DWORD dwTime = GetTickCount();<br>
: while( ( GetTickCount() - dwTime ) > 500 );<br>
: <br>
: If you want a very accurate timer, check out the multimedia timer functions in MSDN, I think I posted something about that in here a while ago, or maybe the C++ board. Cant remember!<br>
: <br>
: : I'm trying to figure out how to use timers in Win32 so that I can time certain events, such as fade-ins. I currently use a for(x,x,x) loop, but even though that works great on our old p1/200mmx, it is un-noticeable on the p3/500. I would like to time it to about 500ms intervals for the next shading. Any help would be greatly appreciated. Thanks for your time!<br>
: : <br>
: : -Seph<br>
: : <br>
: <br>
: <br>
: <br>
: <br>
: <br>
<br>

That's no good. My Borland help file says that "GetTickCount" just returns the number of milliseconds since Windoze was started. Also says that at 49.7 days it will wrap to 0. Here is the fade from red (after the screen fills with blood) to black code.<br>
<br>
for(int x = 0; x < 256; x++)<br>
{<br>
while((GetTickCount() - dwTime) < 500)<br>
FillRect(fDC, &faderect, (CreateSolidBrush(RGB(255, x, x))));<br>
}<br>
<br>
Any other ideas? Oh and just in case it matters, all of this code is in "fight.dll", not my executeable.<br>
<br>
-Seph

So? why its not good? You can write a function like this:<br>
<br>
void MyDelay( DWORD dwMilliSeconds )<br>
{<br>
DWORD dwInitial = GetTickCount();<br>
while( ( GetTickCount() - dwInitial ) < dwMilliSeconds );<br>
}<br>
<br>
As I understand, you want a delay, thats a difference between two snapshots of time. GetTickCount can do that perfectly well.<br>
<br>
Or am I missing something, again!<br>
<br>
: That's no good. My Borland help file says that "GetTickCount" just returns the number of milliseconds since Windoze was started. Also says that at 49.7 days it will wrap to 0. Here is the fade from red (after the screen fills with blood) to black code.<br>
: <br>
: for(int x = 0; x < 256; x++)<br>
: {<br>
: while((GetTickCount() - dwTime) < 500)<br>
: FillRect(fDC, &faderect, (CreateSolidBrush(RGB(255, x, x))));<br>
: }<br>
: <br>
: Any other ideas? Oh and just in case it matters, all of this code is in "fight.dll", not my executeable.<br>
: <br>
: -Seph<br>
: <br>
<br>

That will work perfectly. I didn't think of storing the current Tick and using it later. I'll try this and see what happens. It's heck just seeing a quick flash of red and black before the battle scene, lol!<br>
<br>
-Seph