Click to Rate and Give Feedback
MSDN
MSDN Library
User Interface
User Input
Mouse Input
Notifications
 WM_MOUSEMOVE Notification
WM_MOUSEMOVE Notification

The WM_MOUSEMOVE message is posted to a window when the cursor moves. If the mouse is not captured, the message is posted to the window that contains the cursor. Otherwise, the message is posted to the window that has captured the mouse.

A window receives this message through its WindowProc function.

Syntax

WM_MOUSEMOVE

    WPARAM wParam
    LPARAM lParam;
    

Parameters

wParam
Indicates whether various virtual keys are down. This parameter can be one or more of the following values.
MK_CONTROL
The CTRL key is down.
MK_LBUTTON
The left mouse button is down.
MK_MBUTTON
The middle mouse button is down.
MK_RBUTTON
The right mouse button is down.
MK_SHIFT
The SHIFT key is down.
MK_XBUTTON1
Windows 2000/XP: The first X button is down.
MK_XBUTTON2
Windows 2000/XP: The second X button is down.
lParam
The low-order word specifies the x-coordinate of the cursor. The coordinate is relative to the upper-left corner of the client area.

The high-order word specifies the y-coordinate of the cursor. The coordinate is relative to the upper-left corner of the client area.

Return Value

If an application processes this message, it should return zero.

Remarks

Use the following code to obtain the horizontal and vertical position:

xPos = GET_X_LPARAM(lParam); 
yPos = GET_Y_LPARAM(lParam); 

You can also use the MAKEPOINTS macro to convert the lParam parameter to a POINTS structure.

Notification Requirements

Minimum DLL Version None
HeaderDeclared in Winuser.h, include Windows.h
Minimum operating systems Windows 95, Windows NT 3.1

See Also

Tags What's this?: Add a tag
Community Content   What is Community Content?
Add new content RSS  Annotations
Value      Đonny   |   Edit   |   Show History
 WM_MOUSEMOVE = &H200
MK_CONTROL = &H8
MK_LBUTTON = &H1
MK_MBUTTON = &H10
MK_RBUTTON = &H2
MK_SHIFT = &H4
MK_XBUTTON1 = &H20
MK_XBUTTON2 = &H40
See Also...      ctacke   |   Edit   |   Show History
WM_LBUTTONDOWN at http://msdn.microsoft.com/en-us/library/ms645607(VS.85).aspx

WM_LBUTTONUP at http://msdn.microsoft.com/en-us/library/ms645608(VS.85).aspx


Correction      Cerasti   |   Edit   |   Show History
This code is no longer valid:
xPos = GET_X_LPARAM(lParam); 
yPos = GET_Y_LPARAM(lParam);

Use this instead:

xPos = LOWORD(lParam); 
yPos = HIWORD(lParam);


Tags What's this?: Add a tag
Flag as ContentBug
No, don't use LOWORD/HIWORD      stickboy   |   Edit   |   Show History

As noted in the GetMessagePos documentation, using LOWORD/HIWORD is wrong since it will not sign-extend negative coordinates for multiple monitor systems. (All of the documentation for mouse messages (WM_MOUSEMOVE, WM_LBUTTONDOWN, etc.) should stress this, just like the GetMessagePos documentation.)

Edit: Actually, I guess since most mouse messages are in client coordinates (whereas GetMessagePos uses screen coordinates), it's not a big deal.

Tags What's this?: Add a tag
Flag as ContentBug
Processing
© 2009 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks | Privacy Statement
Page view tracker