如果有TApplication的话，应该可以使用 SetTimer(). hWnd用Application的Handle试试。<br><br><br>SetTimer<br>The SetTimer function creates a timer with the specified time-out value. <br><br>UINT SetTimer(<br> HWND hWnd, // handle of window for timer messages<br> UINT nIDEvent, // timer identifier<br> UINT uElapse, // time-out value<br> TIMERPROC lpTimerFunc // address of timer procedure<br>);<br> <br>Parameters<br>hWnd <br>Handle to the window to be associated with the timer. This window must be owned by the calling thread. If this parameter is NULL, no window is associated with the timer and the nIDEvent parameter is ignored. <br>nIDEvent <br>Specifies a nonzero timer identifier. If the hWnd parameter is NULL, this parameter is ignored. <br>uElapse <br>Specifies the time-out value, in milliseconds. <br>lpTimerFunc <br>Pointer to the function to be notified when the time-out value elapses. For more information about the function, see TimerProc. <br>If lpTimerFunc is NULL, the system posts a WM_TIMER message to the application queue. The hwnd member of the message'sMSG structure contains the value of the hWnd parameter. <br><br>Return Values<br>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. <br><br>If the function fails to create a timer, the return value is zero. To get extended error information, call GetLastError.<br><br>Remarks<br>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. <br><br>The wParam parameter of the WM_TIMER message contains the value of the nIDEvent parameter. <br><br>
