Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

Diff of /docs/trunk/oodialog/en-US/mouse.xml [r8572] .. [r8573] Maximize Restore

  Switch to side-by-side view

--- a/docs/trunk/oodialog/en-US/mouse.xml
+++ b/docs/trunk/oodialog/en-US/mouse.xml
@@ -1381,12 +1381,11 @@
   <varlistentry><term><emphasis role="bold">Remarks:</emphasis></term>
   <listitem>
   <para>
-    Common <xref linkend="paraGuidelinesWhereToConnect"/> invoke event connection methods and on
-    <link linkend="sctCodingEventHandlers">how</link> to code event handlers are included in the documentation for the
-    <xref linkend="clsEventNotification"/> class. Note that it is not possible to instantiate a
-    mouse object tied to a dialog control window until after the <xref linkend="ovvUnderlying"/> dialog
-    has been created. Therefore, for dialog control windows the <emphasis role="italic">connectEvent</emphasis> method
-    is normally invoked in the <xref linkend="mthInitDialog"/> method.
+    See the sections on <link linkend="sctConnectingEventHandlers">connecting</link> and <link
+    linkend="sctCodingEventHandlers">coding</link> event handlers for additional information on event handlers. Note that it
+    is not possible to instantiate a mouse object tied to a dialog control window until after the <xref
+    linkend="ovvUnderlying"/> dialog has been created. Therefore, for dialog control windows the <emphasis
+    role="italic">connectEvent</emphasis> method is normally invoked in the <xref linkend="mthInitDialog"/> method.
   </para>
   <para>
     <emphasis role="bold">Note</emphasis> that to properly handle and process mouse event messages, it is usually