Update to latest tqt3 automated conversion

1 files changed, 7 insertions, 7 deletions

diff --git a/doc/html/qimevent.html b/doc/html/qimevent.html
index 1b0cfcba0..1f32bb3f8 100644
--- a/doc/html/qimevent.html
+++ b/doc/html/qimevent.html
@@ -33,8 +33,8 @@ body { background: #ffffff; color: black; }
 
 <p>The TQIMEvent class provides parameters for input method events.
 <a href="#details">More...</a>
-<p><tt>#include &lt;<a href="qevent-h.html">qevent.h</a>&gt;</tt>
-<p>Inherits <a href="qevent.html">TQEvent</a>.
+<p><tt>#include &lt;<a href="qevent-h.html">ntqevent.h</a>&gt;</tt>
+<p>Inherits <a href="ntqevent.html">TQEvent</a>.
 <p><a href="qimevent-members.html">List of all member functions.</a>
 <h2>Public Members</h2>
 <ul>
@@ -80,7 +80,7 @@ not be Spacebar, Enter and Escape.
 <p> These three stages are represented by three different types of
 events. The IMStartEvent, IMComposeEvent and IMEndEvent. When a
 new input context is created, an IMStartEvent will be sent to the
-widget and delivered to the <a href="qwidget.html#imStartEvent">TQWidget::imStartEvent</a>() function.
+widget and delivered to the <a href="ntqwidget.html#imStartEvent">TQWidget::imStartEvent</a>() function.
 The widget can then update internal data structures to reflect
 this.
 <p> After this, an IMComposeEvent will be sent to the widget for
@@ -90,7 +90,7 @@ position within the composition string. This string is temporary
 and can change with every key the user types, so the widget will
 need to store the state before the composition started (the state
 it had when it received the IMStartEvent). IMComposeEvents will be
-delivered to the <a href="qwidget.html#imComposeEvent">TQWidget::imComposeEvent</a>() function.
+delivered to the <a href="ntqwidget.html#imComposeEvent">TQWidget::imComposeEvent</a>() function.
 <p> Usually, widgets try to mark the part of the text that is part of
 the current composition in a way that is visible to the user. A
 commonly used visual cue is to use a dotted underline.
@@ -99,7 +99,7 @@ be sent to the widget. The event contains the final string the
 user selected, and could be empty if they canceled the
 composition. This string should be accepted as the final text the
 user entered, and the intermediate composition string should be
-cleared. These events are delivered to <a href="qwidget.html#imEndEvent">TQWidget::imEndEvent</a>().
+cleared. These events are delivered to <a href="ntqwidget.html#imEndEvent">TQWidget::imEndEvent</a>().
 <p> If the user clicks another widget, taking the focus out of the
 widget where the composition is taking place the IMEndEvent will
 be sent and the string it holds will be the result of the
@@ -107,7 +107,7 @@ composition up to that point (which may be an empty string).
 <p>See also <a href="events.html">Event Classes</a>.
 
 <hr><h2>Member Function Documentation</h2>
-<h3 class=fn><a name="TQIMEvent"></a>TQIMEvent::TQIMEvent ( <a href="qevent.html#Type-enum">Type</a>&nbsp;type, const&nbsp;<a href="qstring.html">TQString</a>&nbsp;&amp;&nbsp;text, int&nbsp;cursorPosition )
+<h3 class=fn><a name="TQIMEvent"></a>TQIMEvent::TQIMEvent ( <a href="ntqevent.html#Type-enum">Type</a>&nbsp;type, const&nbsp;<a href="ntqstring.html">TQString</a>&nbsp;&amp;&nbsp;text, int&nbsp;cursorPosition )
 </h3>
 
 <p> Constructs a new TQIMEvent with the accept flag set to FALSE. <em>type</em> can be one of TQEvent::IMStartEvent, TQEvent::IMComposeEvent
@@ -153,7 +153,7 @@ starting at <a href="#cursorPos">cursorPos</a>() ) that should be marked as sele
 input widget receiving the event.
 Will return 0 for IMStartEvent and IMEndEvent.
 
-<h3 class=fn>const&nbsp;<a href="qstring.html">TQString</a>&nbsp;&amp; <a name="text"></a>TQIMEvent::text () const
+<h3 class=fn>const&nbsp;<a href="ntqstring.html">TQString</a>&nbsp;&amp; <a name="text"></a>TQIMEvent::text () const
 </h3>
 
 <p> Returns the composition text. This is a null string for an