The lifetime of a pointer begins when it is first detected.Ī WM_POINTERENTER message is generated if a hovering pointer is detected. For this reason, it is important that you not make any assumptions based on evenly paired WM_POINTERDOWN/ WM_POINTERUP or WM_POINTERENTER/ WM_POINTERLEAVE notifications.Įach pointer has a unique pointer identifier during its lifetime. When a window loses capture of a pointer and it receives the WM_POINTERCAPTURECHANGED notification, it typically will not receive any further notifications. If the application does not process this message, it should call DefWindowProc. If an application processes this message, it should return zero. GET_Y_LPARAM(lParam): the y (vertical point) coordinate.GET_X_LPARAM(lParam): the x (horizontal point) coordinate.Use the following macros to retrieve the physical screen coordinates of the point. Whenever possible, an application should use the complete pointer area information instead of the point location. Applications that wish to respond to fifth actions must retrieve information specific to the pointer type to determine if the second extended mouse (XButton2) button is pressed.īecause the pointer may make contact with the device over a non-trivial area, this point location may be a simplification of a more complex pointer area. IS_POINTER_FIFTHBUTTON_WPARAM(wParam): a flag that indicates whether the specified pointer took fifth action. Applications that wish to respond to fourth actions must retrieve information specific to the pointer type to determine if the first extended mouse (XButton1) button is pressed. IS_POINTER_FOURTHBUTTON_WPARAM(wParam): a flag that indicates whether the specified pointer took fourth action. For example, an application can determine the buttons states of a pen by calling GetPointerPenInfo and examining the flags that specify button states. IS_POINTER_THIRDBUTTON_WPARAM(wParam): a flag that indicates whether there are one or more tertiary actions based on the pointer type applications that wish to respond to tertiary actions must retrieve information specific to the pointer type to determine which tertiary buttons are pressed. A pen pointer will have this set when it is in contact with the digitizer surface with the pen barrel button pressed.This is analogous to a mouse right button down.IS_POINTER_SECONDBUTTON_WPARAM(wParam): a flag that indicates whether there is a secondary action. A pen pointer will have this set when it is in contact with the digitizer surface with no buttons pressed.A touch pointer will have this set when it is in contact with the digitizer surface.This is analogous to a mouse left button down.IS_POINTER_FIRSTBUTTON_WPARAM(wParam): a flag that indicates whether there is a primary action. IS_POINTER_PRIMARY_WPARAM(wParam): indicates that this pointer has been designated as primary. ![]() This flag is not set on messages that indicate a hovering pointer. IS_POINTER_INCONTACT_WPARAM(wParam): a flag that indicates whether this message was generated by a pointer that is in contact with the window surface. This flag is not set on messages that indicate that the pointer has left detection range IS_POINTER_INRANGE_WPARAM(wParam): a flag that indicates whether this message was generated by a pointer during its lifetime. IS_POINTER_NEW_WPARAM(wParam): a flag that indicates whether this message represents the first input generated by a new pointer. GET_POINTERID_WPARAM(wParam): the pointer identifier. ![]() Use the following macros to retrieve information from the wParam parameter. ![]() #define WM_POINTERDOWN 0x0246Ĭontains information about the pointer. For more information, see Writing High-DPI Win32 Applications. DPI virtualization provides automatic scaling support to applications that are not DPI aware and is active by default (users can turn it off). ![]() If your app is not DPI aware, screen coordinates contained in pointer messages and related structures might appear inaccurate due to DPI virtualization. This input message targets the window over which the pointer makes contact, and the pointer is implicitly captured to the window so that the window continues to receive input for the pointer until it breaks contact.Ī window receives this message through its WindowProc function.ĭesktop apps should be DPI aware. Posted when a pointer makes contact over the client area of a window.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |