Remove event handlers wxApp::OnQueryEndSession and wxDialog::OnCharHook from docs...

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

diff --git a/docs/latex/wx/ddeclint.tex b/docs/latex/wx/ddeclint.tex
index 6df0f6e3b561ac517da229a69c3770dbce1836d2..bfb9f6eca24a343e7d8113e9b77721c77412cd4d 100644 (file)
--- a/docs/latex/wx/ddeclint.tex
+++ b/docs/latex/wx/ddeclint.tex
@@ -30,7 +30,7 @@ wxClientBase\\
 
 \latexignore{\rtfignore{\wxheading{Members}}}
 
 
 \latexignore{\rtfignore{\wxheading{Members}}}
 

-\membersection{wxDDEClient::wxDDEClient}
+\membersection{wxDDEClient::wxDDEClient}\label{wxddeclientctor}

 
 \func{}{wxDDEClient}{\void}
 
 
 \func{}{wxDDEClient}{\void}
 


@@ -59,10 +59,10 @@ object is returned.
 
 The advantage of deriving your own connection class is that it will
 enable you to intercept messages initiated by the server, such
 
 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.
 
 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}}
 
 
 \func{bool}{ValidHost}{\param{const wxString\& }{host}}