you need to derive a class from wxDDEConnection and another from wxDDEClient.
The custom wxDDEConnection class will intercept communications in
a `conversation' with a server, and the custom wxDDEServer is required
-so that a user-overriden \helpref{wxDDEClient::OnMakeConnection}{wxddeclientonmakeconnection} member can return
+so that a user-overridden \helpref{wxDDEClient::OnMakeConnection}{wxddeclientonmakeconnection} member can return
a wxDDEConnection of the required class, when a connection is made.
This DDE-based implementation is
\latexignore{\rtfignore{\wxheading{Members}}}
-\membersection{wxDDEClient::wxDDEClient}
+\membersection{wxDDEClient::wxDDEClient}\label{wxddeclientctor}
\func{}{wxDDEClient}{\void}
The advantage of deriving your own connection class is that it will
enable you to intercept messages initiated by the server, such
-as \helpref{wxDDEConnection::OnAdvise}{wxddeconnectiononadvise}. You may also want to
+as \helpref{wxDDEConnection::OnAdvise}{wxconnectiononadvise}. You may also want to
store application-specific data in instances of the new class.
-\membersection{wxDDEClient::ValidHost}
+\membersection{wxDDEClient::ValidHost}\label{wxddeclientvalidhost}
\func{bool}{ValidHost}{\param{const wxString\& }{host}}
-Returns TRUE if this is a valid host name, FALSE otherwise. This always
-returns TRUE under MS Windows.
-
+Returns \true if this is a valid host name, \false otherwise. This always
+returns \true under MS Windows.