WM CHORD: Difference between revisions
Created page with "This message occurs when the operator presses both button one and button two on the pointing device. ==Syntax== <pre> param2 USHORT fsHitTestres; →Hit-test result.: </pre> ==Parameters== ;''fsHitTestres'' (USHORT) - input: ''fsHitTestres'' provides the hit-test result. It contains the value returned from the hit-test process, which determines the window to be associated with this message. For details of the possible values, see WM_HITTEST. ==Returns==..." |
(No difference)
|
Latest revision as of 17:42, 15 April 2025
This message occurs when the operator presses both button one and button two on the pointing device.
Syntax
param2
USHORT fsHitTestres; /* Hit-test result. */
Parameters
- fsHitTestres (USHORT) - input
- fsHitTestres provides the hit-test result. It contains the value returned from the hit-test process, which determines the window to be associated with this message. For details of the possible values, see WM_HITTEST.
Returns
- rc (BOOL) - returns
- Processed indicator.
- TRUE: Message processed
- FALSE: Message ignored
Remarks
This message is posted to the application queue associated with the window that is to receive the pointer-button information.
Default Processing
The default window procedure sends the message to the owner window if it exists, otherwise it takes no action on this message, other than to set rc to FALSE.