WM SEM4: Difference between revisions
Created page with "This message is sent or posted by an application. ==Syntax== <PRE> param1 ULONG flAccumBits; →Semaphore value.: param2 ULONG ulReserved1; →Reserved value, should be 0.: </PRE> ==Parameters== ;flAccumBits (ULONG) - Input : Semaphore value. The semaphore values from all the WM_SEM4 messages posted to a queue, are accumulated by a logical-OR operation. ;ulReserved1 (ULONG) - Input : Reserved value, should be 0. ==Returns== ;ulReserved2 (UL..." |
(No difference)
|
Latest revision as of 22:47, 13 April 2025
This message is sent or posted by an application.
Syntax
param1
ULONG flAccumBits; /* Semaphore value. */
param2
ULONG ulReserved1; /* Reserved value, should be 0. */
Parameters
- flAccumBits (ULONG) - Input
- Semaphore value. The semaphore values from all the WM_SEM4 messages posted to a queue, are accumulated by a logical-OR operation.
- ulReserved1 (ULONG) - Input
- Reserved value, should be 0.
Returns
- ulReserved2 (ULONG) - returns
- Reserved value, should be 0.
Remarks
If the message is posted, it is merged with any existing WM_SEM4 message on the queue by combining the two flAccumBits values using a logical-OR operation.
The WM_SEM4 messages are queued lower than any other type of message.
Default Processing
The default window procedure takes no action on this message, other than to set ulReserved1 to 0.