diff options
Diffstat (limited to 'doc/man/man3/tqapplication.3qt')
| -rw-r--r-- | doc/man/man3/tqapplication.3qt | 76 |
1 files changed, 38 insertions, 38 deletions
diff --git a/doc/man/man3/tqapplication.3qt b/doc/man/man3/tqapplication.3qt index 90a960b60..9f9b2e3d3 100644 --- a/doc/man/man3/tqapplication.3qt +++ b/doc/man/man3/tqapplication.3qt @@ -471,7 +471,7 @@ l - l. Groups of functions System settings desktopSettingsAware(), setDesktopSet .fi </center> .PP -\fINon-GUI programs:\fR While Qt is not optimized or designed for writing non-GUI programs, it's possible to use some of its classes without creating a QApplication. This can be useful if you wish to share code between a non-GUI server and a GUI client. +\fINon-GUI programs:\fR While TQt is not optimized or designed for writing non-GUI programs, it's possible to use some of its classes without creating a QApplication. This can be useful if you wish to share code between a non-GUI server and a GUI client. .PP See also Main Window and Related Classes. .SS "Member Type Documentation" @@ -507,11 +507,11 @@ The global \fCqApp\fR pointer refers to this application object. Only one applic .PP This application object must be constructed before any paint devices (including widgets, pixmaps, bitmaps etc.). .PP -Note that \fIargc\fR and \fIargv\fR might be changed. Qt removes command line arguments that it recognizes. The modified \fIargc\fR and \fIargv\fR can also be accessed later with \fCqApp->argc()\fR and \fCqApp->argv()\fR. The documentation for argv() contains a detailed description of how to process command line arguments. +Note that \fIargc\fR and \fIargv\fR might be changed. TQt removes command line arguments that it recognizes. The modified \fIargc\fR and \fIargv\fR can also be accessed later with \fCqApp->argc()\fR and \fCqApp->argv()\fR. The documentation for argv() contains a detailed description of how to process command line arguments. .PP -Qt debugging options (not available if Qt was compiled with the QT_NO_DEBUG flag defined): +Qt debugging options (not available if TQt was compiled with the QT_NO_DEBUG flag defined): .TP --nograb, tells Qt that it must never grab the mouse or the keyboard. +-nograb, tells TQt that it must never grab the mouse or the keyboard. .TP -dograb (only under X11), running under a debugger can cause an implicit -nograb, use -dograb to override. .TP @@ -519,11 +519,11 @@ Qt debugging options (not available if Qt was compiled with the QT_NO_DEBUG flag .PP See Debugging Techniques for a more detailed explanation. .PP -All Qt programs automatically support the following command line options: +All TQt programs automatically support the following command line options: .TP -reverse causes text to be formatted for right-to-left languages rather than in the usual left-to-right direction. .TP --style= \fIstyle\fR, sets the application GUI style. Possible values are \fCmotif\fR, \fCwindows\fR, and \fCplatinum\fR. If you compiled Qt with additional styles or have additional styles as plugins these will be available to the \fC-style\fR command line option. +-style= \fIstyle\fR, sets the application GUI style. Possible values are \fCmotif\fR, \fCwindows\fR, and \fCplatinum\fR. If you compiled TQt with additional styles or have additional styles as plugins these will be available to the \fC-style\fR command line option. .TP -style \fIstyle\fR, is the same as listed above. .TP @@ -533,7 +533,7 @@ All Qt programs automatically support the following command line options: .TP -widgetcount, prints debug message at the end about number of widgets left undestroyed and maximum number of widgets existed at the same time .PP -The X11 version of Qt also supports some traditional X11 command line options: +The X11 version of TQt also supports some traditional X11 command line options: .TP -display \fIdisplay\fR, sets the X display (default is $DISPLAY). .TP @@ -611,19 +611,19 @@ For Qt/Embedded, passing QApplication::GuiServer for \fItype\fR makes this appli .SH "QApplication::QApplication ( Display * dpy, HANDLE visual = 0, HANDLE colormap = 0 )" Create an application, given an already open display \fIdpy\fR. If \fIvisual\fR and \fIcolormap\fR are non-zero, the application will use those as the default Visual and Colormap contexts. .PP -\fBWarning:\fR Qt only supports TrueColor visuals at depths higher than 8 bits-per-pixel. +\fBWarning:\fR TQt only supports TrueColor visuals at depths higher than 8 bits-per-pixel. .PP This is available only on X11. .SH "QApplication::QApplication ( Display * dpy, int argc, char ** argv, HANDLE visual = 0, HANDLE colormap = 0 )" Create an application, given an already open display \fIdpy\fR and using \fIargc\fR command line arguments in \fIargv\fR. If \fIvisual\fR and \fIcolormap\fR are non-zero, the application will use those as the default Visual and Colormap contexts. .PP -\fBWarning:\fR Qt only supports TrueColor visuals at depths higher than 8 bits-per-pixel. +\fBWarning:\fR TQt only supports TrueColor visuals at depths higher than 8 bits-per-pixel. .PP This is available only on X11. .SH "QApplication::~QApplication ()\fC [virtual]\fR" Cleans up any window system resources that were allocated by this application. Sets the global variable \fCqApp\fR to 0. .SH "void QApplication::aboutTQt ()\fC [slot]\fR" -Displays a simple message box about Qt. The message includes the version number of Qt being used by the application. +Displays a simple message box about Qt. The message includes the version number of TQt being used by the application. .PP This is useful for inclusion in the Help menu of an application. See the examples/menu/menu.cpp example. .PP @@ -659,7 +659,7 @@ Example: network/mail/smtp.cpp. .SH "void QApplication::addLibraryPath ( const QString & path )\fC [static]\fR" Append \fIpath\fR to the end of the library path list. If \fIpath\fR is empty or already in the path list, the path list is not changed. .PP -The default path list consists of a single entry, the installation directory for plugins. The default installation directory for plugins is \fCINSTALL/plugins\fR, where \fCINSTALL\fR is the directory where Qt was installed. +The default path list consists of a single entry, the installation directory for plugins. The default installation directory for plugins is \fCINSTALL/plugins\fR, where \fCINSTALL\fR is the directory where TQt was installed. .PP See also removeLibraryPath(), libraryPaths(), and setLibraryPaths(). .SH "QWidgetList * QApplication::allWidgets ()\fC [static]\fR" @@ -701,7 +701,7 @@ See also topLevelWidgets(), QWidget::visible, and QPtrList::isEmpty(). .SH "QString QApplication::applicationDirPath ()" Returns the directory that contains the application executable. .PP -For example, if you have installed Qt in the \fCC:\Trolltech\Qt\fR directory, and you run the \fCdemo\fR example, this function will return "C:/Trolltech/Qt/examples/demo". +For example, if you have installed TQt in the \fCC:\Trolltech\Qt\fR directory, and you run the \fCdemo\fR example, this function will return "C:/Trolltech/Qt/examples/demo". .PP On Mac OS X this will point to the directory actually containing the executable, which may be inside of an application bundle (if the application is bundled). .PP @@ -711,7 +711,7 @@ See also applicationFilePath(). .SH "QString QApplication::applicationFilePath ()" Returns the file path of the application executable. .PP -For example, if you have installed Qt in the \fCC:\Trolltech\Qt\fR directory, and you run the \fCdemo\fR example, this function will return "C:/Trolltech/Qt/examples/demo/demo.exe". +For example, if you have installed TQt in the \fCC:\Trolltech\Qt\fR directory, and you run the \fCdemo\fR example, this function will return "C:/Trolltech/Qt/examples/demo/demo.exe". .PP \fBWarning:\fR On Unix, this function assumes that argv[0] contains the file name of the executable (which it normally does). It also assumes that the current directory hasn't been changed by the application. .PP @@ -730,7 +730,7 @@ Returns the command line argument vector. .PP \fCargv()[0]\fR is the program name, \fCargv()[1]\fR is the first argument and \fCargv()[argc()-1]\fR is the last argument. .PP -A QApplication object is constructed by passing \fIargc\fR and \fIargv\fR from the \fCmain()\fR function. Some of the arguments may be recognized as Qt options and removed from the argument vector. For example, the X11 version of Qt knows about \fC-display\fR, \fC-font\fR and a few more options. +A QApplication object is constructed by passing \fIargc\fR and \fIargv\fR from the \fCmain()\fR function. Some of the arguments may be recognized as TQt options and removed from the argument vector. For example, the X11 version of TQt knows about \fC-display\fR, \fC-font\fR and a few more options. .PP Example: .PP @@ -970,7 +970,7 @@ Example: i18n/main.cpp. .SH "bool QApplication::isEffectEnabled ( Qt::UIEffect effect )\fC [static]\fR" Returns TRUE if \fIeffect\fR is enabled; otherwise returns FALSE. .PP -By default, Qt will try to use the desktop settings. Call setDesktopSettingsAware(FALSE) to prevent this. +By default, TQt will try to use the desktop settings. Call setDesktopSettingsAware(FALSE) to prevent this. .PP Note: All effects are disabled on screens running at less than 16-bit color depth. .PP @@ -991,7 +991,7 @@ See also mainWidget(), topLevelWidgets(), QWidget::isTopLevel, and QWidget::clos Examples: .)l addressbook/main.cpp, extension/main.cpp, helpviewer/main.cpp, mdi/main.cpp, network/archivesearch/main.cpp, qwerty/main.cpp, and regexptester/main.cpp. .SH "QStringList QApplication::libraryPaths ()\fC [static]\fR" -Returns a list of paths that the application will search when dynamically loading libraries. The installation directory for plugins is the only entry if no paths have been set. The default installation directory for plugins is \fCINSTALL/plugins\fR, where \fCINSTALL\fR is the directory where Qt was installed. The directory of the application executable (NOT the working directory) is also added to the plugin paths. +Returns a list of paths that the application will search when dynamically loading libraries. The installation directory for plugins is the only entry if no paths have been set. The default installation directory for plugins is \fCINSTALL/plugins\fR, where \fCINSTALL\fR is the directory where TQt was installed. The directory of the application executable (NOT the working directory) is also added to the plugin paths. .PP If you want to iterate over the list, you should iterate over a copy, e.g. .PP @@ -1015,11 +1015,11 @@ See the plugins documentation for a description of how the library paths are use .PP See also setLibraryPaths(), addLibraryPath(), removeLibraryPath(), and QLibrary. .SH "void QApplication::lock ()" -Lock the Qt Library Mutex. If another thread has already locked the mutex, the calling thread will block until the other thread has unlocked the mutex. +Lock the TQt Library Mutex. If another thread has already locked the mutex, the calling thread will block until the other thread has unlocked the mutex. .PP See also unlock(), locked(), and Thread Support in Qt. .SH "bool QApplication::locked ()" -Returns TRUE if the Qt Library Mutex is locked by a different thread; otherwise returns FALSE. +Returns TRUE if the TQt Library Mutex is locked by a different thread; otherwise returns FALSE. .PP \fBWarning:\fR Due to different implementations of recursive mutexes on the supported platforms, calling this function from the same thread that previously locked the mutex will give undefined results. .PP @@ -1086,7 +1086,7 @@ Note that you are not limited to the public functions of QWidget. Instead, based .PP See also QStyle::polish(), QWidget::polish(), setPalette(), and setFont(). .SH "void QApplication::postEvent ( QObject * receiver, QEvent * event )\fC [static]\fR" -\fBNote:\fR This function is thread-safe when Qt is built withthread support.</p> Adds the event \fIevent\fR with the object \fIreceiver\fR as the receiver of the event, to an event queue and returns immediately. +\fBNote:\fR This function is thread-safe when TQt is built withthread support.</p> Adds the event \fIevent\fR with the object \fIreceiver\fR as the receiver of the event, to an event queue and returns immediately. .PP The event must be allocated on the heap since the post event queue will take ownership of the event and delete it once it has been posted. .PP @@ -1115,7 +1115,7 @@ See also exec(), QTimer, and QEventLoop::processEvents(). .PP Waits for an event to occur, processes it, then returns. .PP -This function is useful for adapting Qt to situations where the event processing must be grafted onto existing program loops. +This function is useful for adapting TQt to situations where the event processing must be grafted onto existing program loops. .PP Using this function in new applications may be an indication of design problems. .PP @@ -1170,7 +1170,7 @@ Removes \fIpath\fR from the library path list. If \fIpath\fR is empty or not in .PP See also addLibraryPath(), libraryPaths(), and setLibraryPaths(). .SH "void QApplication::removePostedEvents ( QObject * receiver )\fC [static]\fR" -\fBNote:\fR This function is thread-safe when Qt is built withthread support.</p> Removes all events posted using postEvent() for \fIreceiver\fR. +\fBNote:\fR This function is thread-safe when TQt is built withthread support.</p> Removes all events posted using postEvent() for \fIreceiver\fR. .PP The events are \fInot\fR dispatched, instead they are removed from the queue. You should never need to call this function. If you do call it, be aware that killing events may cause \fIreceiver\fR to break one or more invariants. .SH "void QApplication::removeTranslator ( QTranslator * mf )" @@ -1256,13 +1256,13 @@ The options are: .TP QApplication::NormalColor. This is the default color allocation strategy. Use this option if your application uses buttons, menus, texts and pixmaps with few colors. With this option, the application uses system global colors. This works fine for most applications under X11, but on Windows machines it may cause dithering of non-standard colors. .TP -QApplication::CustomColor. Use this option if your application needs a small number of custom colors. On X11, this option is the same as NormalColor. On Windows, Qt creates a Windows palette, and allocates colors to it on demand. +QApplication::CustomColor. Use this option if your application needs a small number of custom colors. On X11, this option is the same as NormalColor. On Windows, TQt creates a Windows palette, and allocates colors to it on demand. .TP QApplication::ManyColor. Use this option if your application is very color hungry (e.g. it requires thousands of colors). Under X11 the effect is: .TP For 256-color displays which have at best a 256 color true color visual, the default visual is used, and colors are allocated from a color cube. The color cube is the 6x6x6 (216 color) "Web palette"<sup>*</sup>, but the number of colors can be changed by the \fI-ncols\fR option. The user can force the application to use the true color visual with the -visual option. .TP -For 256-color displays which have a true color visual with more than 256 colors, use that visual. Silicon Graphics X servers have this feature, for example. They provide an 8 bit visual by default but can deliver true color when asked. On Windows, Qt creates a Windows palette, and fills it with a color cube. +For 256-color displays which have a true color visual with more than 256 colors, use that visual. Silicon Graphics X servers have this feature, for example. They provide an 8 bit visual by default but can deliver true color when asked. On Windows, TQt creates a Windows palette, and fills it with a color cube. .PP Be aware that the CustomColor and ManyColor choices may lead to colormap flashing: The foreground application gets (most) of the available colors, while the background windows will look less attractive. .PP @@ -1288,7 +1288,7 @@ QColor provides more functionality for controlling color allocation and freeing .PP To check what mode you end up with, call QColor::numBitPlanes() once the QApplication object exists. A value greater than 8 (typically 16, 24 or 32) means true color. .PP -<sup>*</sup> The color cube used by Qt has 216 colors whose red, green, and blue components always have one of the following values: 0x00, 0x33, 0x66, 0x99, 0xCC, or 0xFF. +<sup>*</sup> The color cube used by TQt has 216 colors whose red, green, and blue components always have one of the following values: 0x00, 0x33, 0x66, 0x99, 0xCC, or 0xFF. .PP See also colorSpec(), QColor::numBitPlanes(), and QColor::enterAllocContext(). .PP @@ -1305,7 +1305,7 @@ See also cursorFlashTime(). .PP This is the same as QTextCodec::setCodecForTr(). .SH "void QApplication::setDesktopSettingsAware ( bool on )\fC [static]\fR" -By default, Qt will try to use the current standard colors, fonts etc., from the underlying window system's desktop settings, and use them for all relevant widgets. This behavior can be switched off by calling this function with \fIon\fR set to FALSE. +By default, TQt will try to use the current standard colors, fonts etc., from the underlying window system's desktop settings, and use them for all relevant widgets. This behavior can be switched off by calling this function with \fIon\fR set to FALSE. .PP This static function must be called before creating the QApplication object, like this: .PP @@ -1583,7 +1583,7 @@ Example: .PP See also allWidgets(), QWidget::isTopLevel, QWidget::visible, and QPtrList::isEmpty(). .SH "QString QApplication::translate ( const char * context, const char * sourceText, const char * comment = 0, Encoding encoding = DefaultCodec ) const" -\fBNote:\fR This function is reentrant when Qt is built with thread support.</p> Returns the translation text for \fIsourceText\fR, by querying the installed messages files. The message files are searched from the most recently installed message file back to the first installed message file. +\fBNote:\fR This function is reentrant when TQt is built with thread support.</p> Returns the translation text for \fIsourceText\fR, by querying the installed messages files. The message files are searched from the most recently installed message file back to the first installed message file. .PP QObject::tr() and QObject::trUtf8() provide this functionality more conveniently. .PP @@ -1601,7 +1601,7 @@ This function is not virtual. You can use alternative translation techniques by .PP See also QObject::tr(), installTranslator(), and defaultCodec(). .SH "bool QApplication::tryLock ()" -Attempts to lock the Qt Library Mutex, and returns immediately. If the lock was obtained, this function returns TRUE. If another thread has locked the mutex, this function returns FALSE, instead of waiting for the lock to become available. +Attempts to lock the TQt Library Mutex, and returns immediately. If the lock was obtained, this function returns TRUE. If another thread has locked the mutex, this function returns FALSE, instead of waiting for the lock to become available. .PP The mutex must be unlocked with unlock() before another thread can successfully lock it. .PP @@ -1609,7 +1609,7 @@ See also lock(), unlock(), and Thread Support in Qt. .SH "Type QApplication::type () const" Returns the type of application, Tty, GuiClient or GuiServer. .SH "void QApplication::unlock ( bool wakeUpGui = TRUE )" -Unlock the Qt Library Mutex. If \fIwakeUpGui\fR is TRUE (the default), then the GUI thread will be woken with QApplication::wakeUpGuiThread(). +Unlock the TQt Library Mutex. If \fIwakeUpGui\fR is TRUE (the default), then the GUI thread will be woken with QApplication::wakeUpGuiThread(). .PP See also lock(), locked(), and Thread Support in Qt. .SH "void QApplication::wakeUpGuiThread ()" @@ -1621,7 +1621,7 @@ Returns the number of lines to scroll when the mouse wheel is rotated. .PP See also setWheelScrollLines(). .SH "QWidget * QApplication::widgetAt ( int x, int y, bool child = FALSE )\fC [static]\fR" -Returns a pointer to the widget at global screen position \fI(x, y)\fR, or 0 if there is no Qt widget there. +Returns a pointer to the widget at global screen position \fI(x, y)\fR, or 0 if there is no TQt widget there. .PP If \fIchild\fR is FALSE and there is a child widget at position \fI(x, y)\fR, the top-level widget containing it is returned. If \fIchild\fR is TRUE the child widget at position \fI(x, y)\fR is returned. .PP @@ -1631,7 +1631,7 @@ See also QCursor::pos(), QWidget::grabMouse(), and QWidget::grabKeyboard(). .SH "QWidget * QApplication::widgetAt ( const QPoint & pos, bool child = FALSE )\fC [static]\fR" This is an overloaded member function, provided for convenience. It behaves essentially like the above function. .PP -Returns a pointer to the widget at global screen position \fIpos\fR, or 0 if there is no Qt widget there. +Returns a pointer to the widget at global screen position \fIpos\fR, or 0 if there is no TQt widget there. .PP If \fIchild\fR is FALSE and there is a child widget at position \fIpos\fR, the top-level widget containing it is returned. If \fIchild\fR is TRUE the child widget at position \fIpos\fR is returned. .SH "bool QApplication::winEventFilter ( MSG * )\fC [virtual]\fR" @@ -1657,7 +1657,7 @@ Return TRUE if you want to stop the event from being processed. Return FALSE for .PP See also x11ProcessEvent(). .SH "int QApplication::x11ProcessEvent ( XEvent * event )" -This function does the core processing of individual X \fIevent\fRs, normally by dispatching Qt events to the right destination. +This function does the core processing of individual X \fIevent\fRs, normally by dispatching TQt events to the right destination. .PP It returns 1 if the event was consumed by special handling, 0 if the \fIevent\fR was consumed by normal handling, and -1 if the \fIevent\fR was for an unrecognized widget. .PP @@ -1854,9 +1854,9 @@ Under X11, the text is printed to stderr. Under Windows, the text is sent to the .PP 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. +Installs a TQt message handler \fIh\fR. Returns a pointer to the message handler previously defined. .PP -The message handler is a function that prints out debug messages, warnings and fatal error messages. The Qt library (debug version) contains hundreds of warning messages that are printed when internal errors (usually invalid function arguments) occur. If you implement your own message handler, you get total control of these messages. +The message handler is a function that prints out debug messages, warnings and fatal error messages. The TQt library (debug version) contains hundreds of warning messages that are printed when internal errors (usually invalid function arguments) occur. If you implement your own message handler, you get total control of these messages. .PP The default message handler prints the message to the standard output under X11 or to the debugger under Windows. If it is a fatal message, the application aborts immediately. .PP @@ -1930,11 +1930,11 @@ In debug mode, this function calls tqFatal() with a message if the computer is t .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. +This function does nothing when TQt is built with \fCQT_NO_DEBUG\fR defined. .SH "const char * tqVersion ()" -Returns the Qt version number as a string, for example, "2.3.0" or" 3.0.5". +Returns the TQt version number as a string, for example, "2.3.0" or" 3.0.5". .PP -The \fCTQT_VERSION\fR define has the numeric value in the form: 0xmmiibb (m = major, i = minor, b = bugfix). For example, Qt 3.0.5's \fCTQT_VERSION\fR is 0x030005. +The \fCTQT_VERSION\fR define has the numeric value in the form: 0xmmiibb (m = major, i = minor, b = bugfix). For example, TQt 3.0.5's \fCTQT_VERSION\fR is 0x030005. .SH "void tqWarning ( const char * msg, ... )" Prints a warning message \fImsg\fR, or calls the message handler (if it has been installed). .PP @@ -1978,8 +1978,8 @@ If you find a bug in Qt, please report it as described in .BR http://doc.trolltech.com/bughowto.html . Good bug reports help us to help you. Thank you. .P -The definitive Qt documentation is provided in HTML format; it is -located at $QTDIR/doc/html and can be read using Qt Assistant or with +The definitive TQt documentation is provided in HTML format; it is +located at $QTDIR/doc/html and can be read using TQt Assistant or with a web browser. This man page is provided as a convenience for those users who prefer man pages, although this format is not officially supported by Trolltech. |