WM ERROR: Difference between revisions
Created page with "This message occurs when an error is detected in a WinGetMsg or a WinPeekMsg function. ==Syntax== <pre> param1 USHORT userrorcode; →Error code.: param2 ULONG ulReserved; →Reserved value, should be 0.: </pre> ==Parameters== ;''userrorcode'' (USHORT) - input: Error code. ;''ulReserved'' (ULONG) - input: Reserved value, should be 0. ==Returns== ;''ulReserved'' (ULONG) - returns: Reserved value, should be 0. ==Remarks== The application can..." |
(No difference)
|
Latest revision as of 16:48, 15 April 2025
This message occurs when an error is detected in a WinGetMsg or a WinPeekMsg function.
Syntax
param1
USHORT userrorcode; /* Error code. */
param2
ULONG ulReserved; /* Reserved value, should be 0. */
Parameters
- userrorcode (USHORT) - input
- Error code.
- ulReserved (ULONG) - input
- Reserved value, should be 0.
Returns
- ulReserved (ULONG) - returns
- Reserved value, should be 0.
Remarks
The application can detect the error situation after the WinGetMsg or the WinPeekMsg function and before the WinDispatchMsg function.
Default Processing
The default window procedure takes no action on this message, other than to set ulReserved to 0.