Export (0) Print
Expand All
2 out of 2 rated this helpful - Rate this topic

WM_NCXBUTTONDBLCLK message

Posted when the user double-clicks the first or second X button while the cursor is in the nonclient area of a window. This message is posted to the window that contains the cursor. If a window has captured the mouse, this message is not posted.

A window receives this message through its WindowProc function.


#define WM_NCXBUTTONDBLCLK              0x00AD

Parameters

wParam

The low-order word specifies the hit-test value returned by the DefWindowProc function from processing the WM_NCHITTEST message. For a list of hit-test values, see WM_NCHITTEST.

The high-order word indicates which button was double-clicked. It can be one of the following values.

ValueMeaning
XBUTTON1
0x0001

The first X button was double-clicked..

XBUTTON2
0x0002

The second X button was double-clicked.

 

lParam

A pointer to a POINTS structure that contains the x- and y-coordinates of the cursor. The coordinates are relative to the upper-left corner of the screen.

Return value

If an application processes this message, it should return TRUE. For more information about processing the return value, see the Remarks section.

Remarks

Use the following code to get the information in the wParam parameter.


nHittest = GET_NCHITTEST_WPARAM(wParam); 
fwButton = GET_XBUTTON_WPARAM(wParam); 

You can also use the following code to get the x- and y-coordinates from lParam:


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

Important  Do not use the LOWORD or HIWORD macros to extract the x- and y- coordinates of the cursor position because these macros return incorrect results on systems with multiple monitors. Systems with multiple monitors can have negative x- and y- coordinates, and LOWORD and HIWORD treat the coordinates as unsigned quantities.

By default, the DefWindowProc function tests the specified point to get the position of the cursor and performs the appropriate action. If appropriate, it sends the WM_SYSCOMMAND message to the window.

A window need not have the CS_DBLCLKS style to receive WM_NCXBUTTONDBLCLK messages. The system generates a WM_NCXBUTTONDBLCLK message when the user presses, releases, and again presses an X button within the system's double-click time limit. Double-clicking one of these buttons actually generates four messages: WM_NCXBUTTONDOWN, WM_NCXBUTTONUP, WM_NCXBUTTONDBLCLK, and WM_NCXBUTTONUP again.

Unlike the WM_NCLBUTTONDBLCLK, WM_NCMBUTTONDBLCLK, and WM_NCRBUTTONDBLCLK messages, an application should return TRUE from this message if it processes it. Doing so will allow software that simulates this message on Windows systems earlier than Windows 2000 to determine whether the window procedure processed the message or called DefWindowProc to process it.

Requirements

Minimum supported client

Windows 2000 Professional [desktop apps only]

Minimum supported server

Windows 2000 Server [desktop apps only]

Header

Winuser.h (include Windowsx.h)

See also

Reference
DefWindowProc
GET_X_LPARAM
GET_Y_LPARAM
WM_NCHITTEST
WM_NCXBUTTONDOWN
WM_NCXBUTTONUP
WM_SYSCOMMAND
Conceptual
Mouse Input
Other Resources
MAKEPOINTS
POINTS

 

 

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.