This topic has not yet been rated - Rate this topic

InSendMessageEx function

Applies to: desktop apps only

Determines whether the current window procedure is processing a message that was sent from another thread (in the same process or a different process).

Syntax

DWORD WINAPI InSendMessageEx(
  __reserved  LPVOID lpReserved
);

Parameters

lpReserved

Type: LPVOID

Reserved; must be NULL.

Return value

Type:

Type: DWORD

If the message was not sent, the return value is ISMEX_NOSEND (0x00000000). Otherwise, the return value is one or more of the following values.

Return code/valueDescription
ISMEX_CALLBACK
0x00000004

The message was sent using the SendMessageCallback function. The thread that sent the message is not blocked.

ISMEX_NOTIFY
0x00000002

The message was sent using the SendNotifyMessage function. The thread that sent the message is not blocked.

ISMEX_REPLIED
0x00000008

The window procedure has processed the message. The thread that sent the message is no longer blocked.

ISMEX_SEND
0x00000001

The message was sent using the SendMessage or SendMessageTimeout function. If ISMEX_REPLIED is not set, the thread that sent the message is blocked.

 

Remarks

To determine if the sender is blocked, use the following test:

fBlocked = ( InSendMessageEx(NULL) & (ISMEX_REPLIED|ISMEX_SEND) ) == ISMEX_SEND;

Requirements

Minimum supported client

Windows 2000 Professional

Minimum supported server

Windows 2000 Server

Header

Winuser.h (include Windows.h)

Library

User32.lib

DLL

User32.dll

See also

Reference
SendMessage
SendMessageCallback
SendMessageTimeout
SendNotifyMessage
Conceptual
Messages and Message Queues

 

 

Send comments about this topic to Microsoft

Build date: 2/3/2012

Did you find this helpful?
(1500 characters remaining)
Community Content Add
Annotations FAQ