summaryrefslogtreecommitdiffstats
path: root/doc/html/ntqerrormessage.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/html/ntqerrormessage.html')
-rw-r--r--doc/html/ntqerrormessage.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/html/ntqerrormessage.html b/doc/html/ntqerrormessage.html
index 1876f4319..5e26f2164 100644
--- a/doc/html/ntqerrormessage.html
+++ b/doc/html/ntqerrormessage.html
@@ -64,7 +64,7 @@ TQErrorMessage like this, you create the dialog in the usual way and call the
<a href="#message">message</a>() slot, or connect signals to it.
<p> <li> For developers. In this context the static <a href="#qtHandler">qtHandler</a>() installs
a message handler using <a href="ntqapplication.html#qInstallMsgHandler">qInstallMsgHandler</a>() and creates a TQErrorMessage
-that displays <a href="ntqapplication.html#qDebug">qDebug</a>(), <a href="ntqapplication.html#qWarning">qWarning</a>() and <a href="ntqapplication.html#qFatal">qFatal</a>() messages.
+that displays <a href="ntqapplication.html#qDebug">tqDebug</a>(), <a href="ntqapplication.html#qWarning">tqWarning</a>() and <a href="ntqapplication.html#qFatal">tqFatal</a>() messages.
</ol>
<p> In both cases TQErrorMessage will queue pending messages, and display
them (or not) in order, as soon as the user presses Enter or clicks OK