wxMemoryDC constructor now optionally accepts a wxBitmap parameter,

[wxWidgets.git] / docs / latex / wx / ipcclint.tex

diff --git a/docs/latex/wx/ipcclint.tex b/docs/latex/wx/ipcclint.tex
index cf1c9c6826fabd6b4363f242a3c4912d1b1bcb2b..a229357d96d0c250998bb3ff14e4a277316bd06a 100644 (file)
--- a/docs/latex/wx/ipcclint.tex
+++ b/docs/latex/wx/ipcclint.tex
@@ -1,4 +1,4 @@
-\section{\class{wxClient}}\label{wxddeclient}
+\section{\class{wxClient}}\label{wxclient}
 
 A wxClient object represents the client part of a client-server
 DDE-like (Dynamic Data Exchange) conversation. The actual
@@ -11,7 +11,7 @@ you need to derive a class from wxConnection and another from
 wxClient. The custom wxConnection class will intercept
 communications in a `conversation' with a server, and the custom
 wxClient is required so that a user-overridden
-\helpref{wxClient::OnMakeConnection}{wxddeclientonmakeconnection} 
+\helpref{wxClient::OnMakeConnection}{wxclientonmakeconnection} 
 member can return a wxConnection of the required class, when a
 connection is made. Look at the IPC sample and the 
 \helpref{Interprocess communications overview}{ipcoverview} for
@@ -28,18 +28,18 @@ wxClientBase\\
 
 \wxheading{See also}
 
-\helpref{wxServer}{wxddeserver}, 
-\helpref{wxConnection}{wxddeconnection}, \helpref{Interprocess communications overview}{ipcoverview}
+\helpref{wxServer}{wxserver}, 
+\helpref{wxConnection}{wxconnection}, \helpref{Interprocess communications overview}{ipcoverview}
 
 \latexignore{\rtfignore{\wxheading{Members}}}
 
-\membersection{wxClient::wxClient}
+\membersection{wxClient::wxClient}\label{wxclientctor}
 
 \func{}{wxClient}{\void}
 
 Constructs a client object.
 
-\membersection{wxClient::MakeConnection}\label{wxddeclientmakeconnection}
+\membersection{wxClient::MakeConnection}\label{wxclientmakeconnection}
 
 \func{wxConnectionBase *}{MakeConnection}{\param{const wxString\& }{host}, \param{const wxString\& }{service}, \param{const wxString\& }{topic}}
 
@@ -49,7 +49,7 @@ native DDE in Windows), service name and topic string. If the
 server allows a connection, a wxConnection object will be
 returned. The type of wxConnection returned can be altered by
 overriding the 
-\helpref{wxClient::OnMakeConnection}{wxddeclientonmakeconnection} 
+\helpref{wxClient::OnMakeConnection}{wxclientonmakeconnection} 
 member to return your own derived connection object.
 
 Under Unix, the service name may be either an integer port
@@ -62,22 +62,22 @@ socket is created.
 insecure for IPC as there is absolutely no access control for
 them, use Unix domain sockets whenever possible!
 
-\membersection{wxClient::OnMakeConnection}\label{wxddeclientonmakeconnection}
+\membersection{wxClient::OnMakeConnection}\label{wxclientonmakeconnection}
 
 \func{wxConnectionBase *}{OnMakeConnection}{\void}
 
-Called by \helpref{wxClient::MakeConnection}{wxddeclientmakeconnection}, by
+Called by \helpref{wxClient::MakeConnection}{wxclientmakeconnection}, by
 default this simply returns a new wxConnection object. Override
 this method to return a wxConnection descendant customised for the
 application.
 
 The advantage of deriving your own connection class is that it
 will enable you to intercept messages initiated by the server,
-such as \helpref{wxConnection::OnAdvise}{wxddeconnectiononadvise}. You
+such as \helpref{wxConnection::OnAdvise}{wxconnectiononadvise}. You
 may also want to store application-specific data in instances of
 the new class.
 
-\membersection{wxClient::ValidHost}
+\membersection{wxClient::ValidHost}\label{wxclientvalidhost}
 
 \func{bool}{ValidHost}{\param{const wxString\& }{host}}