#Purebasic timer how to#
#Purebasic timer 64 Bit#
#Purebasic timer code#

#Purebasic timer 64 Bit#

If ((pt.x = ptOld.x) & (pt.y = ptOld.I can not test this at the moment since I have no 64 bit version of linux running at this time. If the cursor position has not changed, move the cursor position with the one from 10 seconds earlier. HWND hwnd, // handle to window for timer messages MyTimerProc is an application-defined callback function that

#Purebasic timer how to#

If ((pt.x = ptOld.x) & (pt.y = ptOld.y))Īlthough the following example also shows you how to trap mouse input, it processes the WM_TIMER message through the application-defined callback function MyTimerProc, rather than through the application's message queue. cursor position with the one from 10 seconds If the window is minimized, compare the current UResult = SetTimer(hwnd, // handle to main window Wc.hCursor = LoadCursor(hinstance, MAKEINTRESOURCE(200))

Wc.hIcon = LoadIcon(hinstance, MAKEINTRESOURCE(400)) Perform application initialization here. HINSTANCE hinstance // handle to current instance When the application closes, KillTimer stops the timer. If the current location is the same as the previous location and the application's main window is minimized, the application moves the mouse pointer to the icon. Each time the application receives a WM_TIMER message, it records the mouse pointer location. SetTimer creates a timer that sends a WM_TIMER message every 10 seconds. The following example uses the SetTimer and KillTimer functions to trap mouse input. Many developers refer to this routine as 'building a mousetrap.' One way to accomplish this is to create a special routine that traps mouse input until a specific event occurs. Sometimes it is necessary to prevent more input while you have a mouse pointer on the screen. Using Timer Functions to Trap Mouse Input The following example destroys the timers identified by the constants IDT_TIMER1, IDT_TIMER2, and IDT_TIMER3. TranslateMessage(&msg) // translates virtual-key codesĭispatchMessage(&msg) // dispatches message to windowĪpplications should use the KillTimer function to destroy timers that are no longer necessary. Post WM_TIMER messages to the hwndTimer procedure. NULL, // handle to window to receive the message While (GetMessage(&msg, // message structure HWND hwndTimer // handle to window for timer messages If your application creates a timer without specifying a window handle, your application must monitor the message queue for WM_TIMER messages and dispatch them to the appropriate window.

The calling convention for MyTimerProc must be based on the TimerProc callback function. (TIMERPROC) MyTimerProc) // timer callback

#Purebasic timer code#

case WM_TIMER:Īn application can also create a timer whose WM_TIMER messages are processed not by the main window procedure but by an application-defined callback function, as in the following code sample, which creates a timer and uses the callback function MyTimerProc to process the timer's WM_TIMER messages. To process the WM_TIMER messages generated by these timers, add a WM_TIMER case statement to the window procedure for the hwnd parameter. The first timer is set for every 10 seconds, the second for every five minutes. The following example uses the SetTimer function to create two timers. Using Timer Functions to Trap Mouse Input.This topic contains the following sections. This topic shows how to create and destroy timers, and how to use a timer to trap mouse input at specified intervals.