Jump to content

WM MOUSEMAP

From EDM2
Revision as of 04:35, 18 April 2025 by Martini (talk | contribs) (Created page with "This message is specific to version 2.1, or higher, of the OS/2 operating system. This message is used only by applications that wish to remap mouse messages in the PM input queue. It is not recommended for general application usage, and applications should NOT process this message in their window procedures. ==Syntax== <pre> param1 ULONG ulPhysButton; The physical button number (1, 2, or 3).: param2 ULONG ulMappedButton; /* The button to be mapped to (...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

This message is specific to version 2.1, or higher, of the OS/2 operating system.

This message is used only by applications that wish to remap mouse messages in the PM input queue. It is not recommended for general application usage, and applications should NOT process this message in their window procedures.

Syntax

param1
    ULONG ulPhysButton;   /* The physical button number (1, 2, or 3). */

param2
    ULONG ulMappedButton; /* The button to be mapped to (1, 2, or 3). */

Parameters

ulPhysButton (ULONG) - input
The physical button number (1, 2, or 3).
ulMappedButton (ULONG) - input
The button to be mapped to (1, 2, or 3).
ulReserved (ULONG) - input
Reserved value, should be 0.

Returns

ulReserved (ULONG) - returns
Reserved value, should be 0.

Remarks

PM will interpret this message when it is read from the PM input queue, as a request to remap all subsequent mouse events for the desired button, until another WM_MOUSEMAP message is received, cancelling that remap request. This message has no meaning to an application.

Default Processing

The default window procedure takes no action on this message, other than to set ulReserved to 0.