@ -1900,7 +1900,7 @@ similar to the C printf() function.
is sent to the debugger.
<p><b>Warning:</b> The internal buffer is limited to 8196 bytes (including
the '\0'-terminator).
<p><b>Warning:</b> Passing (const char *)0 as argument to qDebug might lead
<p><b>Warning:</b> Passing (const char *)0 as argument to tqDebug might lead
to crashes on certain platforms due to the platforms printf implementation.
<p><p>See also <ahref="#qWarning">qWarning</a>(), <ahref="#qFatal">qFatal</a>(), <ahref="#qInstallMsgHandler">qInstallMsgHandler</a>(), and <ahref="debug.html">Debugging</a>.
@ -1926,7 +1926,7 @@ similar to the C printf() function.
is sent to the debugger.
<p><b>Warning:</b> The internal buffer is limited to 8196 bytes (including
the '\0'-terminator).
<p><b>Warning:</b> Passing (const char *)0 as argument to qFatal might lead
<p><b>Warning:</b> Passing (const char *)0 as argument to tqFatal might lead
to crashes on certain platforms due to the platforms printf implementation.
<p><p>See also <ahref="#qDebug">qDebug</a>(), <ahref="#qWarning">qWarning</a>(), <ahref="#qInstallMsgHandler">qInstallMsgHandler</a>(), and <ahref="debug.html">Debugging</a>.
@ -2029,7 +2029,7 @@ similar to the C printf() function.
is sent to the debugger.
<p><b>Warning:</b> The internal buffer is limited to 8196 bytes (including
the '\0'-terminator).
<p><b>Warning:</b> Passing (const char *)0 as argument to qWarning might lead
<p><b>Warning:</b> Passing (const char *)0 as argument to tqWarning might lead
to crashes on certain platforms due to the platforms printf implementation.
<p><p>See also <ahref="#qDebug">qDebug</a>(), <ahref="#qFatal">qFatal</a>(), <ahref="#qInstallMsgHandler">qInstallMsgHandler</a>(), and <ahref="debug.html">Debugging</a>.
<p>Use <em>qmake</em> as before to generate a makefile. If you rename <em>main.cpp</em> temporarily, you will see the message and <em>qmake</em> will stop processing.</p>
<h3><aname="6"></a>Checking for more than one condition</h3>
<p>Suppose you use Windows and you want to be able to see the qDebug() statements when you run your application on the command line. Unless you build your application with the console setting, you won't see the output. We can easily put <em>console</em> on the CONFIG line so that on Windows the makefile will have this setting. But let's say that we only want to add the CONFIG line if we are running on Windows <em>and</em> when <em>debug</em> is already on the CONFIG line. This requires using two nested scopes; just create one scope, then create the other inside that one. Put the settings to be processed inside the last scope, like this:</p>
<p>Suppose you use Windows and you want to be able to see the tqDebug() statements when you run your application on the command line. Unless you build your application with the console setting, you won't see the output. We can easily put <em>console</em> on the CONFIG line so that on Windows the makefile will have this setting. But let's say that we only want to add the CONFIG line if we are running on Windows <em>and</em> when <em>debug</em> is already on the CONFIG line. This requires using two nested scopes; just create one scope, then create the other inside that one. Put the settings to be processed inside the last scope, like this:</p>
If \fCb\fR is zero, the Q_ASSERT statement will output the following message using the qWarning() function:
If \fCb\fR is zero, the Q_ASSERT statement will output the following message using the tqWarning() function:
.PP
.nf
.br
@ -1704,7 +1704,7 @@ If \fCb\fR is zero, the Q_ASSERT statement will output the following message usi
.br
.fi
.PP
See also qWarning() and Debugging.
See also tqWarning() and Debugging.
.SH "void Q_CHECK_PTR ( void * p )"
If \fIp\fR is 0, prints a warning message containing the source code file name and line number, saying that the program ran out of memory.
.PP
@ -1726,8 +1726,8 @@ Example:
.br
.fi
.PP
See also qWarning() and Debugging.
.SH "void qAddPostRoutine ( QtCleanUpFunction p )"
See also tqWarning() and Debugging.
.SH "void tqAddPostRoutine ( QtCleanUpFunction p )"
Adds a global routine that will be called from the QApplication destructor. This function is normally used to add cleanup routines for program-wide functionality.
.PP
The function given by \fIp\fR should take no arguments and return nothing, like this:
@ -1754,13 +1754,13 @@ The function given by \fIp\fR should take no arguments and return nothing, like
.br
global_ptr = new int[100]; // allocate data
.br
qAddPostRoutine( cleanup_ptr ); // delete later
tqAddPostRoutine( cleanup_ptr ); // delete later
.br
}
.br
.fi
.PP
Note that for an application- or module-wide cleanup, qAddPostRoutine() is often not suitable. People have a tendency to make such modules dynamically loaded, and then unload those modules long before the QApplication destructor is called, for example.
Note that for an application- or module-wide cleanup, tqAddPostRoutine() is often not suitable. People have a tendency to make such modules dynamically loaded, and then unload those modules long before the QApplication destructor is called, for example.
.PP
For modules and libraries, using a reference-counted initialization manager or Qt' parent-child delete mechanism may be better. Here is an example of a private class which uses the parent-child mechanism to call a cleanup function at the right time:
.PP
@ -1803,7 +1803,7 @@ For modules and libraries, using a reference-counted initialization manager or Q
.fi
.PP
By selecting the right parent widget/object, this can often be made to clean up the module's data at the exact right moment.
.SH "void qDebug ( const char * msg, ... )"
.SH "void tqDebug ( const char * msg, ... )"
Prints a debug message \fImsg\fR, or calls the message handler (if it has been installed).
.PP
This function takes a format string and a list of arguments, similar to the C printf() function.
@ -1812,7 +1812,7 @@ Example:
.PP
.nf
.br
qDebug( "my window handle = %x", myWidget->id() );
tqDebug( "my window handle = %x", myWidget->id() );
.br
.fi
.PP
@ -1820,10 +1820,10 @@ Under X11, the text is printed to stderr. Under Windows, the text is sent to the
.PP
\fBWarning:\fR The internal buffer is limited to 8196 bytes (including the '\0'-terminator).
.PP
\fBWarning:\fR Passing (const char *)0 as argument to qDebug might lead to crashes on certain platforms due to the platforms printf implementation.
\fBWarning:\fR Passing (const char *)0 as argument to tqDebug might lead to crashes on certain platforms due to the platforms printf implementation.
.PP
See also qWarning(), qFatal(), qInstallMsgHandler(), and Debugging.
.SH "void qFatal ( const char * msg, ... )"
See also tqWarning(), tqFatal(), qInstallMsgHandler(), and Debugging.
.SH "void tqFatal ( const char * msg, ... )"
Prints a fatal error message \fImsg\fR and exits, or calls the message handler (if it has been installed).
.PP
This function takes a format string and a list of arguments, similar to the C printf() function.
@ -1838,7 +1838,7 @@ Example:
.br
if ( b == 0 ) // program error
.br
qFatal( "divide: cannot divide by zero" );
tqFatal( "divide: cannot divide by zero" );
.br
return a/b;
.br
@ -1850,9 +1850,9 @@ Under X11, the text is printed to stderr. Under Windows, the text is sent to the
.PP
\fBWarning:\fR The internal buffer is limited to 8196 bytes (including the '\0'-terminator).
.PP
\fBWarning:\fR Passing (const char *)0 as argument to qFatal might lead to crashes on certain platforms due to the platforms printf implementation.
\fBWarning:\fR Passing (const char *)0 as argument to tqFatal might lead to crashes on certain platforms due to the platforms printf implementation.
.PP
See also qDebug(), qWarning(), qInstallMsgHandler(), and Debugging.
See also tqDebug(), tqWarning(), qInstallMsgHandler(), and Debugging.
.SH "QtMsgHandler qInstallMsgHandler ( QtMsgHandler h )"
Installs a Qt message handler \fIh\fR. Returns a pointer to the message handler previously defined.
.PP
@ -1920,22 +1920,22 @@ Example:
.br
.fi
.PP
See also qDebug(), qWarning(), qFatal(), and Debugging.
The system's word size in bits (typically 32) is returned in \fI*wordSize\fR. The \fI*bigEndian\fR is set to TRUE if this is a big-endian machine, or to FALSE if this is a little-endian machine.
.PP
In debug mode, this function calls qFatal() with a message if the computer is truly weird (i.e. different endianness for 16 bit and 32 bit integers); in release mode it returns FALSE.
In debug mode, this function calls tqFatal() with a message if the computer is truly weird (i.e. different endianness for 16 bit and 32 bit integers); in release mode it returns FALSE.
Prints the message \fImsg\fR and uses \fIcode\fR to get a system specific error message. When \fIcode\fR is -1 (the default), the system's last error code will be used if possible. Use this method to handle failures in platform specific API calls.
.PP
This function does nothing when Qt is built with \fCQT_NO_DEBUG\fR defined.
.SH "const char * qVersion ()"
.SH "const char * tqVersion ()"
Returns the Qt version number as a string, for example, "2.3.0" or" 3.0.5".
.PP
The \fCQT_VERSION\fR define has the numeric value in the form: 0xmmiibb (m = major, i = minor, b = bugfix). For example, Qt 3.0.5's \fCQT_VERSION\fR is 0x030005.
.SH "void qWarning ( const char * msg, ... )"
.SH "void tqWarning ( const char * msg, ... )"
Prints a warning message \fImsg\fR, or calls the message handler (if it has been installed).
.PP
This function takes a format string and a list of arguments, similar to the C printf() function.
@ -1950,7 +1950,7 @@ Example:
.br
if ( c > 200 )
.br
qWarning( "f: bad argument, c == %d", c );
tqWarning( "f: bad argument, c == %d", c );
.br
}
.br
@ -1960,9 +1960,9 @@ Under X11, the text is printed to stderr. Under Windows, the text is sent to the
.PP
\fBWarning:\fR The internal buffer is limited to 8196 bytes (including the '\0'-terminator).
.PP
\fBWarning:\fR Passing (const char *)0 as argument to qWarning might lead to crashes on certain platforms due to the platforms printf implementation.
\fBWarning:\fR Passing (const char *)0 as argument to tqWarning might lead to crashes on certain platforms due to the platforms printf implementation.
.PP
See also qDebug(), qFatal(), qInstallMsgHandler(), and Debugging.
See also tqDebug(), tqFatal(), qInstallMsgHandler(), and Debugging.
@ -151,7 +151,7 @@ See also maxCost() and totalCost().
.SH "uint QAsciiCache::size () const"
Returns the size of the hash array used to implement the cache. This should be a bit bigger than count() is likely to be.
.SH "void QAsciiCache::statistics () const"
A debug-only utility function. Prints out cache usage, hit/miss, and distribution information using qDebug(). This function does nothing in the release library.
A debug-only utility function. Prints out cache usage, hit/miss, and distribution information using tqDebug(). This function does nothing in the release library.
.SH "type * QAsciiCache::take ( const char * k )"
Takes the item associated with \fIk\fR out of the cache without deleting it and returns a pointer to the item taken out, or 0 if the key does not exist in the cache.
@ -175,7 +175,7 @@ See also maxCost() and totalCost().
.SH "uint QCache::size () const"
Returns the size of the hash array used to implement the cache. This should be a bit bigger than count() is likely to be.
.SH "void QCache::statistics () const"
A debug-only utility function. Prints out cache usage, hit/miss, and distribution information using qDebug(). This function does nothing in the release library.
A debug-only utility function. Prints out cache usage, hit/miss, and distribution information using tqDebug(). This function does nothing in the release library.
.SH "type * QCache::take ( const QString & k )"
Takes the item associated with \fIk\fR out of the cache without deleting it, and returns a pointer to the item taken out, or 0 if the key does not exist in the cache.
Copies at most \fIlen\fR bytes from \fIsrc\fR (stopping at \fIlen\fR or the terminating '\0' whichever comes first) into \fIdst\fR and returns a pointer to \fIdst\fR. Guarantees that \fIdst\fR is '\0'-terminated. If \fIsrc\fR or \fIdst\fR is 0, returns 0 immediately.
@ -43,7 +43,7 @@ There are two ways to use this class: <ol type=1>
.IP 1
For production applications. In this context the class can be used to display messages which you don't need the user to see more than once. To use QErrorMessage like this, you create the dialog in the usual way and call the message() slot, or connect signals to it.
.IP 2
For developers. In this context the static qtHandler() installs a message handler using qInstallMsgHandler() and creates a QErrorMessage that displays qDebug(), qWarning() and qFatal() messages.
For developers. In this context the static qtHandler() installs a message handler using qInstallMsgHandler() and creates a QErrorMessage that displays tqDebug(), tqWarning() and tqFatal() messages.
.PP
In both cases QErrorMessage will queue pending messages, and display them (or not) in order, as soon as the user presses Enter or clicks OK after seeing each message.
@ -156,7 +156,7 @@ If you want to use QFtp with the QNetworkProtocol interface, you do not use it d
.br
.fi
.PP
This code will only work if the QFtp class is registered; to register the class, you must call qInitNetworkProtocols() before using a QUrlOperator with QFtp.
This code will only work if the QFtp class is registered; to register the class, you must call tqInitNetworkProtocols() before using a QUrlOperator with QFtp.
.PP
The rest of this descrption describes the direct interface to FTP.
@ -144,7 +144,7 @@ If you want to use QHttp with the QNetworkProtocol interface, you do not use it
.br
.fi
.PP
This code will only work if the QHttp class is registered; to register the class, you must call qInitNetworkProtocols() before using a QUrlOperator with HTTP.
This code will only work if the QHttp class is registered; to register the class, you must call tqInitNetworkProtocols() before using a QUrlOperator with HTTP.
.PP
The QNetworkProtocol interface for HTTP only supports the operations operationGet() and operationPut(), i.e. QUrlOperator::get() and QUrlOperator::put(), if you use it with a QUrlOperator.
@ -145,7 +145,7 @@ See also maxCost() and totalCost().
.SH "uint QIntCache::size () const"
Returns the size of the hash array used to implement the cache. This should be a bit larger than count() is likely to be.
.SH "void QIntCache::statistics () const"
A debug-only utility function. Prints out cache usage, hit/miss, and distribution information using qDebug(). This function does nothing in the release library.
A debug-only utility function. Prints out cache usage, hit/miss, and distribution information using tqDebug(). This function does nothing in the release library.
.SH "type * QIntCache::take ( long k )"
Takes the item associated with \fIk\fR out of the cache without deleting it, and returns a pointer to the item taken out or 0 if the key does not exist in the cache.
@ -32,7 +32,7 @@ This class is derived from QNetworkProtocol. QLocalFs is not normally used direc
.br
.fi
.PP
This code will only work if the QLocalFs class is registered; to register the class, you must call qInitNetworkProtocols() before using a QUrlOperator with QLocalFs.
This code will only work if the QLocalFs class is registered; to register the class, you must call tqInitNetworkProtocols() before using a QUrlOperator with QLocalFs.
.PP
If you really need to use QLocalFs directly, don't forget to set its QUrlOperator with setUrl().
@ -668,7 +668,7 @@ Here's a \fCKeyPressEater\fR class that eats the key presses of its monitored ob
.br
QKeyEvent *k = (QKeyEvent *)e;
.br
qDebug( "Ate key press %d", k->key() );
tqDebug( "Ate key press %d", k->key() );
.br
return TRUE; // eat event
.br
@ -903,7 +903,7 @@ Example:
.br
{
.br
qDebug( "timer event, id %d", e->timerId() );
tqDebug( "timer event, id %d", e->timerId() );
.br
}
.br
@ -945,11 +945,11 @@ You can find an object by name (and type) using child(). You can find a set of o
.PP
The object name is set by the constructor or by the setName() function. The object name is not very useful in the current version of Qt, but will become increasingly important in the future.
.PP
If the object does not have a name, the name() function returns" unnamed", so printf() (used in qDebug()) will not be asked to output a null pointer. If you want a null pointer to be returned for unnamed objects, you can call name( 0 ).
If the object does not have a name, the name() function returns" unnamed", so printf() (used in tqDebug()) will not be asked to output a null pointer. If you want a null pointer to be returned for unnamed objects, you can call name( 0 ).
@ -770,7 +770,7 @@ The following example shows how we could create a 'status' string when processin
.PP
It is generally fine to use filenames and numbers as we have done in the example above. But note that using arg() to construct natural language sentences does not usually translate well into other languages because sentence structure and word order often differ between languages.
.PP
If there is no place marker (\fC%1\fR, \fC%2\fR, etc.), a warning message (qWarning()) is output and the result is undefined.
If there is no place marker (\fC%1\fR, \fC%2\fR, etc.), a warning message (tqWarning()) is output and the result is undefined.
.PP
\fBWarning:\fR If any placeholder occurs more than once, the result is undefined.
.SH "QString QString::arg ( long a, int fieldWidth = 0, int base = 10 ) const"
@ -149,7 +149,7 @@ If you want to be notified about success/failure, progress, etc., you can connec
.PP
The class uses the functionality of registered network protocols to perform these operations. Depending of the protocol of the URL, it uses an appropriate network protocol class for the operations. Each of the operation functions of QUrlOperator creates a QNetworkOperation object that describes the operation and puts it into the operation queue for the network protocol used. If no suitable protocol could be found (because no implementation of the necessary network protocol is registered), the URL operator emits errors. Not every protocol supports every operation, but error handling deals with this problem.
.PP
To register the available network protocols, use the qInitNetworkProtocols() function. The protocols currently supported are:
To register the available network protocols, use the tqInitNetworkProtocols() function. The protocols currently supported are:
.TP
FTP,
.TP
@ -348,7 +348,7 @@ See also copy().
.SH "void QUrlOperator::stop ()\fC [virtual]\fR"
Stops the current network operation and removes all this QUrlOperator's waiting network operations.
.SH RELATED FUNCTION DOCUMENTATION
.SH "void qInitNetworkProtocols ()"
.SH "void tqInitNetworkProtocols ()"
This function registers the network protocols for FTP and HTTP. You must call this function before you use QUrlOperator for these protocols.
@ -68,7 +68,7 @@ must register them before you can use QUrlOperator. For example, put
the following call in your \c main() function, after creating your
QApplication object:
\code
qInitNetworkProtocols();
tqInitNetworkProtocols();
\endcode
\section1 Network- and Protocol-Transparent Operations
@ -325,7 +325,7 @@ But, before we can use our new protocol, we have to register it first, so QUrlOp
\skipto register
\printline register
This registers Qip protocol and bonds it to prefix "qip". You can use qInitNetworkProtocols() which registers pre coded Ftp (for "ftp") and Http ("http") protocols. Local file system (QLocalFs) is always registered.
This registers Qip protocol and bonds it to prefix "qip". You can use tqInitNetworkProtocols() which registers pre coded Ftp (for "ftp") and Http ("http") protocols. Local file system (QLocalFs) is always registered.
@ -297,7 +297,7 @@ bool QAccessibleWidget::doDefaultAction( int control )
{
#if defined(QT_DEBUG)
if(control)
qWarning("QAccessibleWidget::doDefaultAction: This implementation does not support subelements! (ID %d unknown for %s)",control,widget()->className());
tqWarning("QAccessibleWidget::doDefaultAction: This implementation does not support subelements! (ID %d unknown for %s)",control,widget()->className());
#else
Q_UNUSED(control)
#endif
@ -407,7 +407,7 @@ bool QAccessibleWidget::setFocus( int control )
{
#if defined(QT_DEBUG)
if(control)
qWarning("QAccessibleWidget::setFocus: This implementation does not support subelements! (ID %d unknown for %s)",control,widget()->className());
tqWarning("QAccessibleWidget::setFocus: This implementation does not support subelements! (ID %d unknown for %s)",control,widget()->className());
#else
Q_UNUSED(control)
#endif
@ -422,7 +422,7 @@ bool QAccessibleWidget::setFocus( int control )
boolQAccessibleWidget::setSelected(int,bool,bool)
{
#if defined(QT_DEBUG)
qWarning("QAccessibleWidget::setSelected: This function not supported for simple widgets.");
tqWarning("QAccessibleWidget::setSelected: This function not supported for simple widgets.");
MoveWizardPageCommand*cmd=newMoveWizardPageCommand(tr("Move page %1 to %2 in %3").arg(draggedItem).arg(droppedItem).arg(wizard->name()),formwindow,wizard,draggedItem,droppedItem);
