The SetTimer function creates a timer with the specified time-out value.
UINT SetTimer(
HWND hWnd, |
// handle of window for timer messages |
UINT nIDEvent, |
// timer identifier |
UINT uElapse, |
// time-out value |
TIMERPROC lpTimerFunc |
// address of timer procedure |
); |
If lpTimerFunc is NULL, the system posts a WM_TIMER message to the application queue. The hwnd member of the message’s MSG structure contains the value of the hWnd parameter.
If the function succeeds, the return value is an integer identifying the new timer. An application can pass this value, or the string identifier, if it exists, to the KillTimer function to destroy the timer. If the function fails to create a timer, the return value is zero. To get extended error information, call GetLastError.
An application can process WM_TIMER messages by including a WM_TIMER case statement in the window procedure or by specifying a TimerProc callback function when creating the timer. When you specify a TimerProc callback function, the default window procedure calls the callback function when it processes WM_TIMER. Therefore, you need to dispatch messages in the calling thread, even when you use TimerProc instead of processing WM_TIMER.
The wParam parameter of the WM_TIMER message contains the value of the nIDEvent parameter.
KillTimer, MSG, TimerProc, WM_TIMER
file: /Techref/os/win/api/win32/func/src/f83_5.htm, 3KB, , updated: 2000/4/7 11:19, local time: 2024/11/9 15:38,
3.144.2.29:LOG IN ©2024 PLEASE DON'T RIP! THIS SITE CLOSES OCT 28, 2024 SO LONG AND THANKS FOR ALL THE FISH!
|
©2024 These pages are served without commercial sponsorship. (No popup ads, etc...).Bandwidth abuse increases hosting cost forcing sponsorship or shutdown. This server aggressively defends against automated copying for any reason including offline viewing, duplication, etc... Please respect this requirement and DO NOT RIP THIS SITE. Questions? <A HREF="http://linistepper.com/techref/os/win/api/win32/func/src/f83_5.htm"> SetTimer</A> |
Did you find what you needed? |