Jump to content

WM BUTTON3CLICK

From EDM2
Revision as of 17:39, 15 April 2025 by Martini (talk | contribs) (Created page with "This message occurs when the operator presses and then releases button 3 of the pointing device within a specified period of time, and without moving the mouse. ==Syntax== <pre> param1 POINTS ptspointerpos; Pointer position.: param2 USHORT fsHitTestres; Hit-test result.: USHORT fsflags; Keyboard control codes.: </pre> ==Parameters== ;''ptspointerpos'' (POINTS) - input: The pointer position is in window coordinates relative to the bo...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

This message occurs when the operator presses and then releases button 3 of the pointing device within a specified period of time, and without moving the mouse.

Syntax

param1
    POINTS ptspointerpos; /* Pointer position. */

param2
    USHORT fsHitTestres; /* Hit-test result. */
    USHORT fsflags;      /* Keyboard control codes. */

Parameters

ptspointerpos (POINTS) - input
The pointer position is in window coordinates relative to the bottom-left corner of the window.
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.
fsflags (USHORT) - input
Keyboard control codes. In addition to the control codes described with the WM_CHAR message, the following keyboard control codes are valid:
KC_NONE: Indicates that no key is pressed.

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.