summaryrefslogtreecommitdiffstats
path: root/doc/html/ntqsplashscreen.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/html/ntqsplashscreen.html')
-rw-r--r--doc/html/ntqsplashscreen.html16
1 files changed, 8 insertions, 8 deletions
diff --git a/doc/html/ntqsplashscreen.html b/doc/html/ntqsplashscreen.html
index b2646ebb4..03e3375e5 100644
--- a/doc/html/ntqsplashscreen.html
+++ b/doc/html/ntqsplashscreen.html
@@ -35,7 +35,7 @@ body { background: #ffffff; color: black; }
be shown during application startup.
<a href="#details">More...</a>
<p><tt>#include &lt;<a href="qsplashscreen-h.html">ntqsplashscreen.h</a>&gt;</tt>
-<p>Inherits <a href="ntqwidget.html">TQWidget</a>.
+<p>Inherits <a href="tqwidget.html">TQWidget</a>.
<p><a href="qsplashscreen-members.html">List of all member functions.</a>
<h2>Public Members</h2>
<ul>
@@ -75,7 +75,7 @@ provide the user with feedback that the application is loading.
the <a href="ntqt.html#WidgetFlags-enum">WStyle_StaysOnTop</a> if you desire to keep above all the windows in the
GUI.
<p> Some X11 window managers do not support the "stays on top" flag. A
-solution is to set up a timer that periodically calls <a href="ntqwidget.html#raise">raise</a>() on
+solution is to set up a timer that periodically calls <a href="tqwidget.html#raise">raise</a>() on
the splash screen to simulate the "stays on top" effect.
<p> The most common usage is to show a splash screen before the main
widget is displayed on the screen. This is illustrated in the
@@ -86,11 +86,11 @@ following code snippet.
<a href="ntqapplication.html">TQApplication</a> app( argc, argv );
<a href="ntqpixmap.html">TQPixmap</a> pixmap( "splash.png" );
TQSplashScreen *splash = new TQSplashScreen( pixmap );
- splash-&gt;<a href="ntqwidget.html#show">show</a>();
+ splash-&gt;<a href="tqwidget.html#show">show</a>();
<a href="ntqmainwindow.html">TQMainWindow</a> *mainWin = new <a href="ntqmainwindow.html">TQMainWindow</a>;
...
app.<a href="ntqapplication.html#setMainWidget">setMainWidget</a>( mainWin );
- mainWin-&gt;<a href="ntqwidget.html#show">show</a>();
+ mainWin-&gt;<a href="tqwidget.html#show">show</a>();
splash-&gt;<a href="#finish">finish</a>( mainWin );
delete splash;
return app.<a href="ntqapplication.html#exec">exec</a>();
@@ -111,7 +111,7 @@ call <a href="ntqapplication.html#processEvents">TQApplication::processEvents</a
<p> <pre>
<a href="ntqpixmap.html">TQPixmap</a> pixmap( "splash.png" );
TQSplashScreen *splash = new TQSplashScreen( pixmap );
- splash-&gt;<a href="ntqwidget.html#show">show</a>();
+ splash-&gt;<a href="tqwidget.html#show">show</a>();
... // Loading some items
splash-&gt;<a href="#message">message</a>( "Loaded modules" );
tqApp-&gt;<a href="ntqapplication.html#processEvents">processEvents</a>();
@@ -145,10 +145,10 @@ The default implementation draws the message passed by <a href="#message">messag
Reimplement this function if you want to do your own drawing on
the splash screen.
-<h3 class=fn>void <a name="finish"></a>TQSplashScreen::finish ( <a href="ntqwidget.html">TQWidget</a>&nbsp;*&nbsp;mainWin )
+<h3 class=fn>void <a name="finish"></a>TQSplashScreen::finish ( <a href="tqwidget.html">TQWidget</a>&nbsp;*&nbsp;mainWin )
</h3>
Makes the splash screen wait until the widget <em>mainWin</em> is displayed
-before calling <a href="ntqwidget.html#close">close</a>() on itself.
+before calling <a href="tqwidget.html#close">close</a>() on itself.
<h3 class=fn>void <a name="message"></a>TQSplashScreen::message ( const&nbsp;<a href="ntqstring.html">TQString</a>&nbsp;&amp;&nbsp;message, int&nbsp;alignment = AlignLeft, const&nbsp;<a href="ntqcolor.html">TQColor</a>&nbsp;&amp;&nbsp;color = black )<tt> [slot]</tt>
</h3>
@@ -170,7 +170,7 @@ does not have any of the text drawn by <a href="#message">message</a>() calls.
<h3 class=fn>void <a name="repaint"></a>TQSplashScreen::repaint ()
</h3>
-This overrides <a href="ntqwidget.html#repaint">TQWidget::repaint</a>(). It differs from the standard
+This overrides <a href="tqwidget.html#repaint">TQWidget::repaint</a>(). It differs from the standard
repaint function in that it also calls <a href="ntqapplication.html#flush">TQApplication::flush</a>() to
ensure the updates are displayed, even when there is no event loop
present.