Update to latest tqt3 automated conversion

1 files changed, 6 insertions, 6 deletions

diff --git a/doc/html/mac-differences.html b/doc/html/mac-differences.html
index c9a6eced5..c5653af30 100644
--- a/doc/html/mac-differences.html
+++ b/doc/html/mac-differences.html
@@ -103,7 +103,7 @@ Native</a>.
 or using the open(1) command. Mac OS X needs this to dispatch events correctly,
 as well as gaining access to the menubar. If using GDB you must run with the 
 full path to the executable.
-<p> <h2> <a href="qcursor.html">TQCursor</a>
+<p> <h2> <a href="ntqcursor.html">TQCursor</a>
 </h2>
 <a name="2"></a><p> Due to Mac OS X having only 16x16 custom cursors TQCursor is limited by this
 as well. For now the only workaround to this problem is to use a small
@@ -182,7 +182,7 @@ automatically included in the make builds.
 <a name="6-1"></a><p> If a static build fails with the following error messages during the
 designer make phase:
 <p> <pre>
-TQWidget::<a href="qwidget.html#sizeHint">sizeHint</a>() const referenced from libtqui expected to be defined in @executable_path/../Frameworks/libtqt-mt.3.dylib
+TQWidget::<a href="ntqwidget.html#sizeHint">sizeHint</a>() const referenced from libtqui expected to be defined in @executable_path/../Frameworks/libtqt-mt.3.dylib
 non-virtual thunk [nv:-40] to TQWidget::metric(int) const referenced from libtqui
  expected to be defined in @executable_path/../Frameworks/libtqt-mt.3.dylib
 </pre>
@@ -204,7 +204,7 @@ do this:
                                                kCFURLPOSIXPathStyle);
         const char *pathPtr = CFStringGetCStringPtr(macPath, 
                                                CFStringGetSystemEncoding());
-        <a href="qapplication.html#qDebug">qDebug</a>("Path = %s", pathPtr);
+        <a href="ntqapplication.html#qDebug">qDebug</a>("Path = %s", pathPtr);
         CFRelease(pluginRef);
         CFRelease(macPath);
 </pre>
@@ -254,8 +254,8 @@ one-button mouse support.
 into Mac native menubars. Fitting this into your existing TQt application
 will normally be automatic, however, if you have special needs the TQt/Mac
 implementation currently selects a menubar by starting at the active window
-(ie <a href="qapplication.html#activeWindow">TQApplication::activeWindow</a>()), and applying:
-<p> 1) If the window has a <a href="qmenubar.html">TQMenuBar</a> then it is used.
+(ie <a href="ntqapplication.html#activeWindow">TQApplication::activeWindow</a>()), and applying:
+<p> 1) If the window has a <a href="ntqmenubar.html">TQMenuBar</a> then it is used.
 2) If the window is a modal then its menubar is used. If no menubar is
 specified then a default menubar is used (as documented below)
 3) If the window has no parent then the default menubar is used (as documented below).
@@ -273,7 +273,7 @@ used whenever a default menubar is needed.
 <p> <li> TQCustomMenuItems are not supported in Mac native menubars, they are supported
 in popupmenus that are not in the Mac native menubar.
 <p> <li> Items with accelerators that have more than one keystroke
-(<a href="qkeysequence.html">TQKeySequence</a>) will not be honored, and the first key will be used.
+(<a href="ntqkeysequence.html">TQKeySequence</a>) will not be honored, and the first key will be used.
 <p> </ul>
 <p> <h3> Unsupported Native Widgets
 </h3>