XTYP_MONITOR
XTYP_MONITOR
The dynamic
data exchange (DDE) callback function of a DDE debugging application receives
the XTYP_MONITOR transaction whenever a DDE event occurs in the system. To
receive this transaction, an application must specify the APPCLASS_MONITOR flag
when it calls the DdeInitialize function.
Parameters
uFmt
Not used.
hconv
Not used.
hsz1
Not used.
hsz2
Not used.
hdata
Identifies a
DDE object that contains information about the DDE event. The application
should use the DdeAccessData
function to obtain a pointer to the object.
dwData1
Not used.
dwData2
Identifies
the DDE event. This parameter may be one of the following values:
|
Value |
Meaning |
|
MF_CALLBACKS |
The system
sent a transaction to a DDE callback function. The DDE object contains a MONCBSTRUCT structure that provides
information about the transaction. |
|
MF_CONV |
A DDE
conversation was established or terminated. The DDE object contains a MONCONVSTRUCT structure that provides
information about the conversation. |
|
MF_ERRORS |
A DDE error
occurred. The DDE object contains a MONERRSTRUCT structure that provides
information about the error. |
|
MF_HSZ_INFO |
A DDE
application created, freed, or incremented the usage count of a string
handle, or a string handle was freed as a result of a call to the DdeUninitialize function. The DDE object
contains a MONHSZSTRUCT
structure that provides information about the string handle. |
|
MF_LINKS |
A DDE
application started or stopped an advise loop. The DDE object contains a MONLINKSTRUCT structure that provides
information about the advise loop. |
|
MF_POSTMSGS |
The system
or an application posted a DDE message. The DDE object contains a MONMSGSTRUCT structure that provides
information about the message. |
|
MF_SENDMSGS |
The system
or an application sent a DDE message. The DDE object contains a MONMSGSTRUCT
structure that provides information about the message. |
Return Value
If the
callback function processes this transaction, it should return 0.
See Also