diff options
Diffstat (limited to 'doc/man/man3/qapplication.3qt')
| -rw-r--r-- | doc/man/man3/qapplication.3qt | 46 |
1 files changed, 23 insertions, 23 deletions
diff --git a/doc/man/man3/qapplication.3qt b/doc/man/man3/qapplication.3qt index 0be4627..45aeaba 100644 --- a/doc/man/man3/qapplication.3qt +++ b/doc/man/man3/qapplication.3qt @@ -1696,7 +1696,7 @@ Example: .br .fi .PP -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. -.SH "bool qSysInfo ( int * wordSize, bool * bigEndian )" +See also tqDebug(), tqWarning(), tqFatal(), and Debugging. +.SH "bool tqSysInfo ( int * wordSize, bool * bigEndian )" Obtains information about the system. .PP 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. -.SH "void qSystemWarning ( const char * msg, int code )" +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. +.SH "void tqSystemWarning ( const char * msg, int code )" 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. .SH "SEE ALSO" .BR http://doc.trolltech.com/qapplication.html |