Programming a timer??

timeGetTime

GetTickCount

My Website | Everything you need to know about 3D Graphics | Google | Search the Forums

For the sake of completing it.

QueryPerformanceFrequency()
QueryPerformanceCount()

That is a real big help. . . Those functions are in the Win32 libraries aren''t they?

Which timer would you guys recomend the most? (save for one made by me in asm cuz i dont know any asm)

(add "Winmm.lib" to linker)

include "Mmsystem.h"

DWORD dwOldTickcount = timeGetTime();

DWORD dwNewTickcount = timeGetTime();

DWORD dwDifTickcount = (dwNewTickcount - dwOldTickcount) ;

DWORD dwDifsec = (dwDifTickcount / 100);



Hope this is helpful.
-Crow

If the Win32 timer is the best way to go I can use that. But I don't know how to "use" it in programming. (C++) Example?

Whops--Thanks

[edited by - DarkWhoppy on January 19, 2004 8:15:31 PM]

well whats your goal? the way that ive attacked timing in general has been simply by making a timer class...which is well...a timer... hard to explain without a real goal...

also: how accurate/how much overhead is involved with timeGetTime ?

[edited by - Ademan555 on January 19, 2004 8:46:39 PM]

It''ll be used for a demo. Displaying certian images by how much time has passed. like

if(Time >= 1:00) //Which would probably be in millisecs 60,000
{
Do-Stuff-Here;
}

Ya get me? But if someone could provide an example of using the Win32 timer functions I''d appreciate it.

[center][img]http://home.no.net/archaic/DarkWsign.jpg[/img][/center]

ok just use timeGetTime to get the current time, then have a variable that is the last time you did timeGetTime and then subract the past one form the current and voila you have the amount of time passed, from there you have what yo uneed ( hope)

Ademan555: timeGetTime took about 100 clocks on my old Win2k, Athlon XP system. GetSystemTimeAsFileTime and GetTickCount, which just read memory mapped into your process, take only 6 and 8 clocks. QueryPerformanceCounter goes to the hardware, so its overhead is 0.7 .. 3 µs (depending on implementation).
timeGetTime resolution defaults to 10 ms or 15 ms on SMP HAL systems, and can be set down to 1 ms with timeBeginPeriod.
But that''s all information that can be quickly measured or read about in the dox