The MONLINKSTRUCT structure contains information about a DDE advise loop. A DDE monitoring application can use this structure to obtain information about an advise loop that has started or ended.
typedef struct tagMONLINKSTRUCT { // mlst
UINT cb;
DWORD dwTime;
HANDLE hTask;
BOOL fEstablished;
BOOL fNoData;
HSZ hszSvc;
HSZ hszTopic;
HSZ hszItem;
UINT wFmt;
BOOL fServer;
HCONV hConvServer;
HCONV hConvClient;
} MONLINKSTRUCT;
Members
cb
Specifies the structure's size, in bytes.
dwTime
Specifies the Windows time when the advise loop was started or ended. Windows time is the number of milliseconds that have elapsed since the system was booted.
hTask
Identifies a task (application instance) that is a partner in the advise loop.
fEstablished
Indicates whether an advise loop was successfully established. A value of TRUE indicates an advise loop was established; FALSE indicates it was not.
fNoData
Indicates whether the XTYPF_NODATA flag is set for the advise loop. A value of TRUE indicates the flag is set; FALSE indicates it is not.
hszSvc
Identifies the service name of the server in the advise loop.
hszTopic
Identifies the topic name on which the advise loop is established.
hszItem
Identifies the item name that is the subject of the advise loop.
wFmt
Specifies the format of the data exchanged (if any) during the advise loop.
fServer
Indicates whether the link notification came from the server. A value of TRUE indicates the notification came from the server; FALSE indicates otherwise.
hConvServer
Identifies the server conversation.
hConvClient
Identifies the client conversation.
Remarks
Because string handles are local to the process, the hszSvc, hszTopic, and hszItem members are global atoms.
The hConvClient and hConvServer members of the MONLINKSTRUCT structure do not hold the same value as would be seen by the applications engaged in the conversation. Instead, they hold a globally unique pair of values that identify the conversation.
See Also