@ -184,7 +184,7 @@ calls to their <a href="ntqaction.html#setVisible">QAction::setVisible<
<property>
<name>QAssistantClient::open</name>
<doc href="ntqassistantclient.html#open-prop">
<p>This property holds whether Qt Assistant is open.
<p>This property holds whether TQt Assistant is open.
<p>
<p>Get this property's value with <a href="ntqassistantclient.html#isOpen">isOpen</a>().
</doc>
@ -2967,7 +2967,7 @@ don't use a QProgressDialog inside a <a href="ntqwidget.html#paintEvent">p
<p>If this property is set to TRUE then the push button is the auto
default button in a dialog.
<p> In some GUI styles a default button is drawn with an extra frame
around it, up to 3 pixels or more. Qt automatically keeps this
around it, up to 3 pixels or more. TQt automatically keeps this
space free around auto-default buttons, i.e. auto-default buttons
may have a slightly larger size hint.
<p> This property's default is TRUE for buttons that have a <a href="ntqdialog.html">QDialog</a>
@ -3919,7 +3919,7 @@ such as <tt>*.html</tt> and <tt>*.txt</tt> with reasonab
<p>This property holds the enabled set of auto formatting features.
<p>The value can be any combination of the values in the <a href="ntqtextedit.html#AutoFormatting-enum">AutoFormatting</a> enum. The default is <a href="ntqtextedit.html#AutoFormatting-enum">AutoAll</a>. Choose <a href="ntqtextedit.html#AutoFormatting-enum">AutoNone</a>
to disable all automatic formatting.
<p> Currently, the only automatic formatting feature provided is <a href="ntqtextedit.html#AutoFormatting-enum">AutoBulletList</a>; future versions of Qt may offer more.
<p> Currently, the only automatic formatting feature provided is <a href="ntqtextedit.html#AutoFormatting-enum">AutoBulletList</a>; future versions of TQt may offer more.
<p>Set this property's value with <a href="ntqtextedit.html#setAutoFormatting">setAutoFormatting</a>() and get this property's value with <a href="ntqtextedit.html#autoFormatting">autoFormatting</a>().
</doc>
@ -4239,7 +4239,7 @@ pixmap. There is no default iconset.
<doc href="ntqtoolbutton.html#offIconSet-prop">
<p>This property holds the icon set that is used when the button is in an "off" state.
<p><b>This property is obsolete.</b> It is provided to keep old source working. We strongly advise against using it in new code.
<p> Since Qt 3.0, <a href="ntqiconset.html">QIconSet</a> contains both the On and Off icons. There is
<p> Since TQt 3.0, <a href="ntqiconset.html">QIconSet</a> contains both the On and Off icons. There is
now an <a href="ntqtoolbutton.html#iconSet-prop">QToolButton::iconSet</a> property that replaces both <a href="ntqtoolbutton.html#onIconSet-prop">QToolButton::onIconSet</a> and <a href="ntqtoolbutton.html#offIconSet-prop">QToolButton::offIconSet</a>.
<p> For ease of porting, this property is a synonym for <a href="ntqtoolbutton.html#iconSet-prop">QToolButton::iconSet</a>. You probably want to go over your application
code and use the QIconSet On/Off mechanism.
@ -4253,7 +4253,7 @@ code and use the QIconSet On/Off mechanism.
<doc href="ntqtoolbutton.html#onIconSet-prop">
<p>This property holds the icon set that is used when the button is in an "on" state.
<p><b>This property is obsolete.</b> It is provided to keep old source working. We strongly advise against using it in new code.
<p> Since Qt 3.0, <a href="ntqiconset.html">QIconSet</a> contains both the On and Off icons. There is
<p> Since TQt 3.0, <a href="ntqiconset.html">QIconSet</a> contains both the On and Off icons. There is
now an <a href="ntqtoolbutton.html#iconSet-prop">QToolButton::iconSet</a> property that replaces both <a href="ntqtoolbutton.html#onIconSet-prop">QToolButton::onIconSet</a> and <a href="ntqtoolbutton.html#offIconSet-prop">QToolButton::offIconSet</a>.
<p> For ease of porting, this property is a synonym for <a href="ntqtoolbutton.html#iconSet-prop">QToolButton::iconSet</a>. You probably want to go over your application
code and use the QIconSet On/Off mechanism.
@ -4661,7 +4661,7 @@ guaranteed to receive appropriate events before it is shown.
<p> The size component is adjusted if it lies outside the range
defined by <a href="ntqwidget.html#minimumSize">minimumSize</a>() and <a href="ntqwidget.html#maximumSize">maximumSize</a>().
<p> <a href="ntqwidget.html#setGeometry">setGeometry</a>() is virtual, and all other overloaded setGeometry()
implementations in Qt call it.
implementations in TQt call it.
<p> <b>Warning:</b> Calling setGeometry() inside resizeEvent() or moveEvent()
can lead to infinite recursion.
<p> See the <a href="geometry.html">Window Geometry documentation</a>
@ -4809,7 +4809,7 @@ specified by the <a href="ntqt.html#WidgetFlags-enum">WType_TopLevel</a
<p>This property is only relevant for top-level widgets.
<p> Note that due to limitations in some window-systems, this does not
always report the expected results (e.g. if the user on X11
maximizes the window via the window manager, Qt has no way of
maximizes the window via the window manager, TQt has no way of
distinguishing this from any other resize). This is expected to
improve as window manager protocols evolve.
<p> <p>See also <a href="ntqwidget.html#windowState">windowState</a>(), <a href="ntqwidget.html#showMaximized">showMaximized</a>(), <a href="ntqwidget.html#visible-prop">visible</a>, <a href="ntqwidget.html#show">show</a>(), <a href="ntqwidget.html#hide">hide</a>(), <a href="ntqwidget.html#showNormal">showNormal</a>(), and <a href="ntqwidget.html#minimized-prop">minimized</a>.
Returns the shortcut key sequence for \fIstr\fR, or an invalid key sequence (0) if \fIstr\fR has no shortcut sequence.
.PP
For example, shortcutKey("E&xit") returns ALT+Key_X, shortcutKey("&Quit") returns ALT+Key_Q and shortcutKey("Quit") returns 0. (In code that does not inherit the Qt namespace class, you must write e.g. Qt::ALT+Qt::Key_Q.)
For example, shortcutKey("E&xit") returns ALT+Key_X, shortcutKey("&Quit") returns ALT+Key_Q and shortcutKey("Quit") returns 0. (In code that does not inherit the TQt namespace class, you must write e.g. Qt::ALT+Qt::Key_Q.)
.PP
We provide a list of common accelerators in English. At the time of writing, Microsoft and Open Group do not appear to have issued equivalent recommendations for other languages.
.SH "QKeySequence QAccel::stringToKey ( const QString & s )\fC [static]\fR"
@ -312,8 +312,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
@ -48,7 +48,7 @@ The QAccessible class provides enums and static functions relating to accessibil
.PP
Accessibility clients use implementations of the QAccessibleInterface to read the information an accessible object exposes, or to call functions to manipulate the accessible object.
.PP
See the plugin documentation for more details about how to redistribute Qt plugins.
See the plugin documentation for more details about how to redistribute TQt plugins.
.PP
See also Miscellaneous Classes.
.SS "Member Type Documentation"
@ -387,8 +387,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
@ -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
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.
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.
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().
@ -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().
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.
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().
\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().
\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.
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().
\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.
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().
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.
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
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
@ -119,7 +119,7 @@ Items with duplicate keys can be inserted.
.PP
The parameter \fIp\fR is internal and should be left at the default value (0).
.PP
\fBWarning:\fR If this function returns FALSE, you must delete \fId\fR yourself. Additionally, be very careful about using \fId\fR after calling this function, because any other insertions into the cache, from anywhere in the application or within Qt itself, could cause the object to be discarded from the cache and the pointer to become invalid.
\fBWarning:\fR If this function returns FALSE, you must delete \fId\fR yourself. Additionally, be very careful about using \fId\fR after calling this function, because any other insertions into the cache, from anywhere in the application or within TQt itself, could cause the object to be discarded from the cache and the pointer to become invalid.
.SH "bool QAsciiCache::isEmpty () const"
Returns TRUE if the cache is empty; otherwise returns FALSE.
.SH "int QAsciiCache::maxCost () const"
@ -179,8 +179,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
QAssistantClient \- Means of using Qt Assistant as an application's help tool
QAssistantClient \- Means of using TQt Assistant as an application's help tool
.SH SYNOPSIS
\fC#include <ntqassistantclient.h>\fR
.PP
@ -55,21 +55,21 @@ Inherits QObject.
.SS "Properties"
.in +1c
.ti -1c
.BI "bool \fBopen\fR - whether Qt Assistant is open \fI(read " "only" ")\fR"
.BI "bool \fBopen\fR - whether TQt Assistant is open \fI(read " "only" ")\fR"
.br
.in -1c
.SH DESCRIPTION
The QAssistantClient class provides a means of using Qt Assistant as an application's help tool.
The QAssistantClient class provides a means of using TQt Assistant as an application's help tool.
.PP
Using Qt Assistant is simple: Create a QAssistantClient instance, then call showPage() as often as necessary to show your help pages. When you call showPage(), Qt Assistant will be launched if it isn't already running.
Using TQt Assistant is simple: Create a QAssistantClient instance, then call showPage() as often as necessary to show your help pages. When you call showPage(), TQt Assistant will be launched if it isn't already running.
.PP
The QAssistantClient instance can open (openAssistant()) or close (closeAssistant()) Qt Assistant whenever required. If Qt Assistant is open, isOpen() returns TRUE.
The QAssistantClient instance can open (openAssistant()) or close (closeAssistant()) TQt Assistant whenever required. If TQt Assistant is open, isOpen() returns TRUE.
.PP
One QAssistantClient instance interacts with one Qt Assistant instance, so every time you call openAssistant(), showPage() or closeAssistant() they are applied to the particular Qt Assistant instance associated with the QAssistantClient.
One QAssistantClient instance interacts with one TQt Assistant instance, so every time you call openAssistant(), showPage() or closeAssistant() they are applied to the particular TQt Assistant instance associated with the QAssistantClient.
.PP
When you call openAssistant() the assistantOpened() signal is emitted. Similarly when closeAssistant() is called, assistantClosed() is emitted. In either case, if an error occurs, error() is emitted.
.PP
This class is not included in the Qt library itself. To use it you must link against \fClibtqassistantclient.a\fR (Unix) or \fCqassistantclient.lib\fR (Windows), which is built into \fCINSTALL/lib\fR if you built the Qt tools (\fCINSTALL\fR is the directory where Qt is installed). If you use qmake, then you can simply add the following line to your pro file:
This class is not included in the TQt library itself. To use it you must link against \fClibtqassistantclient.a\fR (Unix) or \fCqassistantclient.lib\fR (Windows), which is built into \fCINSTALL/lib\fR if you built the TQt tools (\fCINSTALL\fR is the directory where TQt is installed). If you use qmake, then you can simply add the following line to your pro file:
.PP
.nf
.br
@ -77,43 +77,43 @@ This class is not included in the Qt library itself. To use it you must link aga
.br
.fi
.PP
See also "Adding Documentation to Qt Assistant" in the Qt Assistant manual.
See also "Adding Documentation to TQt Assistant" in the TQt Assistant manual.
Constructs an assistant client object. The \fIpath\fR specifies the path to the Qt Assistant executable. If \fIpath\fR is an empty string the system path (\fC%PATH%\fR or \fC$PATH\fR) is used.
Constructs an assistant client object. The \fIpath\fR specifies the path to the TQt Assistant executable. If \fIpath\fR is an empty string the system path (\fC%PATH%\fR or \fC$PATH\fR) is used.
.PP
The assistant client object is a child of \fIparent\fR and is called \fIname\fR.
.SH "QAssistantClient::~QAssistantClient ()"
Destroys the assistant client object and frees up all allocated resources.
This signal is emitted when the connection to Qt Assistant is closed. This happens when the user exits Qt Assistant, or when an error in the server or client occurs, or if closeAssistant() is called.
This signal is emitted when the connection to TQt Assistant is closed. This happens when the user exits TQt Assistant, or when an error in the server or client occurs, or if closeAssistant() is called.
This signal is emitted if Qt Assistant cannot be started or if an error occurs during the initialization of the connection between Qt Assistant and the calling application. The \fImsg\fR provides an explanation of the error.
This signal is emitted if TQt Assistant cannot be started or if an error occurs during the initialization of the connection between TQt Assistant and the calling application. The \fImsg\fR provides an explanation of the error.
.SH "bool QAssistantClient::isOpen () const"
Returns TRUE if Qt Assistant is open; otherwise returns FALSE. See the "open" property for details.
Returns TRUE if TQt Assistant is open; otherwise returns FALSE. See the "open" property for details.
This function opens Qt Assistant and sets up the client-server communiction between the application and Qt Assistant. If it is already open, this function does nothing. If an error occurs, error() is emitted.
This function opens TQt Assistant and sets up the client-server communiction between the application and TQt Assistant. If it is already open, this function does nothing. If an error occurs, error() is emitted.
Call this function to make Qt Assistant show a particular \fIpage\fR. The \fIpage\fR is a filename (e.g. \fCmyhelpfile.html\fR). See "Adding Documentation to Qt Assistant" in the Qt Assistant manual for further information.
Call this function to make TQt Assistant show a particular \fIpage\fR. The \fIpage\fR is a filename (e.g. \fCmyhelpfile.html\fR). See "Adding Documentation to TQt Assistant" in the TQt Assistant manual for further information.
.PP
If Qt Assistant hasn't been opened yet, this function will do nothing. You can use isOpen() to determine whether Qt Assistant is up and running, or you can connect to the asssistantOpened() signal.
If TQt Assistant hasn't been opened yet, this function will do nothing. You can use isOpen() to determine whether TQt Assistant is up and running, or you can connect to the asssistantOpened() signal.
.PP
See also open and assistantOpened().
.PP
Example: helpsystem/mainwindow.cpp.
.SS "Property Documentation"
.SH "bool open"
This property holds whether Qt Assistant is open.
This property holds whether TQt Assistant is open.
.PP
Get this property's value with isOpen().
@ -131,8 +131,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
@ -32,7 +32,7 @@ This class is part of the \fBQt ActiveQt Extension\fR.
.br
.in -1c
.SH DESCRIPTION
This class is defined in the \fBQt ActiveQt Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main Qt API.
This class is defined in the \fBQt ActiveQt Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main TQt API.
.PP
The QAxAggregated class is an abstract base class for implementations of additional COM interfaces.
.PP
@ -131,8 +131,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
@ -112,11 +112,11 @@ Inherited by QAxObject and QAxWidget.
.br
.in -1c
.SH DESCRIPTION
This class is defined in the \fBQt ActiveQt Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main Qt API.
This class is defined in the \fBQt ActiveQt Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main TQt API.
.PP
The QAxBase class is an abstract class that provides an API to initalize and access a COM object.
.PP
QAxBase is an abstract class that cannot be used directly, and is instantiated through the subclasses QAxObject and QAxWidget. This class provides the API to access the COM object directly through its IUnknown implementation. If the COM object implements the IDispatch interface, the properties and methods of that object become available as Qt properties and slots.
QAxBase is an abstract class that cannot be used directly, and is instantiated through the subclasses QAxObject and QAxWidget. This class provides the API to access the COM object directly through its IUnknown implementation. If the COM object implements the IDispatch interface, the properties and methods of that object become available as TQt properties and slots.
.PP
.nf
.br
@ -124,7 +124,7 @@ QAxBase is an abstract class that cannot be used directly, and is instantiated t
.br
.fi
.PP
Properties exposed by the object's IDispatch implementation can be read and written through the property system provided by the Qt Object Model (both subclasses are QObjects, so you can use setProperty() and property() as with QObject). Properties with multiple parameters are not supported.
Properties exposed by the object's IDispatch implementation can be read and written through the property system provided by the TQt Object Model (both subclasses are QObjects, so you can use setProperty() and property() as with QObject). Properties with multiple parameters are not supported.
.PP
.nf
.br
@ -142,7 +142,7 @@ Write-functions for properties and other methods exposed by the object's IDispat
.br
.fi
.PP
Outgoing events supported by the COM object are emitted as standard Qt signals.
Outgoing events supported by the COM object are emitted as standard TQt signals.
.PP
.nf
.br
@ -152,11 +152,11 @@ Outgoing events supported by the COM object are emitted as standard Qt signals.
.br
.fi
.PP
QAxBase transparently converts between COM data types and the equivalent Qt data types. Some COM types have no equivalent Qt data structure.
QAxBase transparently converts between COM data types and the equivalent TQt data types. Some COM types have no equivalent TQt data structure.
.PP
Supported COM datatypes are listed in the first column of following table. The second column is the Qt type that can be used with the QObject property functions. The third column is the Qt type that is used in the prototype of generated signals and slots for in-parameters, and the last column is the Qt type that is used in the prototype of signals and slots for out-parameters. <center>.nf
Supported COM datatypes are listed in the first column of following table. The second column is the TQt type that can be used with the QObject property functions. The third column is the TQt type that is used in the prototype of generated signals and slots for in-parameters, and the last column is the TQt type that is used in the prototype of signals and slots for out-parameters. <center>.nf
@ -273,7 +273,7 @@ Some ActiveX controls might be unstable when connected to an event sink. To get
.PP
Note that this function should be called immediately after construction of the object (without passing an object identifier), and before calling QAxWidget->setControl().
.SH "void QAxBase::disableMetaObject ()"
Disables the meta object generation for this ActiveX container. This also disables the event sink and class info generation. If you don't intend to use the Qt meta object implementation call this function to speed up the meta object generation.
Disables the meta object generation for this ActiveX container. This also disables the event sink and class info generation. If you don't intend to use the TQt meta object implementation call this function to speed up the meta object generation.
.PP
Some ActiveX controls might be unstable when used with OLE automation. Use standard COM methods to use those controls through the COM interfaces provided by queryInterface().
.PP
@ -549,8 +549,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
@ -44,7 +44,7 @@ This class is part of the \fBQt ActiveQt Extension\fR.
.br
.in -1c
.SH DESCRIPTION
This class is defined in the \fBQt ActiveQt Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main Qt API.
This class is defined in the \fBQt ActiveQt Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main TQt API.
.PP
The QAxBindable class provides an interface between a QWidget and an ActiveX client.
.PP
@ -140,8 +140,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
@ -95,7 +95,7 @@ This class is part of the \fBQt ActiveQt Extension\fR.
.br
.in -1c
.SH DESCRIPTION
This class is defined in the \fBQt ActiveQt Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main Qt API.
This class is defined in the \fBQt ActiveQt Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main TQt API.
.PP
The QAxFactory class defines a factory for the creation of COM components.
.PP
@ -424,8 +424,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
This class is defined in the \fBQt ActiveQt Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main Qt API.
This class is defined in the \fBQt ActiveQt Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main TQt API.
.PP
The QAxObject class provides a QObject that wraps a COM object.
.PP
A QAxObject can be instantiated as an empty object, with the name of the COM object it should wrap, or with a pointer to the IUnknown that represents an existing COM object. If the COM object implements the IDispatch interface, the properties, methods and events of that object become available as Qt properties, slots and signals. The base class, QAxBase, provides an API to access the COM object directly through the IUnknown pointer.
A QAxObject can be instantiated as an empty object, with the name of the COM object it should wrap, or with a pointer to the IUnknown that represents an existing COM object. If the COM object implements the IDispatch interface, the properties, methods and events of that object become available as TQt properties, slots and signals. The base class, QAxBase, provides an API to access the COM object directly through the IUnknown pointer.
.PP
QAxObject is a QObject and can be used as such, e.g. it can be organized in an object hierarchy, receive events and connect to signals and slots.
.PP
@ -171,8 +171,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
This class is defined in the \fBQt ActiveQt Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main Qt API.
This class is defined in the \fBQt ActiveQt Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main TQt API.
.PP
The QAxScript class provides a wrapper around script code.
.PP
@ -157,8 +157,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
This class is defined in the \fBQt ActiveQt Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main Qt API.
This class is defined in the \fBQt ActiveQt Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main TQt API.
.PP
The QAxScriptEngine class provides a wrapper around a script engine.
.PP
@ -111,8 +111,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
This class is defined in the \fBQt ActiveQt Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main Qt API.
This class is defined in the \fBQt ActiveQt Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main TQt API.
.PP
The QAxScriptManager class provides a bridge between application objects and script code.
.PP
The QAxScriptManager acts as a bridge between the COM objects embedded in the Qt application through QAxObject or QAxWidget, and the scripting languages available through the Windows Script technologies, usually JScript and VBScript.
The QAxScriptManager acts as a bridge between the COM objects embedded in the TQt application through QAxObject or QAxWidget, and the scripting languages available through the Windows Script technologies, usually JScript and VBScript.
.PP
Create one QAxScriptManager for each separate document in your application, and add the COM objects the scripts need to access using addObject(). Then load() the script sources and invoke the functions using call().
.PP
@ -185,8 +185,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
This class is defined in the \fBQt ActiveQt Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main Qt API.
This class is defined in the \fBQt ActiveQt Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main TQt API.
.PP
The QAxWidget class is a QWidget that wraps an ActiveX control.
.PP
A QAxWidget can be instantiated as an empty object, with the name of the ActiveX control it should wrap, or with an existing interface pointer to the ActiveX control. The ActiveX control's properties, methods and events which only use supported data types, become available as Qt properties, slots and signals. The base class QAxBase provides an API to access the ActiveX directly through the IUnknown pointer.
A QAxWidget can be instantiated as an empty object, with the name of the ActiveX control it should wrap, or with an existing interface pointer to the ActiveX control. The ActiveX control's properties, methods and events which only use supported data types, become available as TQt properties, slots and signals. The base class QAxBase provides an API to access the ActiveX directly through the IUnknown pointer.
.PP
QAxWidget is a QWidget and can be used as such, e.g. it can be organized in a widget hierarchy, receive events or act as an event filter. Standard widget properties, e.g. enabled are supported, but it depends on the ActiveX control to implement support for ambient properties like e.g. palette or font. QAxWidget tries to provide the necessary hints.
.PP
@ -203,8 +203,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
The QBig5Codec class provides conversion to and from the Big5 encoding.
.PP
QBig5Codec was originally contributed by Ming-Che Chuang <mingche@cobra.ee.ntu.edu.tw> for the Big-5+ encoding, and was included in Qt with the author's permission, and the grateful thanks of the Trolltech team. (Note: Ming-Che's code is QPL'd, as per an mail to info@trolltech.com.)
QBig5Codec was originally contributed by Ming-Che Chuang <mingche@cobra.ee.ntu.edu.tw> for the Big-5+ encoding, and was included in TQt with the author's permission, and the grateful thanks of the Trolltech team. (Note: Ming-Che's code is QPL'd, as per an mail to info@trolltech.com.)
.PP
However, since Big-5+ was never formally approved, and was never used by anyone, the Taiwan Free Software community and the Li18nux Big5 Standard Subgroup agree that the de-facto standard Big5-ETen (zh_TW.Big5 or zh_TW.TW-Big5) be used instead.
.PP
@ -50,8 +50,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
The QBig5hkscsCodec class provides conversion to and from the Big5-HKSCS encoding.
.PP
QBig5hkscsCodec grew out of the QBig5Codec originally contributed by Ming-Che Chuang <mingche@cobra.ee.ntu.edu.tw>. James Su <suzhe@turbolinux.com.cn> <suzhe@gnuchina.org> and Anthony Fok <anthony@thizlinux.com> <foka@debian.org> implemented HKSCS-1999 QBig5hkscsCodec for Qt-2.3.x, but it was too late in Qt development schedule to be officially included in the Qt-2.3.x series.
QBig5hkscsCodec grew out of the QBig5Codec originally contributed by Ming-Che Chuang <mingche@cobra.ee.ntu.edu.tw>. James Su <suzhe@turbolinux.com.cn> <suzhe@gnuchina.org> and Anthony Fok <anthony@thizlinux.com> <foka@debian.org> implemented HKSCS-1999 QBig5hkscsCodec for Qt-2.3.x, but it was too late in TQt development schedule to be officially included in the Qt-2.3.x series.
.PP
Wu Yi <wuyi@hancom.com> ported the HKSCS-1999 QBig5hkscsCodec to Qt-3.0.1 in March 2002.
.PP
@ -66,8 +66,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
@ -239,7 +239,7 @@ If the stretch factor is 0 and nothing else in the QBoxLayout has a stretch fact
.PP
Alignment is specified by \fIalignment\fR which is a bitwise OR of Qt::AlignmentFlags values. The default alignment is 0, which means that the widget fills the entire cell.
.PP
From Qt 3.0, the \fIalignment\fR parameter is interpreted more aggressively than in previous versions of Qt. A non-default alignment now indicates that the widget should not grow to fill the available space, but should be sized according to sizeHint().
From TQt 3.0, the \fIalignment\fR parameter is interpreted more aggressively than in previous versions of Qt. A non-default alignment now indicates that the widget should not grow to fill the available space, but should be sized according to sizeHint().
.PP
See also insertWidget(), setAutoAdd(), addLayout(), and addSpacing().
.PP
@ -296,7 +296,7 @@ If the stretch factor is 0 and nothing else in the QBoxLayout has a stretch fact
.PP
Alignment is specified by \fIalignment\fR, which is a bitwise OR of Qt::AlignmentFlags values. The default alignment is 0, which means that the widget fills the entire cell.
.PP
From Qt 3.0, the \fIalignment\fR parameter is interpreted more aggressively than in previous versions of Qt. A non-default alignment now indicates that the widget should not grow to fill the available space, but should be sized according to sizeHint().
From TQt 3.0, the \fIalignment\fR parameter is interpreted more aggressively than in previous versions of Qt. A non-default alignment now indicates that the widget should not grow to fill the available space, but should be sized according to sizeHint().
.PP
See also setAutoAdd(), insertLayout(), and insertSpacing().
@ -233,7 +233,7 @@ You can also set a custom accelerator using the setAccel() function. This is use
.br
.fi
.PP
All of the buttons provided by Qt (QPushButton, QToolButton, QCheckBox and QRadioButton) can display both text and pixmaps.
All of the buttons provided by TQt (QPushButton, QToolButton, QCheckBox and QRadioButton) can display both text and pixmaps.
.PP
To subclass QButton, you must reimplement at least drawButton() (to draw the button's outline) and drawButtonLabel() (to draw its text or pixmap). It is generally advisable to reimplement sizeHint() as well, and sometimes hitButton() (to determine whether a button press is within the button).
.PP
@ -478,8 +478,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
@ -130,7 +130,7 @@ The cache's size is limited, and if the total cost is too high, QCache will remo
.PP
The parameter \fIp\fR is internal and should be left at the default value (0).
.PP
\fBWarning:\fR If this function returns FALSE (which could happen, e.g. if the cost of this item alone exceeds maxCost()) you must delete \fId\fR yourself. Additionally, be very careful about using \fId\fR after calling this function because any other insertions into the cache, from anywhere in the application or within Qt itself, could cause the object to be discarded from the cache and the pointer to become invalid.
\fBWarning:\fR If this function returns FALSE (which could happen, e.g. if the cost of this item alone exceeds maxCost()) you must delete \fId\fR yourself. Additionally, be very careful about using \fId\fR after calling this function because any other insertions into the cache, from anywhere in the application or within TQt itself, could cause the object to be discarded from the cache and the pointer to become invalid.
.SH "bool QCache::isEmpty () const"
Returns TRUE if the cache is empty; otherwise returns FALSE.
.SH "int QCache::maxCost () const"
@ -203,8 +203,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
Moves all QCanvasItem::animated() canvas items on the canvas and refreshes all changes to all views of the canvas. (An `animated' item is an item that is in motion; see setVelocity().)
.PP
The advance takes place in two phases. In phase 0, the QCanvasItem::advance() function of each QCanvasItem::animated() canvas item is called with paramater 0. Then all these canvas items are called again, with parameter 1. In phase 0, the canvas items should not change position, merely examine other items on the canvas for which special processing is required, such as collisions between items. In phase 1, all canvas items should change positions, ignoring any other items on the canvas. This two-phase approach allows for considerations of "fairness", although no QCanvasItem subclasses supplied with Qt do anything interesting in phase 0.
The advance takes place in two phases. In phase 0, the QCanvasItem::advance() function of each QCanvasItem::animated() canvas item is called with paramater 0. Then all these canvas items are called again, with parameter 1. In phase 0, the canvas items should not change position, merely examine other items on the canvas for which special processing is required, such as collisions between items. In phase 1, all canvas items should change positions, ignoring any other items on the canvas. This two-phase approach allows for considerations of "fairness", although no QCanvasItem subclasses supplied with TQt do anything interesting in phase 0.
.PP
The canvas can be configured to call this function periodically with setAdvancePeriod().
.PP
@ -445,8 +445,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
@ -168,7 +168,7 @@ QCanvasItem provides the show() and isVisible() functions like those in QWidget.
.PP
QCanvasItem also provides the setEnabled(), setActive() and setSelected() functions; these functions set the relevant boolean and cause a repaint but the boolean values they set are not used in QCanvasItem itself. You can make use of these booleans in your subclasses.
.PP
By default, canvas items have no velocity, no size, and are not in motion. The subclasses provided in Qt do not change these defaults except where noted.
By default, canvas items have no velocity, no size, and are not in motion. The subclasses provided in TQt do not change these defaults except where noted.
.PP
See also Graphics Classes and Image Processing Classes.
.SS "Member Type Documentation"
@ -414,8 +414,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
Almost all the functions in this class are reentrant when Qt is built with thread support. The exception is \fBdecomposition\fR(). </p>
Almost all the functions in this class are reentrant when TQt is built with thread support. The exception is \fBdecomposition\fR(). </p>
.PP
\fC#include <ntqstring.h>\fR
.PP
@ -215,7 +215,7 @@ QChar further provides direction(), which indicates the "natural" writing direct
.PP
Composed Unicode characters (like å) can be converted to decomposed Unicode ("a" followed by "ring above") by using decomposition().
.PP
In Unicode, comparison is not necessarily possible and case conversion is very difficult at best. Unicode, covering the" entire" world, also includes most of the world's case and sorting problems. Qt tries, but not very hard: operator==() and friends will do comparison based purely on the numeric Unicode value (code point) of the characters, and upper() and lower() will do case changes when the character has a well-defined upper/lower-case equivalent. There is no provision for locale-dependent case folding rules or comparison; these functions are meant to be fast so they can be used unambiguously in data structures. (See QString::localeAwareCompare() though.)
In Unicode, comparison is not necessarily possible and case conversion is very difficult at best. Unicode, covering the" entire" world, also includes most of the world's case and sorting problems. TQt tries, but not very hard: operator==() and friends will do comparison based purely on the numeric Unicode value (code point) of the characters, and upper() and lower() will do case changes when the character has a well-defined upper/lower-case equivalent. There is no provision for locale-dependent case folding rules or comparison; these functions are meant to be fast so they can be used unambiguously in data structures. (See QString::localeAwareCompare() though.)
.PP
The conversion functions include unicode() (to a scalar), latin1() (to scalar, but converts all non-Latin-1 characters to 0), row() (gives the Unicode row), cell() (gives the Unicode cell), digitValue() (gives the integer value of any of the numerous digit characters), and a host of constructors.
.PP
@ -292,7 +292,7 @@ The following categories are informative in Unicode:
.PP
There are two categories that are specific to Qt:
.TP
\fCQChar::NoCategory\fR - used when Qt is dazed and confused and cannot make sense of anything.
\fCQChar::NoCategory\fR - used when TQt is dazed and confused and cannot make sense of anything.
.TP
\fCQChar::Punctuation_Dask\fR - old typo alias for Punctuation_Dash
.SH "QChar::CombiningClass"
@ -333,7 +333,7 @@ Returns the cell (least significant byte) of the Unicode character.
Returns the combining class for the character as defined in the Unicode standard. This is mainly useful as a positioning hint for marks attached to a base character.
.PP
The Qt text rendering engine uses this information to correctly position non spacing marks around a base character.
The TQt text rendering engine uses this information to correctly position non spacing marks around a base character.
@ -35,7 +35,7 @@ Close events are sent to widgets that the user wants to close, usually by choosi
.PP
Close events contain a flag that indicates whether the receiver wants the widget to be closed or not. When a widget accepts the close event, it is hidden (and destroyed if it was created with the WDestructiveClose flag). If it refuses to accept the close event nothing happens. (Under X11 it is possible that the window manager will forcibly close the window; but at the time of writing we are not aware of any window manager that does this.)
.PP
The application's main widget -- QApplication::mainWidget() -- is a special case. When it accepts the close event, Qt leaves the main event loop and the application is immediately terminated (i.e. it returns from the call to QApplication::exec() in the main() function).
The application's main widget -- QApplication::mainWidget() -- is a special case. When it accepts the close event, TQt leaves the main event loop and the application is immediately terminated (i.e. it returns from the call to QApplication::exec() in the main() function).
.PP
The event handler QWidget::closeEvent() receives close events. The default implementation of this event handler accepts the close event. If you do not want your widget to be hidden, or want some special handing, you should reimplement the event handler.
.PP
@ -98,8 +98,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
@ -179,7 +179,7 @@ In addition to the RGB value, a QColor also has a pixel value and a validity. Th
.PP
The validity (isValid()) indicates whether the color is legal at all. For example, a RGB color with RGB values out of range is illegal. For performance reasons, QColor mostly disregards illegal colors. The result of using an invalid color is unspecified and will usually be surprising.
.PP
There are 19 predefined QColor objects: \fCwhite\fR, \fCblack\fR, \fCred\fR, \fCdarkRed\fR, \fCgreen\fR, \fCdarkGreen\fR, \fCblue\fR, \fCdarkBlue\fR, \fCcyan\fR, \fCdarkCyan\fR, \fCmagenta\fR, \fCdarkMagenta\fR, \fCyellow\fR, \fCdarkYellow\fR, \fCgray\fR, \fCdarkGray\fR, \fClightGray\fR, \fCcolor0\fR and \fCcolor1\fR, accessible as members of the Qt namespace (ie. \fCQt::red\fR).
There are 19 predefined QColor objects: \fCwhite\fR, \fCblack\fR, \fCred\fR, \fCdarkRed\fR, \fCgreen\fR, \fCdarkGreen\fR, \fCblue\fR, \fCdarkBlue\fR, \fCcyan\fR, \fCdarkCyan\fR, \fCmagenta\fR, \fCdarkMagenta\fR, \fCyellow\fR, \fCdarkYellow\fR, \fCgray\fR, \fCdarkGray\fR, \fClightGray\fR, \fCcolor0\fR and \fCcolor1\fR, accessible as members of the TQt namespace (ie. \fCQt::red\fR).
.PP
<center>
.ce 1
@ -225,7 +225,7 @@ V, for value, is 0-255 and represents lightness or brightness of the color. 0 is
.PP
Here are some examples: Pure red is H=0, S=255, V=255. A dark red, moving slightly towards the magenta, could be H=350 (equivalent to -10), S=255, V=180. A grayish light red could have H about 0 (say 350-359 or 0-10), S about 50-100, and S=255.
.PP
Qt returns a hue value of -1 for achromatic colors. If you pass a too-big hue value, Qt forces it into range. Hue 360 or 720 is treated as 0; hue 540 is treated as 180.
Qt returns a hue value of -1 for achromatic colors. If you pass a too-big hue value, TQt forces it into range. Hue 360 or 720 is treated as 0; hue 540 is treated as 180.
.PP
See also QPalette, QColorGroup, QApplication::setColorSpec(), Color FAQ, Widget Appearance and Style, Graphics Classes, and Image Processing Classes.
.SS "Member Type Documentation"
@ -289,7 +289,7 @@ Internal clean up required for QColor. This function is called from the QApplica
The example code loads a pixmap from file. It frees up all colors that were allocated the last time loadPixmap() was called.
.PP
The initial/default context is 0. Qt keeps a list of colors associated with their allocation contexts. You can call destroyAllocContext() to get rid of all colors that were allocated in a specific context.
The initial/default context is 0. TQt keeps a list of colors associated with their allocation contexts. You can call destroyAllocContext() to get rid of all colors that were allocated in a specific context.
.PP
Calling enterAllocContext() enters an allocation context. The allocation context lasts until you call leaveAllocContext(). QColor has an internal stack of allocation contexts. Each call to enterAllocContex() must have a corresponding leaveAllocContext().
.PP
@ -580,8 +580,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
@ -111,7 +111,7 @@ To set or get the position of the mouse cursor use the static methods QCursor::p
.PP
See also QWidget, GUI Design Handbook: Cursors, Widget Appearance and Style, and Implicitly and Explicitly Shared Classes.
.PP
On X11, Qt supports the Xcursor library, which allows for full color icon themes. The table below shows the cursor name used for each Qt::CursorShape value. If a cursor cannot be found using the name shown below, a standard X11 cursor will be used instead. Note: X11 does not provide appropriate cursors for all possible Qt::CursorShape values. It is possible that some cursors will be taken from the Xcursor theme, while others will use an internal bitmap cursor.
On X11, TQt supports the Xcursor library, which allows for full color icon themes. The table below shows the cursor name used for each Qt::CursorShape value. If a cursor cannot be found using the name shown below, a standard X11 cursor will be used instead. Note: X11 does not provide appropriate cursors for all possible Qt::CursorShape values. It is possible that some cursors will be taken from the Xcursor theme, while others will use an internal bitmap cursor.
.PP
<center>.nf
.TS
@ -145,7 +145,7 @@ B=0 and M=0 gives transparent.
.TP
B=1 and M=0 gives an undefined result.
.PP
Use the global Qt color \fCcolor0\fR to draw 0-pixels and \fCcolor1\fR to draw 1-pixels in the bitmaps.
Use the global TQt color \fCcolor0\fR to draw 0-pixels and \fCcolor1\fR to draw 1-pixels in the bitmaps.
.PP
Valid cursor sizes depend on the display hardware (or the underlying window system). We recommend using 32x32 cursors, because this size is supported on all platforms. Some platforms also support 16x16, 48x48 and 64x64 cursors.
.PP
@ -241,8 +241,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
QDataStream \- Serialization of binary data to a QIODevice
.SH SYNOPSIS
All the functions in this class are reentrant when Qt is built with thread support.</p>
All the functions in this class are reentrant when TQt is built with thread support.</p>
.PP
\fC#include <ntqdatastream.h>\fR
.PP
@ -199,15 +199,15 @@ Example (read binary data from a stream):
.br
.fi
.PP
Each item written to the stream is written in a predefined binary format that varies depending on the item's type. Supported Qt types include QBrush, QColor, QDateTime, QFont, QPixmap, QString, QVariant and many others. For the complete list of all Qt types supporting data streaming see the Format of the QDataStream operators.
Each item written to the stream is written in a predefined binary format that varies depending on the item's type. Supported TQt types include QBrush, QColor, QDateTime, QFont, QPixmap, QString, QVariant and many others. For the complete list of all TQt types supporting data streaming see the Format of the QDataStream operators.
.PP
For integers it is best to always cast to a Qt integer type for writing, and to read back into the same Qt integer type. This ensures that you get integers of the size you want and insulates you from compiler and platform differences.
For integers it is best to always cast to a TQt integer type for writing, and to read back into the same TQt integer type. This ensures that you get integers of the size you want and insulates you from compiler and platform differences.
.PP
To take one example, a \fCchar*\fR string is written as a 32-bit integer equal to the length of the string including the NUL byte ('\0'), followed by all the characters of the string including the NUL byte. When reading a \fCchar*\fR string, 4 bytes are read to create the 32-bit length value, then that many characters for the \fCchar*\fR string including the NUL are read.
.PP
The initial IODevice is usually set in the constructor, but can be changed with setDevice(). If you've reached the end of the data (or if there is no IODevice set) atEnd() will return TRUE.
.PP
If you want the data to be compatible with an earlier version of Qt use setVersion().
If you want the data to be compatible with an earlier version of TQt use setVersion().
.PP
If you want the data to be human-readable, e.g. for debugging, you can set the data stream into printable data mode with setPrintableData(). The data is then written slower, in a bloated but human readable format.
.PP
@ -508,11 +508,11 @@ Sets the version number of the data serialization format to \fIv\fR.
.PP
You don't need to set a version if you are using the current version of Qt.
.PP
In order to accommodate new functionality, the datastream serialization format of some Qt classes has changed in some versions of Qt. If you want to read data that was created by an earlier version of Qt, or write data that can be read by a program that was compiled with an earlier version of Qt, use this function to modify the serialization format of QDataStream.
In order to accommodate new functionality, the datastream serialization format of some TQt classes has changed in some versions of Qt. If you want to read data that was created by an earlier version of Qt, or write data that can be read by a program that was compiled with an earlier version of Qt, use this function to modify the serialization format of QDataStream.
.PP
<center>.nf
.TS
l - l. Qt Version QDataStream Version Qt 3.3 6 Qt 3.2 5 Qt 3.1 5 Qt 3.0 4 Qt 2.1.x and Qt 2.2.x 3 Qt 2.0.x 2 Qt 1.x
l - l. TQt Version QDataStream Version TQt 3.3 6 TQt 3.2 5 TQt 3.1 5 TQt 3.0 4 TQt 2.1.x and TQt 2.2.x 3 TQt 2.0.x 2 TQt 1.x
.TE
.fi
</center>
@ -523,7 +523,7 @@ Unsets the IO device. This is the same as calling setDevice( 0 ).
.PP
See also device() and setDevice().
.SH "int QDataStream::version () const"
Returns the version number of the data serialization format. In Qt 3.1, this number is 5.
Returns the version number of the data serialization format. In TQt 3.1, this number is 5.
All the functions in this class are reentrant when Qt is built with thread support.</p>
All the functions in this class are reentrant when TQt is built with thread support.</p>
.PP
\fC#include <ntqdatetime.h>\fR
.PP
@ -153,7 +153,7 @@ The daysInMonth() and daysInYear() functions return how many days there are in t
.PP
Note that QDate should not be used for date calculations for dates prior to the introduction of the Gregorian calendar. This calendar was adopted by England from the 14<sup><small>th</small></sup> September 1752 (hence this is the earliest valid QDate), and subsequently by most other Western countries, until 1923.
.PP
The end of time is reached around the year 8000, by which time we expect Qt to be obsolete.
The end of time is reached around the year 8000, by which time we expect TQt to be obsolete.
.PP
See also QTime, QDateTime, QDateEdit, QDateTimeEdit, and Time and Date.
.SH MEMBER FUNCTION DOCUMENTATION
@ -417,8 +417,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
@ -71,7 +71,7 @@ Systems with more than one graphics card and monitor can manage the physical scr
.PP
The QDesktopWidget provides information about the geometry of the available screens with screenGeometry(). The number of screens available is returned by numScreens(). The screen number that a particular point or widget is located in is returned by screenNumber().
.PP
Widgets provided by Qt use this class, for example, to place tooltips, menus and dialog boxes according to the parent or application widget.
Widgets provided by TQt use this class, for example, to place tooltips, menus and dialog boxes according to the parent or application widget.
.PP
Applications can use this class to save window positions, or to place child widgets on one screen.
.PP
@ -178,8 +178,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
@ -167,7 +167,7 @@ A modeless dialog. After the show() call, control returns to the main event loop
.br
a.setMainWidget( life );
.br
life->setCaption("Qt Example - Life");
life->setCaption("TQt Example - Life");
.br
life->show();
.fi
@ -196,7 +196,7 @@ A dialog is always a top-level widget, but if it has a parent, its default locat
.PP
The widget flags \fIf\fR are passed on to the QWidget constructor. If, for example, you don't want a What's This button in the titlebar of the dialog, pass WStyle_Customize | WStyle_NormalBorder | WStyle_Title | WStyle_SysMenu in \fIf\fR.
.PP
\fBWarning:\fR In Qt 3.2, the \fImodal\fR flag is obsolete. There is now a setModal() function that can be used for obtaining a modal behavior when calling show(). This is rarely needed, because modal dialogs are usually invoked using exec(), which ignores the \fImodal\fR flag.
\fBWarning:\fR In TQt 3.2, the \fImodal\fR flag is obsolete. There is now a setModal() function that can be used for obtaining a modal behavior when calling show(). This is rarely needed, because modal dialogs are usually invoked using exec(), which ignores the \fImodal\fR flag.
.PP
See also QWidget::setWFlags() and Qt::WidgetFlags.
.SH "QDialog::~QDialog ()"
@ -310,8 +310,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
QDir \- Access to directory structures and their contents in a platform-independent way
.SH SYNOPSIS
All the functions in this class are reentrant when Qt is built with thread support.</p>
All the functions in this class are reentrant when TQt is built with thread support.</p>
.PP
\fC#include <ntqdir.h>\fR
.PP
@ -204,7 +204,7 @@ The QDir class provides access to directory structures and their contents in a p
.PP
A QDir is used to manipulate path names, access information regarding paths and files, and manipulate the underlying file system.
.PP
A QDir can point to a file using either a relative or an absolute path. Absolute paths begin with the directory separator "/" (optionally preceded by a drive specification under Windows). If you always use "/" as a directory separator, Qt will translate your paths to conform to the underlying operating system. Relative file names begin with a directory name or a file name and specify a path relative to the current directory.
A QDir can point to a file using either a relative or an absolute path. Absolute paths begin with the directory separator "/" (optionally preceded by a drive specification under Windows). If you always use "/" as a directory separator, TQt will translate your paths to conform to the underlying operating system. Relative file names begin with a directory name or a file name and specify a path relative to the current directory.
.PP
The "current" path refers to the application's working directory. A QDir's own path is set and retrieved with setPath() and path().
.PP
@ -220,7 +220,7 @@ To get a path with a filename use filePath(), and to get a directory name use di
.PP
The list of root directories is provided by drives(); on Unix systems this returns a list containing one root directory, "/"; on Windows the list will usually contain "C:/", and possibly "D:/", etc.
.PP
It is easiest to work with "/" separators in Qt code. If you need to present a path to the user or need a path in a form suitable for a function in the underlying operating system use convertSeparators().
It is easiest to work with "/" separators in TQt code. If you need to present a path to the user or need a path in a form suitable for a function in the underlying operating system use convertSeparators().
.PP
Examples:
.)l
@ -491,7 +491,7 @@ Example: dirview/main.cpp.
.SH "QStrList QDir::encodedEntryList ( int filterSpec = DefaultFilter, int sortSpec = DefaultSort ) const\fC [virtual]\fR"
\fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
.PP
This function is included to easy porting from Qt 1.x to Qt 2.0, it is the same as entryList(), but encodes the filenames as 8-bit strings using QFile::encodedName().
This function is included to easy porting from TQt 1.x to TQt 2.0, it is the same as entryList(), but encodes the filenames as 8-bit strings using QFile::encodedName().
.PP
It is more efficient to use entryList().
.SH "QStrList QDir::encodedEntryList ( const QString & nameFilter, int filterSpec = DefaultFilter, int sortSpec = DefaultSort ) const\fC [virtual]\fR"
@ -499,7 +499,7 @@ It is more efficient to use entryList().
.PP
This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
.PP
This function is included to easy porting from Qt 1.x to Qt 2.0, it is the same as entryList(), but encodes the filenames as 8-bit strings using QFile::encodedName().
This function is included to easy porting from TQt 1.x to TQt 2.0, it is the same as entryList(), but encodes the filenames as 8-bit strings using QFile::encodedName().
Returns the native directory separator; "/" under UNIX (including Mac OS X) and "\" under Windows.
.PP
You do not need to use this function to build file paths. If you always use "/", Qt will translate your paths to conform to the underlying operating system.
You do not need to use this function to build file paths. If you always use "/", TQt will translate your paths to conform to the underlying operating system.
@ -215,7 +215,7 @@ In the example above we create a new QToolBar in the constructor of a QMainWindo
.PP
A dock window is often used to contain a single widget. In these cases the widget can be set by calling setWidget(). If you're constructing a dock window that contains multiple widgets, e.g. a toolbar, arrange the widgets within a box layout inside the dock window. To do this use the boxLayout() function to get a pointer to the dock window's box layout, then add widgets to the layout using the box layout's QBoxLayout::addWidget() function. The dock window will dynamically set the orientation of the layout to be vertical or horizontal as necessary, although you can control this yourself with setOrientation().
.PP
Although a common use of dock windows is for toolbars, they can be used with any widgets. (See the Qt Designer and Qt Linguist applications, for example.) When using larger widgets it may make sense for the dock window to be resizable by calling setResizeEnabled(). Resizable dock windows are given splitter-like handles to allow the user to resize them within their dock area. When resizable dock windows are undocked they become top level windows and can be resized like any other top level windows, e.g. by dragging a corner or edge.
Although a common use of dock windows is for toolbars, they can be used with any widgets. (See the TQt Designer and TQt Linguist applications, for example.) When using larger widgets it may make sense for the dock window to be resizable by calling setResizeEnabled(). Resizable dock windows are given splitter-like handles to allow the user to resize them within their dock area. When resizable dock windows are undocked they become top level windows and can be resized like any other top level windows, e.g. by dragging a corner or edge.
.PP
Dock windows can be docked and undocked using dock() and undock(). A dock window's orientation can be set with setOrientation(). You can also use QDockArea::moveDockWindow(). If you're using a QMainWindow, QMainWindow::moveDockWindow() and QMainWindow::removeDockWindow() are available.
.PP
@ -458,8 +458,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
QEucJpCodec \- Conversion to and from EUC-JP character sets
.SH SYNOPSIS
All the functions in this class are reentrant when Qt is built with thread support.</p>
All the functions in this class are reentrant when TQt is built with thread support.</p>
.PP
\fC#include <ntqeucjpcodec.h>\fR
.PP
@ -37,7 +37,7 @@ More precisely, the QEucJpCodec class subclasses QTextCodec to provide support f
.PP
The environment variable \fCUNICODEMAP_JP\fR can be used to fine-tune QJisCodec, QSjisCodec and QEucJpCodec. The QJisCodec documentation describes how to use this variable.
.PP
Most of the code here was written by Serika Kurusugawa, a.k.a. Junji Takagi, and is included in Qt with the author's permission and the grateful thanks of the Trolltech team. Here is the copyright statement for that code:
Most of the code here was written by Serika Kurusugawa, a.k.a. Junji Takagi, and is included in TQt with the author's permission and the grateful thanks of the Trolltech team. Here is the copyright statement for that code:
.PP
Copyright (C) 1999 Serika Kurusugawa. All rights reserved.
.PP
@ -78,8 +78,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
@ -91,7 +91,7 @@ It receives events from the window system and other sources. It then sends them
.PP
QEventLoop allows the application programmer to have more control over event delivery. Programs that perform long operations can call either processOneEvent() or processEvents() with various ProcessEvent values OR'ed together to control which events should be delivered.
.PP
QEventLoop also allows the integration of an external event loop with the Qt event loop. The Motif Extension included with Qt includes a reimplementation of QEventLoop for merging Qt and Motif events together.
QEventLoop also allows the integration of an external event loop with the TQt event loop. The Motif Extension included with TQt includes a reimplementation of QEventLoop for merging TQt and Motif events together.
.PP
To use your own instance of QEventLoop or QEventLoop subclass create it before you create the QApplication object.
.PP
@ -127,7 +127,7 @@ See also awake().
.SH "int QEventLoop::activateSocketNotifiers ()"
Activates all pending socket notifiers and returns the number of socket notifiers that were activated.
.SH "int QEventLoop::activateTimers ()"
Activates all Qt timers and returns the number of timers that were activated.
Activates all TQt timers and returns the number of timers that were activated.
.PP
QEventLoop subclasses that do their own timer handling need to call this after the time returned by timeToWait() has elapsed.
.PP
@ -200,7 +200,7 @@ Registers \fInotifier\fR with the event loop. Subclasses need to reimplement thi
Unregisters \fInotifier\fR from the event loop. Subclasses need to reimplement this method to tie a socket notifier into another event loop. Reimplementations \fIMUST\fR call the base implementation.
.SH "void QEventLoop::wakeUp ()\fC [virtual]\fR"
\fBNote:\fR This function is thread-safe when Qt is built withthread support.</p>
\fBNote:\fR This function is thread-safe when TQt is built withthread support.</p>
.PP
Wakes up the event loop.
.PP
@ -228,8 +228,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
Almost all the functions in this class are reentrant when Qt is built with thread support. The exceptions are \fBsetEncodingFunction\fR(), \fBsetDecodingFunction\fR(), and \fBsetErrorString\fR(). </p>
Almost all the functions in this class are reentrant when TQt is built with thread support. The exceptions are \fBsetEncodingFunction\fR(), \fBsetDecodingFunction\fR(), and \fBsetErrorString\fR(). </p>
.PP
\fC#include <ntqfile.h>\fR
.PP
@ -514,8 +514,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
All the functions in this class are reentrant when Qt is built with thread support.</p>
All the functions in this class are reentrant when TQt is built with thread support.</p>
.PP
\fC#include <ntqfileinfo.h>\fR
.PP
@ -187,7 +187,7 @@ This enum is used by the permission() function to report the permissions and own
.TP
\fCQFileInfo::ExeOther\fR - The file is executable by anyone.
.PP
\fBWarning:\fR The semantics of ReadUser, WriteUser and ExeUser are unfortunately not platform independent: on Unix, the rights of the owner of the file are returned and on Windows the rights of the current user are returned. This behavior might change in a future Qt version. If you want to find the rights of the owner of the file, you should use the flags ReadOwner, WriteOwner and ExeOwner. If you want to find out the rights of the current user, you should use isReadable(), isWritable() and isExecutable().
\fBWarning:\fR The semantics of ReadUser, WriteUser and ExeUser are unfortunately not platform independent: on Unix, the rights of the owner of the file are returned and on Windows the rights of the current user are returned. This behavior might change in a future TQt version. If you want to find the rights of the owner of the file, you should use the flags ReadOwner, WriteOwner and ExeOwner. If you want to find out the rights of the current user, you should use isReadable(), isWritable() and isExecutable().
.SH MEMBER FUNCTION DOCUMENTATION
.SH "QFileInfo::QFileInfo ()"
Constructs a new empty QFileInfo.
@ -525,8 +525,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
@ -230,7 +230,7 @@ QFont \- Font used for drawing text
.SH DESCRIPTION
The QFont class specifies a font used for drawing text.
.PP
When you create a QFont object you specify various attributes that you want the font to have. Qt will use the font with the specified attributes, or if no matching font exists, Qt will use the closest matching installed font. The attributes of the font that is actually used are retrievable from a QFontInfo object. If the window system provides an exact match exactMatch() returns TRUE. Use QFontMetrics to get measurements, e.g. the pixel length of a string using QFontMetrics::width().
When you create a QFont object you specify various attributes that you want the font to have. TQt will use the font with the specified attributes, or if no matching font exists, TQt will use the closest matching installed font. The attributes of the font that is actually used are retrievable from a QFontInfo object. If the window system provides an exact match exactMatch() returns TRUE. Use QFontMetrics to get measurements, e.g. the pixel length of a string using QFontMetrics::width().
.PP
Use QApplication::setFont() to set the application's default font.
.PP
@ -270,9 +270,9 @@ Each replacement font family is searched for.
.IP 4
If none of these are found or there was no styleHint(), "helvetica" will be searched for.
.IP 5
If "helvetica" isn't found Qt will try the lastResortFamily().
If "helvetica" isn't found TQt will try the lastResortFamily().
.IP 6
If the lastResortFamily() isn't found Qt will try the lastResortFont() which will always return a name of some kind.
If the lastResortFamily() isn't found TQt will try the lastResortFont() which will always return a name of some kind.
.PP
Once a font is found, the remaining attributes are matched in order of priority: <ol type=1>
.IP 7
@ -302,9 +302,9 @@ If you had both an Adobe and a Cronyx Helvetica, you might get either.
You can specify the foundry you want in the family name. Both fonts, f1 and f2, in the above example will be set to "Helvetica [Cronyx]".
@ -553,7 +553,7 @@ Constructs a font object with the specified \fIfamily\fR, \fIpointSize\fR, \fIwe
.PP
If \fIpointSize\fR is <= 0 it is set to 1.
.PP
The \fIfamily\fR name may optionally also include a foundry name, e.g. "Helvetica [Cronyx]". (The Qt 2.x syntax, i.e." Cronyx-Helvetica", is also supported.) If the \fIfamily\fR is available from more than one foundry and the foundry isn't specified, an arbitrary foundry is chosen. If the family isn't available a family will be set using the font matching algorithm.
The \fIfamily\fR name may optionally also include a foundry name, e.g. "Helvetica [Cronyx]". (The TQt 2.x syntax, i.e." Cronyx-Helvetica", is also supported.) If the \fIfamily\fR is available from more than one foundry and the foundry isn't specified, an arbitrary foundry is chosen. If the family isn't available a family will be set using the font matching algorithm.
.PP
See also Weight, setFamily(), setPointSize(), setWeight(), setItalic(), setStyleHint(), and QApplication::font().
.SH "QFont::QFont ( const QFont & font )"
@ -640,7 +640,7 @@ Returns a "last resort" font name for the font matching algorithm. This is used
.PP
The current implementation tries a wide variety of common fonts, returning the first one it finds. The implementation may change at any time, but this function will always return a string containing something.
.PP
It is theoretically possible that there really isn't a lastResortFont() in which case Qt will abort with an error message. We have not been able to identify a case where this happens. Please report it as a bug if it does, preferably with a list of the fonts you have installed.
It is theoretically possible that there really isn't a lastResortFont() in which case TQt will abort with an error message. We have not been able to identify a case where this happens. Please report it as a bug if it does, preferably with a list of the fonts you have installed.
.PP
See also lastResortFamily() and rawName().
.SH "bool QFont::operator!= ( const QFont & f ) const"
@ -691,7 +691,7 @@ Returns the name of the font within the underlying window system.
.PP
On Windows, this is usually just the family name of a TrueType font.
.PP
On X11, it is an XLFD (X Logical Font Description). When Qt is build with Xft support on X11, the return value can be an Xft pattern or an XLFD.
On X11, it is an XLFD (X Logical Font Description). When TQt is build with Xft support on X11, the return value can be an Xft pattern or an XLFD.
.PP
Using the return value of this function is usually \fInot\fR \fIportable\fR.
.PP
@ -718,7 +718,7 @@ Please use QApplication::setFont() instead.
.SH "void QFont::setFamily ( const QString & family )"
Sets the family name of the font. The name is case insensitive and may include a foundry name.
.PP
The \fIfamily\fR name may optionally also include a foundry name, e.g. "Helvetica [Cronyx]". (The Qt 2.x syntax, i.e." Cronyx-Helvetica", is also supported.) If the \fIfamily\fR is available from more than one foundry and the foundry isn't specified, an arbitrary foundry is chosen. If the family isn't available a family will be set using the font matching algorithm.
The \fIfamily\fR name may optionally also include a foundry name, e.g. "Helvetica [Cronyx]". (The TQt 2.x syntax, i.e." Cronyx-Helvetica", is also supported.) If the \fIfamily\fR is available from more than one foundry and the foundry isn't specified, an arbitrary foundry is chosen. If the family isn't available a family will be set using the font matching algorithm.
.PP
See also family(), setStyleHint(), and QFontInfo.
.SH "void QFont::setFixedPitch ( bool enable )"
@ -761,7 +761,7 @@ See also pointSizeFloat(), setPointSize(), and setPixelSize().
.SH "void QFont::setRawMode ( bool enable )"
If \fIenable\fR is TRUE, turns raw mode on; otherwise turns raw mode off. This function only has an effect under X11.
.PP
If raw mode is enabled, Qt will search for an X font with a complete font name matching the family name, ignoring all other values set for the QFont. If the font name matches several fonts, Qt will use the first font returned by X. QFontInfo \fIcannot\fR be used to fetch information about a QFont using raw mode (it will return the values set in the QFont for all parameters, including the family name).
If raw mode is enabled, TQt will search for an X font with a complete font name matching the family name, ignoring all other values set for the QFont. If the font name matches several fonts, TQt will use the first font returned by X. QFontInfo \fIcannot\fR be used to fetch information about a QFont using raw mode (it will return the values set in the QFont for all parameters, including the family name).
.PP
\fBWarning:\fR Do not use raw mode unless you really, really need it! In most (if not all) cases, setRawName() is a much better choice.
.PP
@ -894,8 +894,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
@ -112,7 +112,7 @@ The QFontDatabase class provides information about the fonts available in the un
.PP
The most common uses of this class are to query the database for the list of font families() and for the pointSizes() and styles() that are available for each family. An alternative to pointSizes() is smoothSizes() which returns the sizes at which a given family and style will look attractive.
.PP
If the font family is available from two or more foundries the foundry name is included in the family name, e.g. "Helvetica [Adobe]" and "Helvetica [Cronyx]". When you specify a family you can either use the old hyphenated Qt 2.x "foundry-family" format, e.g. "Cronyx-Helvetica", or the new bracketed Qt 3.x "family [foundry]" format e.g. "Helvetica [Cronyx]". If the family has a foundry it is always returned, e.g. by families(), using the bracketed format.
If the font family is available from two or more foundries the foundry name is included in the family name, e.g. "Helvetica [Adobe]" and "Helvetica [Cronyx]". When you specify a family you can either use the old hyphenated TQt 2.x "foundry-family" format, e.g. "Cronyx-Helvetica", or the new bracketed TQt 3.x "family [foundry]" format e.g. "Helvetica [Cronyx]". If the family has a foundry it is always returned, e.g. by families(), using the bracketed format.
.PP
The font() function returns a QFont given a family, style and point size.
.PP
@ -291,8 +291,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
@ -108,7 +108,7 @@ This is an overloaded member function, provided for convenience. It behaves esse
.PP
Executes a modal font dialog and returns a font.
.PP
If the user clicks OK, the selected font is returned. If the user clicks Cancel, the Qt default font is returned.
If the user clicks OK, the selected font is returned. If the user clicks Cancel, the TQt default font is returned.
.PP
The dialog is called \fIname\fR, with parent \fIparent\fR. If the \fIok\fR parameter is not-null, \fI*\fR\fIok\fR is set to TRUE if the user clicked OK, and FALSE if the user clicked Cancel.
.PP
@ -151,8 +151,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
@ -289,7 +289,7 @@ The functions hasPendingCommands() and clearPendingCommands() allow you to query
.PP
The safest and easiest way to use the FTP protocol is to use QUrlOperator() or the FTP commands described above. If you are an experienced network programmer and want to have complete control you can use rawCommand() to execute arbitrary FTP commands.
.PP
See also Qt Network Documentation, QNetworkProtocol, QUrlOperator, QHttp, and Input/Output and Networking.
See also TQt Network Documentation, QNetworkProtocol, QUrlOperator, QHttp, and Input/Output and Networking.
.SS "Member Type Documentation"
.SH "QFtp::Command"
This enum is used as the return value for the currentCommand() function. This allows you to perform specific actions for particular commands, e.g. in a FTP client, you might want to clear the directory view when a list() command is started; in this case you can simply check in the slot connected to the start() signal if the currentCommand() is List.
@ -637,8 +637,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
The GBK codec was contributed to Qt by Justin Yu <justiny@turbolinux.com.cn> and Sean Chen <seanc@turbolinux.com.cn>. They may also be reached at Yu Mingjian <yumj@sun.ihep.ac.cn>, <yumingjian@china.com> Chen Xiangyang <chenxy@sun.ihep.ac.cn>
The GBK codec was contributed to TQt by Justin Yu <justiny@turbolinux.com.cn> and Sean Chen <seanc@turbolinux.com.cn>. They may also be reached at Yu Mingjian <yumj@sun.ihep.ac.cn>, <yumingjian@china.com> Chen Xiangyang <chenxy@sun.ihep.ac.cn>
.PP
The GB18030 codec Qt functions were contributed to Qt by James Su <suzhe@gnuchina.org>, <suzhe@turbolinux.com.cn> who pioneered much of GB18030 development on GNU/Linux systems.
The GB18030 codec TQt functions were contributed to TQt by James Su <suzhe@gnuchina.org>, <suzhe@turbolinux.com.cn> who pioneered much of GB18030 development on GNU/Linux systems.
.PP
The GB18030 codec was contributed to Qt by Anthony Fok <anthony@thizlinux.com>, <foka@debian.org> using a Perl script to generate C++ tables from gb-18030-2000.xml while merging contributions from James Su, Justin Yu and Sean Chen. A copy of the source Perl script is available at:
The GB18030 codec was contributed to TQt by Anthony Fok <anthony@thizlinux.com>, <foka@debian.org> using a Perl script to generate C++ tables from gb-18030-2000.xml while merging contributions from James Su, Justin Yu and Sean Chen. A copy of the source Perl script is available at:
QGL \- Namespace for miscellaneous identifiers in the Qt OpenGL module
QGL \- Namespace for miscellaneous identifiers in the TQt OpenGL module
.SH SYNOPSIS
\fC#include <ntqgl.h>\fR
.PP
@ -20,7 +20,7 @@ Inherited by QGLFormat, QGLContext, and QGLWidget.
.br
.in -1c
.SH DESCRIPTION
The QGL class is a namespace for miscellaneous identifiers in the Qt OpenGL module.
The QGL class is a namespace for miscellaneous identifiers in the TQt OpenGL module.
.PP
Normally you can ignore this class. QGLWidget and the other OpenGL<sup>*</sup> module classes inherit it, so when you make your own QGLWidget subclass you can use the identifiers in the QGL namespace without qualification.
.PP
@ -83,8 +83,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
The QGLWidget class is a widget for rendering OpenGL graphics.
.PP
QGLWidget provides functionality for displaying OpenGL<sup>*</sup> graphics integrated into a Qt application. It is very simple to use. You inherit from it and use the subclass like any other QWidget, except that instead of drawing the widget's contents using QPainter etc. you use the standard OpenGL rendering commands.
QGLWidget provides functionality for displaying OpenGL<sup>*</sup> graphics integrated into a TQt application. It is very simple to use. You inherit from it and use the subclass like any other QWidget, except that instead of drawing the widget's contents using QPainter etc. you use the standard OpenGL rendering commands.
.PP
QGLWidget provides three convenient virtual functions that you can reimplement in your subclass to perform the typical OpenGL tasks:
.TP
@ -157,7 +157,7 @@ Here is a rough outline of how a QGLWidget subclass might look:
.br
{
.br
TQ_OBJECT // must include this if you use Qt signals/slots
TQ_OBJECT // must include this if you use TQt signals/slots
.br
.br
public:
@ -255,7 +255,7 @@ initializeOverlayGL()
.PP
These methods work in the same way as the normal paintGL() etc. functions, except that they will be called when the overlay context is made current. You can explicitly make the overlay context current by using makeOverlayCurrent(), and you can access the overlay context directly (e.g. to ask for its transparent color) by calling overlayContext().
.PP
On X servers in which the default visual is in an overlay plane, non-GL Qt windows can also be used for overlays. See the examples/opengl/overlay_x11 example program for details.
On X servers in which the default visual is in an overlay plane, non-GL TQt windows can also be used for overlays. See the examples/opengl/overlay_x11 example program for details.
.PP
<sup>*</sup> OpenGL is a trademark of Silicon Graphics, Inc. in the United States and other countries.
.PP
@ -500,8 +500,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
@ -261,7 +261,7 @@ Alignment is specified by \fIalignment\fR, which is a bitwise OR of Qt::Alignmen
You should not call this if you have enabled the auto-add facility of the layout.
.IP
.TP
From Qt 3.0, the \fIalignment\fR parameter is interpreted more aggressively than in previous versions of Qt. A non-default alignment now indicates that the widget should not grow to fill the available space, but should be sized according to sizeHint().
From TQt 3.0, the \fIalignment\fR parameter is interpreted more aggressively than in previous versions of Qt. A non-default alignment now indicates that the widget should not grow to fill the available space, but should be sized according to sizeHint().
.PP
See also addMultiCellWidget().
.PP
@ -270,7 +270,7 @@ Examples:
.SH "QRect QGridLayout::cellGeometry ( int row, int col ) const"
Returns the geometry of the cell with row \fIrow\fR and column \fIcol\fR in the grid. Returns an invalid rectangle if \fIrow\fR or \fIcol\fR is outside the grid.
.PP
\fBWarning:\fR in the current version of Qt this function does not return valid results until setGeometry() has been called, i.e. after the mainWidget() is visible.
\fBWarning:\fR in the current version of TQt this function does not return valid results until setGeometry() has been called, i.e. after the mainWidget() is visible.
.SH "int QGridLayout::colSpacing ( int col ) const"
Returns the column spacing for column \fIcol\fR.
.PP
@ -378,8 +378,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
@ -205,7 +205,7 @@ Sets whether the group box has a checkbox in its title to \fIb\fR. See the "chec
.SH "void QGroupBox::setChecked ( bool b )\fC [slot]\fR"
Sets whether the group box's checkbox is checked to \fIb\fR. See the "checked" property for details.
.SH "void QGroupBox::setColumnLayout ( int strips, Orientation direction )\fC [virtual]\fR"
Changes the layout of the group box. This function is only useful in combination with the default constructor that does not take any layout information. This function will put all existing children in the new layout. It is not good Qt programming style to call this function after children have been inserted. Sets the number of columns or rows to be \fIstrips\fR, depending on \fIdirection\fR.
Changes the layout of the group box. This function is only useful in combination with the default constructor that does not take any layout information. This function will put all existing children in the new layout. It is not good TQt programming style to call this function after children have been inserted. Sets the number of columns or rows to be \fIstrips\fR, depending on \fIdirection\fR.
.PP
See also orientation and columns.
.PP
@ -317,8 +317,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
@ -88,7 +88,7 @@ The QIconSet class provides a set of icons with different styles and sizes.
.PP
A QIconSet can generate smaller, larger, active, and disabled pixmaps from the set of icons it is given. Such pixmaps are used by QToolButton, QHeader, QPopupMenu, etc. to show an icon representing a particular action.
.PP
The simplest use of QIconSet is to create one from a QPixmap and then use it, allowing Qt to work out all the required icon styles and sizes. For example:
The simplest use of QIconSet is to create one from a QPixmap and then use it, allowing TQt to work out all the required icon styles and sizes. For example:
.PP
.nf
.br
@ -112,7 +112,7 @@ You can use the static function setIconSize() to set the preferred size of the g
.PP
The isGenerated() function returns TRUE if an icon was generated by QIconSet or by a factory; clearGenerated() clears all cached pixmaps.
.SH "Making Classes that Use QIconSet"
If you write your own widgets that have an option to set a small pixmap, consider allowing a QIconSet to be set for that pixmap. The Qt class QToolButton is an example of such a widget.
If you write your own widgets that have an option to set a small pixmap, consider allowing a QIconSet to be set for that pixmap. The TQt class QToolButton is an example of such a widget.
.PP
Provide a method to set a QIconSet, and when you draw the icon, choose whichever icon is appropriate for the current state of your widget. For example:
.PP
@ -272,8 +272,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
@ -305,7 +305,7 @@ QImage \- Hardware-independent pixmap representation with direct access to the p
.SH DESCRIPTION
The QImage class provides a hardware-independent pixmap representation with direct access to the pixel data.
.PP
It is one of the two classes Qt provides for dealing with images, the other being QPixmap. QImage is designed and optimized for I/O and for direct pixel access/manipulation. QPixmap is designed and optimized for drawing. There are (slow) functions to convert between QImage and QPixmap: QPixmap::convertToImage() and QPixmap::convertFromImage().
It is one of the two classes TQt provides for dealing with images, the other being QPixmap. QImage is designed and optimized for I/O and for direct pixel access/manipulation. QPixmap is designed and optimized for drawing. There are (slow) functions to convert between QImage and QPixmap: QPixmap::convertToImage() and QPixmap::convertFromImage().
.PP
An image has the parameters width, height and depth (bits per pixel, bpp), a color table and the actual pixels. QImage supports 1-bpp, 8-bpp and 32-bpp image data. 1-bpp and 8-bpp images use a color lookup table; the pixel value is a color table index.
.PP
@ -1083,8 +1083,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
@ -38,7 +38,7 @@ New image file formats are installed by creating objects of derived classes of Q
.PP
QImageFormatType is a very simple class. Its only task is to recognize image data in some format and make a new object, subclassed from QImageFormat, which can decode that format.
.PP
The factories for formats built into Qt are automatically defined before any other factory is initialized. If two factories would recognize an image format, the factory created last will override the earlier one; you can thus override current and future built-in formats.
The factories for formats built into TQt are automatically defined before any other factory is initialized. If two factories would recognize an image format, the factory created last will override the earlier one; you can thus override current and future built-in formats.
.PP
See also Graphics Classes, Image Processing Classes, and Multimedia Classes.
.SH MEMBER FUNCTION DOCUMENTATION
@ -66,8 +66,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
@ -107,7 +107,7 @@ QImageIO \- Parameters for loading and saving images
.SH DESCRIPTION
The QImageIO class contains parameters for loading and saving images.
.PP
QImageIO contains a QIODevice object that is used for image data I/O. The programmer can install new image file formats in addition to those that Qt provides.
QImageIO contains a QIODevice object that is used for image data I/O. The programmer can install new image file formats in addition to those that TQt provides.
.PP
Qt currently supports the following image file formats: PNG, BMP, XBM, XPM and PNM. It may also support JPEG, MNG and GIF, if specially configured during compilation. The different PNM formats are: PBM (P1 or P4), PGM (P2 or P5), and PPM (P3 or P6).
.PP
@ -134,7 +134,7 @@ Destroys the object and all related data.
Defines an image I/O handler for the image format called \fIformat\fR, which is recognized using the regular expression \fIheader\fR, read using \fIreadImage\fR and written using \fIwriteImage\fR.
.PP
\fIflags\fR is a string of single-character flags for this format. The only flag defined currently is T (upper case), so the only legal value for \fIflags\fR are "T" and the empty string. The "T" flag means that the image file is a text file, and Qt should treat all newline conventions as equivalent. (XPM files and some PPM files are text files for example.)
\fIflags\fR is a string of single-character flags for this format. The only flag defined currently is T (upper case), so the only legal value for \fIflags\fR are "T" and the empty string. The "T" flag means that the image file is a text file, and TQt should treat all newline conventions as equivalent. (XPM files and some PPM files are text files for example.)
.PP
\fIformat\fR is used to select a handler to write a QImage; \fIheader\fR is used to select a handler to read an image file.
.PP
@ -177,11 +177,11 @@ Example:
.br
.fi
.PP
Before the regex test, all the 0 bytes in the file header are converted to 1 bytes. This is done because when Qt was ASCII-based, QRegExp could not handle 0 bytes in strings.
Before the regex test, all the 0 bytes in the file header are converted to 1 bytes. This is done because when TQt was ASCII-based, QRegExp could not handle 0 bytes in strings.
.PP
The regexp is only applied on the first 14 bytes of the file.
.PP
Note that Qt assumes that there is only one handler per format; if two handlers support the same format, Qt will choose one arbitrarily. It is not possible to have one handler support reading, and another support writing.
Note that TQt assumes that there is only one handler per format; if two handlers support the same format, TQt will choose one arbitrarily. It is not possible to have one handler support reading, and another support writing.
.SH "QString QImageIO::description () const"
Returns the image description string.
.PP
@ -257,7 +257,7 @@ See also setIODevice(), setFileName(), setFormat(), write(), and QPixmap::load()
Sets the image's parameter string to \fIparameters\fR. This is for image handlers that require special parameters.
.PP
Although the current image formats supported by Qt ignore the parameters string, it may be used in future extensions or by contributions (for example, JPEG).
Although the current image formats supported by TQt ignore the parameters string, it may be used in future extensions or by contributions (for example, JPEG).
.PP
See also parameters().
.SH "void QImageIO::setQuality ( int q )"
@ -353,8 +353,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
@ -113,7 +113,7 @@ The cache's size is limited, and if the total cost is too high, QIntCache will r
.PP
The parameter \fIp\fR is internal and should be left at the default value (0).
.PP
\fBWarning:\fR If this function returns FALSE (for example, the cost \fC,\fR exceeds maxCost()), you must delete \fId\fR yourself. Additionally, be very careful about using \fId\fR after calling this function. Any other insertions into the cache, from anywhere in the application or within Qt itself, could cause the object to be discarded from the cache and the pointer to become invalid.
\fBWarning:\fR If this function returns FALSE (for example, the cost \fC,\fR exceeds maxCost()), you must delete \fId\fR yourself. Additionally, be very careful about using \fId\fR after calling this function. Any other insertions into the cache, from anywhere in the application or within TQt itself, could cause the object to be discarded from the cache and the pointer to become invalid.
.SH "bool QIntCache::isEmpty () const"
Returns TRUE if the cache is empty; otherwise returns FALSE.
.SH "int QIntCache::maxCost () const"
@ -173,8 +173,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
QJisCodec \- Conversion to and from JIS character sets
.SH SYNOPSIS
All the functions in this class are reentrant when Qt is built with thread support.</p>
All the functions in this class are reentrant when TQt is built with thread support.</p>
.PP
\fC#include <ntqjiscodec.h>\fR
.PP
@ -51,7 +51,7 @@ In addition, the extensions "nec-vdc", "ibm-vdc" and "udc" are supported.
.PP
For example, if you want to use Unicode style conversion but with NEC's extension, set \fCUNICODEMAP_JP\fR to <nobr>\fCunicode-0.9, nec-vdc\fR.</nobr> (You will probably need to quote that in a shell command.)
.PP
Most of the code here was written by Serika Kurusugawa, a.k.a. Junji Takagi, and is included in Qt with the author's permission and the grateful thanks of the Trolltech team. Here is the copyright statement for that code:
Most of the code here was written by Serika Kurusugawa, a.k.a. Junji Takagi, and is included in TQt with the author's permission and the grateful thanks of the Trolltech team. Here is the copyright statement for that code:
.PP
Copyright (C) 1999 Serika Kurusugawa. All rights reserved.
.PP
@ -84,8 +84,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
@ -419,7 +419,7 @@ This is typically a single-column list in which either no item or one item is se
.PP
QListBox will add scroll bars as necessary, but it isn't intended for \fIreally\fR big lists. If you want more than a few thousand items, it's probably better to use a different widget mainly because the scroll bars won't provide very good navigation, but also because QListBox may become slow with huge lists. (See QListView and QTable for possible alternatives.)
.PP
There are a variety of selection modes described in the QListBox::SelectionMode documentation. The default is Single selection mode, but you can change it using setSelectionMode(). (setMultiSelection() is still provided for compatibility with Qt 1.x. We recommend using setSelectionMode() in all code.)
There are a variety of selection modes described in the QListBox::SelectionMode documentation. The default is Single selection mode, but you can change it using setSelectionMode(). (setMultiSelection() is still provided for compatibility with TQt 1.x. We recommend using setSelectionMode() in all code.)
.PP
Because QListBox offers multiple selection it must display keyboard focus and selection state separately. Therefore there are functions both to set the selection state of an item, i.e. setSelected(), and to set which item displays keyboard focus, i.e. setCurrentItem().
.PP
@ -1098,8 +1098,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
@ -54,7 +54,7 @@ There are additional issues that should be taken into consideration to make an a
Layout - The restrictions on window layout are such that some aspects of layout that are style-dependent cannot be achieved using QLayout. Changes are being considered (and feedback would be appreciated) to make layouts QStyle-able. Some of the restrictions involve horizontal and vertical widget alignment and widget size (covered below).
.IP
.TP
Widget size - Aqua allows widgets to have specific fixed sizes. Qt does not fully implement this behaviour so as to maintain multiplatform compatibility. As a result some widgets sizes may be inappropriate (and subsequently not rendered correctly by the Appearance Manager).The QWidget::sizeHint() will return the appropriate size for many managed widgets (widgets enumerated in QStyle::ContentsType).
Widget size - Aqua allows widgets to have specific fixed sizes. TQt does not fully implement this behaviour so as to maintain multiplatform compatibility. As a result some widgets sizes may be inappropriate (and subsequently not rendered correctly by the Appearance Manager).The QWidget::sizeHint() will return the appropriate size for many managed widgets (widgets enumerated in QStyle::ContentsType).
.IP
.TP
Effects - QMacStyle (in contrast to QAquaStyle) is not emulating (except where Appearance Manager does not provide certain capabilities), for example QPushButton pulsing effects. In this case a near matching emulation has been implemented, but naturally this will not be identical to the similar functionality built into the Appearance Manager. Please report any issues you see in effects or non-standard widgets.
@ -123,8 +123,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
The QMainWindow class provides a main application window, with a menu bar, dock windows (e.g. for toolbars), and a status bar.
.PP
Main windows are most often used to provide menus, toolbars and a status bar around a large central widget, such as a text edit, drawing canvas or QWorkspace (for MDI applications). QMainWindow is usually subclassed since this makes it easier to encapsulate the central widget, menus and toolbars as well as the window's state. Subclassing makes it possible to create the slots that are called when the user clicks menu items or toolbar buttons. You can also create main windows using Qt Designer. We'll briefly review adding menu items and toolbar buttons then describe the facilities of QMainWindow itself.
Main windows are most often used to provide menus, toolbars and a status bar around a large central widget, such as a text edit, drawing canvas or QWorkspace (for MDI applications). QMainWindow is usually subclassed since this makes it easier to encapsulate the central widget, menus and toolbars as well as the window's state. Subclassing makes it possible to create the slots that are called when the user clicks menu items or toolbar buttons. You can also create main windows using TQt Designer. We'll briefly review adding menu items and toolbar buttons then describe the facilities of QMainWindow itself.
.PP
.nf
.br
@ -271,7 +271,7 @@ QMainWindows may be created in their own right as shown above. The central widge
.br
ApplicationWindow *mw = new ApplicationWindow();
.br
mw->setCaption( "Qt Example - Application" );
mw->setCaption( "TQt Example - Application" );
.br
mw->show();
.fi
@ -833,8 +833,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
@ -170,7 +170,7 @@ QMap \- Value-based template class that provides a dictionary
.SH DESCRIPTION
The QMap class is a value-based template class that provides a dictionary.
.PP
QMap is a Qt implementation of an STL-like map container. It can be used in your application if the standard \fCmap\fR is not available on all your target platforms. QMap is part of the Qt Template Library.
QMap is a TQt implementation of an STL-like map container. It can be used in your application if the standard \fCmap\fR is not available on all your target platforms. QMap is part of the TQt Template Library.
.PP
QMap<Key, Data> defines a template instance to create a dictionary with keys of type Key and values of type Data. QMap does not store pointers to the members of the map; instead, it holds a copy of every member. For this reason, QMap is value-based, whereas QPtrList and QDict are pointer-based.
.PP
@ -188,7 +188,7 @@ Note that C++ defaults to field-by-field assignment operators and copy construct
.PP
The class used for the key requires that the \fCoperator<\fR is implemented to define ordering of the keys.
.PP
QMap's function naming is consistent with the other Qt classes (e.g., count(), isEmpty()). QMap also provides extra functions for compatibility with STL algorithms, such as size() and empty(). Programmers already familiar with the STL \fCmap\fR can use these the STL-like functions if preferred.
QMap's function naming is consistent with the other TQt classes (e.g., count(), isEmpty()). QMap also provides extra functions for compatibility with STL algorithms, such as size() and empty(). Programmers already familiar with the STL \fCmap\fR can use these the STL-like functions if preferred.
.PP
Example:
.PP
@ -340,14 +340,14 @@ There are a couple of ways of inserting new items into the map. One uses the ins
.PP
Items can also be removed from the map in several ways. One way is to pass an iterator to remove(). Another way is to pass a key value to remove(), which will delete the entry with the requested key. In addition you can clear the entire map using the clear() method.
.PP
See also QMapIterator, Qt Template Library Classes, Implicitly and Explicitly Shared Classes, and Non-GUI Classes.
See also QMapIterator, TQt Template Library Classes, Implicitly and Explicitly Shared Classes, and Non-GUI Classes.
.SS "Member Type Documentation"
.SH "QMap::ConstIterator"
The map's const iterator type, Qt style.
The map's const iterator type, TQt style.
.SH "QMap::Iterator"
The map's iterator type, Qt style.
The map's iterator type, TQt style.
.SH "QMap::ValueType"
Corresponds to QPair<key_type, mapped_type>, Qt style.
Corresponds to QPair<key_type, mapped_type>, TQt style.
.SH "QMap::const_iterator"
The map's const iterator type.
.SH "QMap::const_pointer"
@ -542,8 +542,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
@ -77,7 +77,7 @@ QMap is highly optimized for performance and memory usage, but the trade-off is
.PP
For every Iterator there is also a ConstIterator. You must use the ConstIterator to access a QMap in a const environment or if the reference or pointer to the map is itself const. Its semantics are the same, but it only returns const references to the item it points to.
.PP
See also QMap, QMapConstIterator, Qt Template Library Classes, and Non-GUI Classes.
See also QMap, QMapConstIterator, TQt Template Library Classes, and Non-GUI Classes.
.SS "Member Type Documentation"
.SH "QMapIterator::iterator_category"
The type of iterator category, \fCstd::bidirectional_iterator_tag\fR.
@ -140,8 +140,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
@ -212,7 +212,7 @@ Menu items may be removed with removeItem() and enabled or disabled with setItem
.SH "QMenuBar on Qt/Mac"
QMenuBar on Qt/Mac is a wrapper for using the system-wide menubar. If you have multiple menubars in one dialog the outermost menubar (normally inside a widget with widget flag WType_TopLevel) will be used for the system-wide menubar.
.PP
Note that arbitrary Qt widgets \fIcannot\fR be inserted into a QMenuBar on the Mac because Qt uses Mac's native menus which don't support this functionality. This limitation does not apply to stand-alone QPopupMenus.
Note that arbitrary TQt widgets \fIcannot\fR be inserted into a QMenuBar on the Mac because TQt uses Mac's native menus which don't support this functionality. This limitation does not apply to stand-alone QPopupMenus.
.PP
Qt/Mac also provides a menubar merging feature to make QMenuBar conform more closely to accepted Mac OS X menubar layout. The merging functionality is based on string matching the title of a QPopupMenu entry. These strings are translated (using QObject::tr()) in the "QMenuBar" context. If an entry is moved its slots will still fire as if it was in the original place. The table below outlines the strings looked for and where the entry is placed if matched:
.PP
@ -318,15 +318,15 @@ In the example above, pressing Ctrl+O or selecting "Open" from the menu activate
.PP
Some insert functions take a QIconSet parameter to specify the little menu item icon. Note that you can always pass a QPixmap object instead.
.PP
The \fIid\fR specifies the identification number associated with the menu item. Note that only positive values are valid, as a negative value will make Qt select a unique id for the item.
The \fIid\fR specifies the identification number associated with the menu item. Note that only positive values are valid, as a negative value will make TQt select a unique id for the item.
.PP
The \fIindex\fR specifies the position in the menu. The menu item is appended at the end of the list if \fIindex\fR is negative.
.PP
Note that keyboard accelerators in Qt are not application-global, instead they are bound to a certain top-level window. For example, accelerators in QPopupMenu items only work for menus that are associated with a certain window. This is true for popup menus that live in a menu bar since their accelerators will then be installed in the menu bar itself. This also applies to stand-alone popup menus that have a top-level widget in their parentWidget() chain. The menu will then install its accelerator object on that top-level widget. For all other cases use an independent QAccel object.
Note that keyboard accelerators in TQt are not application-global, instead they are bound to a certain top-level window. For example, accelerators in QPopupMenu items only work for menus that are associated with a certain window. This is true for popup menus that live in a menu bar since their accelerators will then be installed in the menu bar itself. This also applies to stand-alone popup menus that have a top-level widget in their parentWidget() chain. The menu will then install its accelerator object on that top-level widget. For all other cases use an independent QAccel object.
.PP
\fBWarning:\fR Be careful when passing a literal 0 to insertItem() because some C++ compilers choose the wrong overloaded function. Cast the 0 to what you mean, e.g. \fC(QObject*)0\fR.
.PP
\fBWarning:\fR On Mac OS X, items that connect to a slot that are inserted into a menubar will not function as we use the native menubar that knows nothing about signals or slots. Instead insert the items into a popup menu and insert the popup menu into the menubar. This may be fixed in a future Qt version.
\fBWarning:\fR On Mac OS X, items that connect to a slot that are inserted into a menubar will not function as we use the native menubar that knows nothing about signals or slots. Instead insert the items into a popup menu and insert the popup menu into the menubar. This may be fixed in a future TQt version.
.PP
Returns the allocated menu identifier number (\fIid\fR if \fIid\fR >= 0).
.PP
@ -576,8 +576,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
@ -358,15 +358,15 @@ In the example above, pressing Ctrl+O or selecting "Open" from the menu activate
.PP
Some insert functions take a QIconSet parameter to specify the little menu item icon. Note that you can always pass a QPixmap object instead.
.PP
The \fIid\fR specifies the identification number associated with the menu item. Note that only positive values are valid, as a negative value will make Qt select a unique id for the item.
The \fIid\fR specifies the identification number associated with the menu item. Note that only positive values are valid, as a negative value will make TQt select a unique id for the item.
.PP
The \fIindex\fR specifies the position in the menu. The menu item is appended at the end of the list if \fIindex\fR is negative.
.PP
Note that keyboard accelerators in Qt are not application-global, instead they are bound to a certain top-level window. For example, accelerators in QPopupMenu items only work for menus that are associated with a certain window. This is true for popup menus that live in a menu bar since their accelerators will then be installed in the menu bar itself. This also applies to stand-alone popup menus that have a top-level widget in their parentWidget() chain. The menu will then install its accelerator object on that top-level widget. For all other cases use an independent QAccel object.
Note that keyboard accelerators in TQt are not application-global, instead they are bound to a certain top-level window. For example, accelerators in QPopupMenu items only work for menus that are associated with a certain window. This is true for popup menus that live in a menu bar since their accelerators will then be installed in the menu bar itself. This also applies to stand-alone popup menus that have a top-level widget in their parentWidget() chain. The menu will then install its accelerator object on that top-level widget. For all other cases use an independent QAccel object.
.PP
\fBWarning:\fR Be careful when passing a literal 0 to insertItem() because some C++ compilers choose the wrong overloaded function. Cast the 0 to what you mean, e.g. \fC(QObject*)0\fR.
.PP
\fBWarning:\fR On Mac OS X, items that connect to a slot that are inserted into a menubar will not function as we use the native menubar that knows nothing about signals or slots. Instead insert the items into a popup menu and insert the popup menu into the menubar. This may be fixed in a future Qt version.
\fBWarning:\fR On Mac OS X, items that connect to a slot that are inserted into a menubar will not function as we use the native menubar that knows nothing about signals or slots. Instead insert the items into a popup menu and insert the popup menu into the menubar. This may be fixed in a future TQt version.
.PP
Returns the allocated menu identifier number (\fIid\fR if \fIid\fR >= 0).
.PP
@ -591,7 +591,7 @@ An accelerator key consists of a key code and a combination of the modifiers \fC
.PP
Defining an accelerator key produces a text that is added to the menu item; for instance, \fCCTRL\fR + \fCKey_O\fR produces "Ctrl+O". The text is formatted differently for different platforms.
.PP
Note that keyboard accelerators in Qt are not application-global, instead they are bound to a certain top-level window. For example, accelerators in QPopupMenu items only work for menus that are associated with a certain window. This is true for popup menus that live in a menu bar since their accelerators will then be installed in the menu bar itself. This also applies to stand-alone popup menus that have a top-level widget in their parentWidget() chain. The menu will then install its accelerator object on that top-level widget. For all other cases use an independent QAccel object.
Note that keyboard accelerators in TQt are not application-global, instead they are bound to a certain top-level window. For example, accelerators in QPopupMenu items only work for menus that are associated with a certain window. This is true for popup menus that live in a menu bar since their accelerators will then be installed in the menu bar itself. This also applies to stand-alone popup menus that have a top-level widget in their parentWidget() chain. The menu will then install its accelerator object on that top-level widget. For all other cases use an independent QAccel object.
.PP
Example:
.PP
@ -695,8 +695,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
@ -332,7 +332,7 @@ QMessageBox provides a very simple About box which displays an appropriate icon
.PP
See about() for more information.
.PP
If you want your users to know that the application is built using Qt (so they know that you use high quality tools) you might like to add an "About Qt" menu option under the Help menu to invoke aboutTQt().
If you want your users to know that the application is built using TQt (so they know that you use high quality tools) you might like to add an "About Qt" menu option under the Help menu to invoke aboutTQt().
.PP
If none of the standard message boxes is suitable, you can create a QMessageBox from scratch and use custom button texts:
.PP
@ -537,7 +537,7 @@ See also QWidget::icon and QApplication::mainWidget().
Examples:
.)l action/application.cpp, application/application.cpp, chart/chartform.cpp, helpviewer/helpwindow.cpp, mdi/application.cpp, menu/menu.cpp, and themes/themes.cpp.
Displays a simple message box about Qt, with caption \fIcaption\fR and centered over \fIparent\fR (if \fIparent\fR is not 0). The message includes the version number of Qt being used by the application.
Displays a simple message box about Qt, with caption \fIcaption\fR and centered over \fIparent\fR (if \fIparent\fR is not 0). 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
@ -846,8 +846,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
@ -60,9 +60,9 @@ QMetaObject \- Meta information about Qt objects
.br
.in -1c
.SH DESCRIPTION
The QMetaObject class contains meta information about Qt objects.
The QMetaObject class contains meta information about TQt objects.
.PP
The Meta Object System in Qt is responsible for the signals and slots inter-object communication mechanism, runtime type information and the property system. All meta information in Qt is kept in a single instance of QMetaObject per class.
The Meta Object System in TQt is responsible for the signals and slots inter-object communication mechanism, runtime type information and the property system. All meta information in TQt is kept in a single instance of QMetaObject per class.
.PP
This class is not normally required for application programming. But if you write meta applications, such as scripting engines or GUI builders, you might find these functions useful:
.TP
@ -172,8 +172,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
This class is defined in the \fBQt Motif Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main Qt API.
This class is defined in the \fBQt Motif Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main TQt API.
.PP
The QMotif class provides the basis of the Motif Extension.
.PP
@ -76,7 +76,7 @@ Example usage of QMotif and QApplication:
This class is defined in the \fBQt Motif Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main Qt API.
This class is defined in the \fBQt Motif Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main TQt API.
.PP
The QMotifDialog class provides the QDialog API for Motif-based dialogs.
.PP
@ -166,8 +166,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
This class is defined in the \fBQt Motif Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main Qt API.
This class is defined in the \fBQt Motif Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main TQt API.
.PP
The QMotifWidget class provides the QWidget API for Xt/Motif widgets.
.PP
QMotifWidget exists to provide a QWidget that can act as a parent for any Xt/Motif widget. Since the QMotifWidget is a proper QWidget, it can be used as a top-level widget (e.g. 0 parent) or as a child of any other QWidget. Note: Since QMotifWidget acts as a parent for Xt/Motif widgets, you should not create QWidgets with a QMotifWidget parent.
.PP
An Xt/Motif widget with a top-level QMotifWidget parent can begin using the standard Qt dialogs and custom QDialogs while keeping the main Xt/Motif interface of the application. Using a QMotifWidget as the parent for the various QDialogs will ensure that modality and stacking works properly throughout the entire application.
An Xt/Motif widget with a top-level QMotifWidget parent can begin using the standard TQt dialogs and custom QDialogs while keeping the main Xt/Motif interface of the application. Using a QMotifWidget as the parent for the various QDialogs will ensure that modality and stacking works properly throughout the entire application.
.PP
Applications moving to Qt may have custom Xt/Motif widgets that will take time to rewrite with Qt. Such applications can use these custom widgets as QMotifWidget with QWidget parents. This allows the application's interface to be replaced gradually.
Applications moving to TQt may have custom Xt/Motif widgets that will take time to rewrite with Qt. Such applications can use these custom widgets as QMotifWidget with QWidget parents. This allows the application's interface to be replaced gradually.
.PP
\fBWarning:\fR QMotifWidget uses the X11 window ID of the Motif widget directly, instead of creating its own. Because ot this, QWidget::reparent() will not work. This includes the functions QWidget::showFullScreen() and QWidget::showNormal(), which use QWidget::reparent().
.SH MEMBER FUNCTION DOCUMENTATION
@ -74,8 +74,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
@ -132,9 +132,9 @@ QMovie objects are explicitly shared. This means that a QMovie copied from anoth
.PP
The set of data formats supported by QMovie is determined by the decoder factories that have been installed; the format of the input is determined as the input is decoded.
.PP
The supported formats are MNG (if Qt is configured with MNG support enabled) and GIF (if Qt is configured with GIF support enabled, see ntqgif.h).
The supported formats are MNG (if TQt is configured with MNG support enabled) and GIF (if TQt is configured with GIF support enabled, see ntqgif.h).
.PP
If Qt is configured to support GIF reading, we are required to state that "The Graphics Interchange Format(c) is the Copyright property of CompuServe Incorporated. GIF(sm) is a Service Mark property of CompuServe Incorporated.
If TQt is configured to support GIF reading, we are required to state that "The Graphics Interchange Format(c) is the Copyright property of CompuServe Incorporated. GIF(sm) is a Service Mark property of CompuServe Incorporated.
.PP
\fBWarning:\fR If you are in a country that recognizes software patents and in which Unisys holds a patent on LZW compression and/or decompression and you want to use GIF, Unisys may require you to license that technology. Such countries include Canada, Japan, the USA, France, Germany, Italy and the UK.
.PP
@ -310,8 +310,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
@ -135,13 +135,13 @@ Inherited by QFtp, QHttp, and QLocalFs.
.SH DESCRIPTION
The QNetworkProtocol class provides a common API for network protocols.
.PP
This is a base class which should be used for network protocols implementations that can then be used in Qt (e.g. in the file dialog) together with the QUrlOperator.
This is a base class which should be used for network protocols implementations that can then be used in TQt (e.g. in the file dialog) together with the QUrlOperator.
.PP
The easiest way to implement a new network protocol is to reimplement the operation*() methods, e.g. operationGet(), etc. Only the supported operations should be reimplemented. To specify which operations are supported, also reimplement supportedOperations() and return an int that is OR'd together using the supported operations from the QNetworkProtocol::Operation enum.
.PP
When you implement a network protocol this way, it is important to emit the correct signals. Also, always emit the finished() signal when an operation is done (on success \fIand\fR on failure). Qt relies on correctly emitted finished() signals.
When you implement a network protocol this way, it is important to emit the correct signals. Also, always emit the finished() signal when an operation is done (on success \fIand\fR on failure). TQt relies on correctly emitted finished() signals.
.PP
For a detailed description of the Qt Network Architecture and how to implement and use network protocols in Qt, see the Qt Network Documentation.
For a detailed description of the TQt Network Architecture and how to implement and use network protocols in Qt, see the TQt Network Documentation.
.PP
See also Input/Output and Networking.
.SS "Member Type Documentation"
@ -285,7 +285,7 @@ When implementing your own network protocol and reading children, you usually do
.SH "void QNetworkProtocol::operationGet ( QNetworkOperation * op )\fC [virtual protected]\fR"
When implementing a new network protocol, this method should be reimplemented if the protocol supports getting data; this method should then process the QNetworkOperation.
.PP
When you reimplement this method it's very important that you emit the correct signals at the correct time (especially the finished() signal after processing an operation). Take a look at the Qt Network Documentation which describes in detail how to reimplement this method. You may also want to look at the example implementation in examples/network/networkprotocol/nntp.cpp.
When you reimplement this method it's very important that you emit the correct signals at the correct time (especially the finished() signal after processing an operation). Take a look at the TQt Network Documentation which describes in detail how to reimplement this method. You may also want to look at the example implementation in examples/network/networkprotocol/nntp.cpp.
.PP
\fIop\fR is the pointer to the operation object which contains all the information on the operation that has finished, including the state, etc.
.PP
@ -295,7 +295,7 @@ Returns the operation, which is being processed, or 0 of no operation is being p
.SH "void QNetworkProtocol::operationListChildren ( QNetworkOperation * op )\fC [virtual protected]\fR"
When implementing a new network protocol, this method should be reimplemented if the protocol supports listing children (files); this method should then process this QNetworkOperation.
.PP
When you reimplement this method it's very important that you emit the correct signals at the correct time (especially the finished() signal after processing an operation). Take a look at the Qt Network Documentation which describes in detail how to reimplement this method. You may also want to look at the example implementation in examples/network/networkprotocol/nntp.cpp.
When you reimplement this method it's very important that you emit the correct signals at the correct time (especially the finished() signal after processing an operation). Take a look at the TQt Network Documentation which describes in detail how to reimplement this method. You may also want to look at the example implementation in examples/network/networkprotocol/nntp.cpp.
.PP
\fIop\fR is the pointer to the operation object which contains all the information on the operation that has finished, including the state, etc.
.SH "void QNetworkProtocol::operationMkDir ( QNetworkOperation * op )\fC [virtual protected]\fR"
When implementing a new network protocol, this method should be reimplemented if the protocol supports making directories; this method should then process this QNetworkOperation.
.PP
When you reimplement this method it's very important that you emit the correct signals at the correct time (especially the finished() signal after processing an operation). Take a look at the Qt Network Documentation which describes in detail how to reimplement this method. You may also want to look at the example implementation in examples/network/networkprotocol/nntp.cpp.
When you reimplement this method it's very important that you emit the correct signals at the correct time (especially the finished() signal after processing an operation). Take a look at the TQt Network Documentation which describes in detail how to reimplement this method. You may also want to look at the example implementation in examples/network/networkprotocol/nntp.cpp.
.PP
\fIop\fR is the pointer to the operation object which contains all the information on the operation that has finished, including the state, etc.
.SH "void QNetworkProtocol::operationPut ( QNetworkOperation * op )\fC [virtual protected]\fR"
When implementing a new network protocol, this method should be reimplemented if the protocol supports putting (uploading) data; this method should then process the QNetworkOperation.
.PP
When you reimplement this method it's very important that you emit the correct signals at the correct time (especially the finished() signal after processing an operation). Take a look at the Qt Network Documentation which describes in detail how to reimplement this method. You may also want to look at the example implementation in examples/network/networkprotocol/nntp.cpp.
When you reimplement this method it's very important that you emit the correct signals at the correct time (especially the finished() signal after processing an operation). Take a look at the TQt Network Documentation which describes in detail how to reimplement this method. You may also want to look at the example implementation in examples/network/networkprotocol/nntp.cpp.
.PP
\fIop\fR is the pointer to the operation object which contains all the information on the operation that has finished, including the state, etc.
.SH "void QNetworkProtocol::operationRemove ( QNetworkOperation * op )\fC [virtual protected]\fR"
When implementing a new network protocol, this method should be reimplemented if the protocol supports removing children (files); this method should then process this QNetworkOperation.
.PP
When you reimplement this method it's very important that you emit the correct signals at the correct time (especially the finished() signal after processing an operation). Take a look at the Qt Network Documentation which is describes in detail how to reimplement this method. You may also want to look at the example implementation in examples/network/networkprotocol/nntp.cpp.
When you reimplement this method it's very important that you emit the correct signals at the correct time (especially the finished() signal after processing an operation). Take a look at the TQt Network Documentation which is describes in detail how to reimplement this method. You may also want to look at the example implementation in examples/network/networkprotocol/nntp.cpp.
.PP
\fIop\fR is the pointer to the operation object which contains all the information on the operation that has finished, including the state, etc.
.SH "void QNetworkProtocol::operationRename ( QNetworkOperation * op )\fC [virtual protected]\fR"
When implementing a new newtork protocol, this method should be reimplemented if the protocol supports renaming children (files); this method should then process this QNetworkOperation.
.PP
When you reimplement this method it's very important that you emit the correct signals at the correct time (especially the finished() signal after processing an operation). Take a look at the Qt Network Documentation which describes in detail how to reimplement this method. You may also want to look at the example implementation in examples/network/networkprotocol/nntp.cpp.
When you reimplement this method it's very important that you emit the correct signals at the correct time (especially the finished() signal after processing an operation). Take a look at the TQt Network Documentation which describes in detail how to reimplement this method. You may also want to look at the example implementation in examples/network/networkprotocol/nntp.cpp.
.PP
\fIop\fR is the pointer to the operation object which contains all the information on the operation that has finished, including the state, etc.
This class is defined in the \fBQt Netscape Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main Qt API.
This class is defined in the \fBQt Netscape Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main TQt API.
.PP
The QNPInstance class provides a QObject that is a web browser plugin.
.PP
@ -278,8 +278,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
@ -59,13 +59,13 @@ This class is part of the \fBQt Netscape Extension\fR.
.br
.in -1c
.SH DESCRIPTION
This class is defined in the \fBQt Netscape Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main Qt API.
This class is defined in the \fBQt Netscape Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main TQt API.
.PP
The QNPlugin class provides the main factory for plugin objects.
.PP
This class is the heart of the plugin. One instance of this object is created when the plugin is \fIfirst\fR needed, by calling QNPlugin::create(), which must be implemented in your plugin code to return some derived class of QNPlugin. The one QNPlugin object creates all QNPInstance instances for a web browser running in a single process.
.PP
Additionally, if Qt is linked to the plugin as a dynamic library, only one instance of QApplication will exist \fIacross all plugins that have been made with Qt\fR. So, your plugin should tread lightly on global settings. Do not, for example, use QApplication::setFont() - that will change the font in every widget of every Qt-based plugin currently loaded!
Additionally, if TQt is linked to the plugin as a dynamic library, only one instance of QApplication will exist \fIacross all plugins that have been made with Qt\fR. So, your plugin should tread lightly on global settings. Do not, for example, use QApplication::setFont() - that will change the font in every widget of every Qt-based plugin currently loaded!
.SH MEMBER FUNCTION DOCUMENTATION
.SH "QNPlugin::QNPlugin ()\fC [protected]\fR"
Creates a QNPlugin. This may only be used by the constructor of the class, derived from QNPlugin, that is returned by your plugin's implementation of the QNPlugin::create() function.
@ -145,8 +145,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
@ -53,7 +53,7 @@ This class is part of the \fBQt Netscape Extension\fR.
.br
.in -1c
.SH DESCRIPTION
This class is defined in the \fBQt Netscape Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main Qt API.
This class is defined in the \fBQt Netscape Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main TQt API.
.PP
The QNPStream class provides a stream of data provided to a QNPInstance by the browser.
.PP
@ -102,8 +102,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
This class is defined in the \fBQt Netscape Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main Qt API.
This class is defined in the \fBQt Netscape Extension\fR, which can be found in the \fCqt/extensions\fR directory. It is not included in the main TQt API.
.PP
The QNPWidget class provides a QWidget that is a web browser plugin window.
.PP
@ -117,8 +117,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
The QObject class is the base class of all Qt objects.
The QObject class is the base class of all TQt objects.
.PP
QObject is the heart of the Qt object model. The central feature in this model is a very powerful mechanism for seamless object communication called signals and slots. You can connect a signal to a slot with connect() and destroy the connection with disconnect(). To avoid never ending notification loops you can temporarily block signals with blockSignals(). The protected functions connectNotify() and disconnectNotify() make it possible to track connections.
QObject is the heart of the TQt object model. The central feature in this model is a very powerful mechanism for seamless object communication called signals and slots. You can connect a signal to a slot with connect() and destroy the connection with disconnect(). To avoid never ending notification loops you can temporarily block signals with blockSignals(). The protected functions connectNotify() and disconnectNotify() make it possible to track connections.
.PP
QObjects organize themselves in object trees. When you create a QObject with another object as parent, the object will automatically do an insertChild() on the parent and thus show up in the parent's children() list. The parent takes ownership of the object i.e. it will automatically delete its children in its destructor. You can look for an object by name and optionally type using child() or queryList(), and get the list of tree roots using objectTrees().
.PP
@ -211,7 +211,7 @@ Last but not least, QObject provides the basic timer support in Qt; see QTimer f
.PP
Notice that the TQ_OBJECT macro is mandatory for any object that implements signals, slots or properties. You also need to run the moc program (Meta Object Compiler) on the source file. We strongly recommend the use of this macro in \fIall\fR subclasses of QObject regardless of whether or not they actually use signals, slots and properties, since failure to do so may lead certain functions to exhibit undefined behaviour.
.PP
All Qt widgets inherit QObject. The convenience function isWidgetType() returns whether an object is actually a widget. It is much faster than inherits( "QWidget" ).
All TQt widgets inherit QObject. The convenience function isWidgetType() returns whether an object is actually a widget. It is much faster than inherits( "QWidget" ).
.PP
Some QObject functions, e.g. children(), objectTrees() and queryList() return a QObjectList. A QObjectList is a QPtrList of QObjects. QObjectLists support the same operations as QPtrLists and have an iterator class, QObjectListIt.
.PP
@ -388,7 +388,7 @@ See also event() and QCustomEvent.
.SH "void QObject::deleteLater ()\fC [slot]\fR"
Performs a deferred deletion of this object.
.PP
Instead of an immediate deletion this function schedules a deferred delete event for processing when Qt returns to the main event loop.
Instead of an immediate deletion this function schedules a deferred delete event for processing when TQt returns to the main event loop.
.PP
Example: table/bigtable/main.cpp.
.SH "void QObject::destroyed ()\fC [signal]\fR"
@ -579,7 +579,7 @@ Example:
.PP
Notice in the example above that unhandled events are passed to the base class's eventFilter() function, since the base class might have reimplemented eventFilter() for its own internal purposes.
.PP
\fBWarning:\fR If you delete the receiver object in this function, be sure to return TRUE. Otherwise, Qt will forward the event to the deleted object and the program might crash.
\fBWarning:\fR If you delete the receiver object in this function, be sure to return TRUE. Otherwise, TQt will forward the event to the deleted object and the program might crash.
.PP
See also installEventFilter().
.PP
@ -703,7 +703,7 @@ And here's how to install it on two widgets:
.PP
The QAccel class, for example, uses this technique to intercept accelerator key presses.
.PP
\fBWarning:\fR If you delete the receiver object in your eventFilter() function, be sure to return TRUE. If you return FALSE, Qt sends the event to the deleted object and the program will crash.
\fBWarning:\fR If you delete the receiver object in your eventFilter() function, be sure to return TRUE. If you return FALSE, TQt sends the event to the deleted object and the program will crash.
.PP
See also removeEventFilter(), eventFilter(), and event().
@ -779,7 +779,7 @@ Searches the children and optionally grandchildren of this object, and returns a
.PP
If \fIregexpMatch\fR is TRUE (the default), \fIobjName\fR is a regular expression that the objects's names must match. The syntax is that of a QRegExp. If \fIregexpMatch\fR is FALSE, \fIobjName\fR is a string and object names must match it exactly.
.PP
Note that \fIinheritsClass\fR uses single inheritance from QObject, the way inherits() does. According to inherits(), QMenuBar inherits QWidget but not QMenuData. This does not quite match reality, but is the best that can be done on the wide variety of compilers Qt supports.
Note that \fIinheritsClass\fR uses single inheritance from QObject, the way inherits() does. According to inherits(), QMenuBar inherits QWidget but not QMenuData. This does not quite match reality, but is the best that can be done on the wide variety of compilers TQt supports.
.PP
Finally, if \fIrecursiveSearch\fR is TRUE (the default), queryList() searches \fIn\fRth-generation as well as first-generation children.
.PP
@ -909,7 +909,7 @@ Example:
.br
.fi
.PP
Note that QTimer's accuracy depends on the underlying operating system and hardware. Most platforms support an accuracy of 20 ms; some provide more. If Qt is unable to deliver the requested number of timer clicks, it will silently discard some.
Note that QTimer's accuracy depends on the underlying operating system and hardware. Most platforms support an accuracy of 20 ms; some provide more. If TQt is unable to deliver the requested number of timer clicks, it will silently discard some.
.PP
The QTimer class provides a high-level programming interface with one-shot timers and timer signals instead of events.
.PP
@ -990,8 +990,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
@ -189,7 +189,7 @@ Example (scroll widget contents 10 pixels to the right):
.br
.fi
.PP
\fBWarning:\fR Qt requires that a QApplication object exists before any paint devices can be created. Paint devices access window system resources, and these resources are not initialized before an application object is created.
\fBWarning:\fR TQt requires that a QApplication object exists before any paint devices can be created. Paint devices access window system resources, and these resources are not initialized before an application object is created.
.PP
See also Graphics Classes and Image Processing Classes.
.SH MEMBER FUNCTION DOCUMENTATION
@ -372,8 +372,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
@ -474,7 +474,7 @@ Mostly, all this is done inside a paint event. (In fact, 99% of all QPainter use
Usage is simple, and there are many settings you can use:
.IP
.TP
font() is the currently set font. If you set a font that isn't available, Qt finds a close match. In fact font() returns what you set using setFont() and fontInfo() returns the font actually being used (which may be the same).
font() is the currently set font. If you set a font that isn't available, TQt finds a close match. In fact font() returns what you set using setFont() and fontInfo() returns the font actually being used (which may be the same).
.IP
.TP
brush() is the currently set brush; the color or pattern that's used for filling e.g. circles.
@ -782,7 +782,7 @@ If the supplied polygon is not convex, the results are undefined.
.PP
On some platforms (e.g. X Window), this is faster than drawPolygon().
.PP
\fBWarning:\fR On X11, coordinates that do not fit into 16-bit signed values are truncated. This limitation is expected to go away in Qt 4.
\fBWarning:\fR On X11, coordinates that do not fit into 16-bit signed values are truncated. This limitation is expected to go away in TQt 4.
.PP
Example: aclock/aclock.cpp.
.SH "void QPainter::drawCubicBezier ( const QPointArray & a, int index = 0 )"
@ -790,7 +790,7 @@ Draws a cubic Bezier curve defined by the control points in \fIa\fR, starting at
.PP
Control points after \fIa[index + 3]\fR are ignored. Nothing happens if there aren't enough control points.
.PP
\fBWarning:\fR On X11, coordinates that do not fit into 16-bit signed values are truncated. This limitation is expected to go away in Qt 4.
\fBWarning:\fR On X11, coordinates that do not fit into 16-bit signed values are truncated. This limitation is expected to go away in TQt 4.
.SH "void QPainter::drawEllipse ( int x, int y, int w, int h )"
Draws an ellipse with center at \fI(x + w/2, y + h/2)\fR and size \fI(w, h)\fR.
.PP
@ -842,7 +842,7 @@ Draws \fInlines\fR separate lines from points defined in \fIa\fR, starting at \f
.PP
Draws the 1st line from \fIa[index]\fR to \fIa[index+1]\fR. Draws the 2nd line from \fIa[index+2]\fR to \fIa[index+3]\fR etc.
.PP
\fBWarning:\fR On X11, coordinates that do not fit into 16-bit signed values are truncated. This limitation is expected to go away in Qt 4.
\fBWarning:\fR On X11, coordinates that do not fit into 16-bit signed values are truncated. This limitation is expected to go away in TQt 4.
.PP
See also drawPolyline(), drawPolygon(), and QPen.
.SH "void QPainter::drawPicture ( int x, int y, const QPicture & pic )"
@ -916,7 +916,7 @@ Draws/plots an array of points, \fIa\fR, using the current pen.
.PP
If \fIindex\fR is non-zero (the default is zero) only points from \fIindex\fR are drawn. If \fInpoints\fR is negative (the default) the rest of the points from \fIindex\fR are drawn. If \fInpoints\fR is zero or greater, \fInpoints\fR points are drawn.
.PP
\fBWarning:\fR On X11, coordinates that do not fit into 16-bit signed values are truncated. This limitation is expected to go away in Qt 4.
\fBWarning:\fR On X11, coordinates that do not fit into 16-bit signed values are truncated. This limitation is expected to go away in TQt 4.
.SH "void QPainter::drawPolygon ( const QPointArray & a, bool winding = FALSE, int index = 0, int npoints = -1 )"
Draws the polygon defined by the \fInpoints\fR points in \fIa\fR starting at \fIa[index]\fR. (\fIindex\fR defaults to 0.)
.PP
@ -926,7 +926,7 @@ The first point is always connected to the last point.
.PP
The polygon is filled with the current brush(). If \fIwinding\fR is TRUE, the polygon is filled using the winding fill algorithm. If \fIwinding\fR is FALSE, the polygon is filled using the even-odd (alternative) fill algorithm.
.PP
\fBWarning:\fR On X11, coordinates that do not fit into 16-bit signed values are truncated. This limitation is expected to go away in Qt 4.
\fBWarning:\fR On X11, coordinates that do not fit into 16-bit signed values are truncated. This limitation is expected to go away in TQt 4.
.PP
See also drawLineSegments(), drawPolyline(), and QPen.
.PP
@ -937,7 +937,7 @@ Draws the polyline defined by the \fInpoints\fR points in \fIa\fR starting at \f
.PP
If \fInpoints\fR is -1 (the default) all points until the end of the array are used (i.e. a.size()-index-1 line segments are drawn).
.PP
\fBWarning:\fR On X11, coordinates that do not fit into 16-bit signed values are truncated. This limitation is expected to go away in Qt 4.
\fBWarning:\fR On X11, coordinates that do not fit into 16-bit signed values are truncated. This limitation is expected to go away in TQt 4.
.PP
See also drawLineSegments(), drawPolygon(), and QPen.
.PP
@ -1697,8 +1697,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
@ -38,7 +38,7 @@ QPair \- Value-based template class that provides a pair of elements
.SH DESCRIPTION
The QPair class is a value-based template class that provides a pair of elements.
.PP
QPair is a Qt implementation of an STL-like pair. It can be used in your application if the standard pair<> is not available on your target platforms.
QPair is a TQt implementation of an STL-like pair. It can be used in your application if the standard pair<> is not available on your target platforms.
.PP
QPair<T1, T2> defines a template instance to create a pair of values that contains two values of type T1 and T2. Please note that QPair does not store pointers to the two elements; it holds a copy of every member. This is why these kinds of classes are called \fIvalue based\fR. If you're interested in \fIpointer based\fR classes see, for example, QPtrList and QDict.
.PP
@ -58,7 +58,7 @@ QPair uses an STL-like syntax to manipulate and address the objects it contains.
.PP
Functions that need to return two values can use a QPair.
.PP
See also Qt Template Library Classes, Implicitly and Explicitly Shared Classes, and Non-GUI Classes.
See also TQt Template Library Classes, Implicitly and Explicitly Shared Classes, and Non-GUI Classes.
.SS "Member Type Documentation"
.SH "QPair::first_type"
The type of the first element in the pair.
@ -88,8 +88,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
@ -107,7 +107,7 @@ QPalette \- Color groups for each widget state
.SH DESCRIPTION
The QPalette class contains color groups for each widget state.
.PP
A palette consists of three color groups: \fIactive\fR, \fIdisabled\fR, and \fIinactive\fR. All widgets contain a palette, and all widgets in Qt use their palette to draw themselves. This makes the user interface easily configurable and easier to keep consistent.
A palette consists of three color groups: \fIactive\fR, \fIdisabled\fR, and \fIinactive\fR. All widgets contain a palette, and all widgets in TQt use their palette to draw themselves. This makes the user interface easily configurable and easier to keep consistent.
.PP
If you create a new widget we strongly recommend that you use the colors in the palette rather than hard-coding specific colors.
.PP
@ -281,8 +281,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
@ -89,7 +89,7 @@ A picture serializes painter commands to an IO device in a platform-independent
.PP
Pictures are called meta-files on some platforms.
.PP
Qt pictures use a proprietary binary format. Unlike native picture (meta-file) formats on many window systems, Qt pictures have no limitations regarding their contents. Everything that can be painted can also be stored in a picture, e.g. fonts, pixmaps, regions, transformed graphics, etc.
Qt pictures use a proprietary binary format. Unlike native picture (meta-file) formats on many window systems, TQt pictures have no limitations regarding their contents. Everything that can be painted can also be stored in a picture, e.g. fonts, pixmaps, regions, transformed graphics, etc.
.PP
QPicture is an implicitly shared class.
.PP
@ -138,19 +138,19 @@ Constructs an empty picture.
.PP
The \fIformatVersion\fR parameter may be used to \fIcreate\fR a QPicture that can be read by applications that are compiled with earlier versions of Qt.
.TP
\fIformatVersion\fR == 1 is binary compatible with Qt 1.x and later.
\fIformatVersion\fR == 1 is binary compatible with TQt 1.x and later.
.TP
\fIformatVersion\fR == 2 is binary compatible with Qt 2.0.x and later.
\fIformatVersion\fR == 2 is binary compatible with TQt 2.0.x and later.
.TP
\fIformatVersion\fR == 3 is binary compatible with Qt 2.1.x and later.
\fIformatVersion\fR == 3 is binary compatible with TQt 2.1.x and later.
.TP
\fIformatVersion\fR == 4 is binary compatible with Qt 3.0.x and later.
\fIformatVersion\fR == 4 is binary compatible with TQt 3.0.x and later.
.TP
\fIformatVersion\fR == 5 is binary compatible with Qt 3.1.
\fIformatVersion\fR == 5 is binary compatible with TQt 3.1.
.PP
Note that the default formatVersion is -1 which signifies the current release, i.e. for Qt 3.1 a formatVersion of 5 is the same as the default formatVersion of -1.
Note that the default formatVersion is -1 which signifies the current release, i.e. for TQt 3.1 a formatVersion of 5 is the same as the default formatVersion of -1.
.PP
Reading pictures generated by earlier versions of Qt is supported and needs no special coding; the format is automatically detected.
Reading pictures generated by earlier versions of TQt is supported and needs no special coding; the format is automatically detected.
.SH "QPicture::QPicture ( const QPicture & pic )"
Constructs a shallow copy of \fIpic\fR.
.SH "QPicture::~QPicture ()"
@ -174,7 +174,7 @@ Loads a picture from the file specified by \fIfileName\fR and returns TRUE if su
.PP
By default, the file will be interpreted as being in the native QPicture format. Specifying the \fIformat\fR string is optional and is only needed for importing picture data stored in a different format.
.PP
Currently, the only external format supported is the W3C SVG format which requires the Qt XML module. The corresponding \fIformat\fR string is "svg".
Currently, the only external format supported is the W3C SVG format which requires the TQt XML module. The corresponding \fIformat\fR string is "svg".
.PP
See also save().
.PP
@ -203,7 +203,7 @@ Saves a picture to the file specified by \fIfileName\fR and returns TRUE if succ
.PP
Specifying the file \fIformat\fR string is optional. It's not recommended unless you intend to export the picture data for use by a third party reader. By default the data will be saved in the native QPicture file format.
.PP
Currently, the only external format supported is the W3C SVG format which requires the Qt XML module. The corresponding \fIformat\fR string is "svg".
Currently, the only external format supported is the W3C SVG format which requires the TQt XML module. The corresponding \fIformat\fR string is "svg".
.PP
See also load().
.PP
@ -243,8 +243,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
@ -210,7 +210,7 @@ Inherited by QBitmap and QCanvasPixmap.
.SH DESCRIPTION
The QPixmap class is an off-screen, pixel-based paint device.
.PP
QPixmap is one of the two classes Qt provides for dealing with images; the other is QImage. QPixmap is designed and optimized for drawing; QImage is designed and optimized for I/O and for direct pixel access/manipulation. There are (slow) functions to convert between QImage and QPixmap: convertToImage() and convertFromImage().
QPixmap is one of the two classes TQt provides for dealing with images; the other is QImage. QPixmap is designed and optimized for drawing; QImage is designed and optimized for I/O and for direct pixel access/manipulation. There are (slow) functions to convert between QImage and QPixmap: convertToImage() and convertFromImage().
.PP
One common use of the QPixmap class is to enable smooth updating of widgets. Whenever something complex needs to be drawn, you can use a pixmap to obtain flicker-free drawing, like this:
.PP
@ -236,7 +236,7 @@ In addition to loading a pixmap from file using load() you can also loadFromData
.PP
Note regarding Windows 95 and 98: on Windows 9x the system crashes if you create more than about 1000 pixmaps, independent of the size of the pixmaps or installed RAM. Windows NT-systems (including 2000, XP and following versions) do not have the same limitation, but depending on the graphics equipment the system will fail to allocate pixmap objects at some point (due to system running out of GDI resources).
.PP
Qt tries to work around the resource limitation. If you set the pixmap optimization to QPixmap::MemoryOptim and the width of your pixmap is less than or equal to 128 pixels, Qt stores the pixmap in a way that is very memory-efficient when there are many pixmaps.
Qt tries to work around the resource limitation. If you set the pixmap optimization to QPixmap::MemoryOptim and the width of your pixmap is less than or equal to 128 pixels, TQt stores the pixmap in a way that is very memory-efficient when there are many pixmaps.
.PP
If your application uses dozens or hundreds of pixmaps (for example on tool bar buttons and in popup menus), and you plan to run it on Windows 95 or Windows 98, we recommend using code like this:
.PP
@ -414,9 +414,9 @@ See also defaultDepth(), isNull(), and QImage::convertDepth().
.SH "void QPixmap::detach ()\fC [virtual]\fR"
This is a special-purpose function that detaches the pixmap from shared pixmap data.
.PP
A pixmap is automatically detached by Qt whenever its contents is about to change. This is done in all QPixmap member functions that modify the pixmap (fill(), resize(), convertFromImage(), load(), etc.), in bitBlt() for the destination pixmap and in QPainter::begin() on a pixmap.
A pixmap is automatically detached by TQt whenever its contents is about to change. This is done in all QPixmap member functions that modify the pixmap (fill(), resize(), convertFromImage(), load(), etc.), in bitBlt() for the destination pixmap and in QPainter::begin() on a pixmap.
.PP
It is possible to modify a pixmap without letting Qt know. You can first obtain the system-dependent handle() and then call system-specific functions (for instance, BitBlt under Windows) that modify the pixmap contents. In such cases, you can call detach() to cut the pixmap loose from other pixmaps that share data with this one.
It is possible to modify a pixmap without letting TQt know. You can first obtain the system-dependent handle() and then call system-specific functions (for instance, BitBlt under Windows) that modify the pixmap contents. In such cases, you can call detach() to cut the pixmap loose from other pixmaps that share data with this one.
.PP
detach() returns immediately if there is just a single reference or if the pixmap has not been initialized yet.
Inserts a copy of the pixmap \fIpm\fR associated with the \fIkey\fR into the cache.
.PP
All pixmaps inserted by the Qt library have a key starting with" $qt", so your own pixmap keys should never begin "$qt".
All pixmaps inserted by the TQt library have a key starting with" $qt", so your own pixmap keys should never begin "$qt".
.PP
When a pixmap is inserted and the cache is about to exceed its limit, it removes pixmaps until there is enough room for the pixmap to be inserted.
.PP
@ -107,7 +107,7 @@ Inserts the pixmap \fIpm\fR associated with \fIkey\fR into the cache. Returns TR
.PP
If this function returns FALSE, you must delete \fIpm\fR yourself.
.PP
If this function returns TRUE, do not use \fIpm\fR afterwards or keep references to it because any other insertions into the cache, whether from anywhere in the application or within Qt itself, could cause the pixmap to be discarded from the cache and the pointer to become invalid.
If this function returns TRUE, do not use \fIpm\fR afterwards or keep references to it because any other insertions into the cache, whether from anywhere in the application or within TQt itself, could cause the pixmap to be discarded from the cache and the pointer to become invalid.
.PP
Due to these dangers, we strongly recommend that you use insert(const QString&, const QPixmap&) instead. \fR
@ -446,15 +446,15 @@ In the example above, pressing Ctrl+O or selecting "Open" from the menu activate
.PP
Some insert functions take a QIconSet parameter to specify the little menu item icon. Note that you can always pass a QPixmap object instead.
.PP
The \fIid\fR specifies the identification number associated with the menu item. Note that only positive values are valid, as a negative value will make Qt select a unique id for the item.
The \fIid\fR specifies the identification number associated with the menu item. Note that only positive values are valid, as a negative value will make TQt select a unique id for the item.
.PP
The \fIindex\fR specifies the position in the menu. The menu item is appended at the end of the list if \fIindex\fR is negative.
.PP
Note that keyboard accelerators in Qt are not application-global, instead they are bound to a certain top-level window. For example, accelerators in QPopupMenu items only work for menus that are associated with a certain window. This is true for popup menus that live in a menu bar since their accelerators will then be installed in the menu bar itself. This also applies to stand-alone popup menus that have a top-level widget in their parentWidget() chain. The menu will then install its accelerator object on that top-level widget. For all other cases use an independent QAccel object.
Note that keyboard accelerators in TQt are not application-global, instead they are bound to a certain top-level window. For example, accelerators in QPopupMenu items only work for menus that are associated with a certain window. This is true for popup menus that live in a menu bar since their accelerators will then be installed in the menu bar itself. This also applies to stand-alone popup menus that have a top-level widget in their parentWidget() chain. The menu will then install its accelerator object on that top-level widget. For all other cases use an independent QAccel object.
.PP
\fBWarning:\fR Be careful when passing a literal 0 to insertItem() because some C++ compilers choose the wrong overloaded function. Cast the 0 to what you mean, e.g. \fC(QObject*)0\fR.
.PP
\fBWarning:\fR On Mac OS X, items that connect to a slot that are inserted into a menubar will not function as we use the native menubar that knows nothing about signals or slots. Instead insert the items into a popup menu and insert the popup menu into the menubar. This may be fixed in a future Qt version.
\fBWarning:\fR On Mac OS X, items that connect to a slot that are inserted into a menubar will not function as we use the native menubar that knows nothing about signals or slots. Instead insert the items into a popup menu and insert the popup menu into the menubar. This may be fixed in a future TQt version.
.PP
Returns the allocated menu identifier number (\fIid\fR if \fIid\fR >= 0).
.PP
@ -687,7 +687,7 @@ An accelerator key consists of a key code and a combination of the modifiers SHI
.PP
Defining an accelerator key produces a text that is added to the menu item; for instance, CTRL + Key_O produces "Ctrl+O". The text is formatted differently for different platforms.
.PP
Note that keyboard accelerators in Qt are not application-global, instead they are bound to a certain top-level window. For example, accelerators in QPopupMenu items only work for menus that are associated with a certain window. This is true for popup menus that live in a menu bar since their accelerators will then be installed in the menu bar itself. This also applies to stand-alone popup menus that have a top-level widget in their parentWidget() chain. The menu will then install its accelerator object on that top-level widget. For all other cases use an independent QAccel object.
Note that keyboard accelerators in TQt are not application-global, instead they are bound to a certain top-level window. For example, accelerators in QPopupMenu items only work for menus that are associated with a certain window. This is true for popup menus that live in a menu bar since their accelerators will then be installed in the menu bar itself. This also applies to stand-alone popup menus that have a top-level widget in their parentWidget() chain. The menu will then install its accelerator object on that top-level widget. For all other cases use an independent QAccel object.
.PP
Example:
.PP
@ -798,8 +798,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
@ -224,7 +224,7 @@ There are also some settings that the user sets (through the printer dialog) and
pageOrder() tells the application program whether to print first-page-first or last-page-first.
.IP
.TP
colorMode() tells the application program whether to print in color or grayscale. (If you print in color and the printer does not support color, Qt will try to approximate. The document may take longer to print, but the quality should not be made visibly poorer.)
colorMode() tells the application program whether to print in color or grayscale. (If you print in color and the printer does not support color, TQt will try to approximate. The document may take longer to print, but the quality should not be made visibly poorer.)
.IP
.TP
fromPage() and toPage() indicate what pages the application program should print.
@ -396,7 +396,7 @@ This enum describes the mode the printer should work in. It basically presets a
.TP
\fCQPrinter::HighResolution\fR - Use printer resolution on windows, set the resolution of the postscript driver to 600dpi.
.TP
\fCQPrinter::Compatible\fR - Almost the same as PrinterResolution, but keeps some peculiarities of the Qt 2.x printer driver. This is useful for applications ported from Qt 2.x to Qt 3.x.
\fCQPrinter::Compatible\fR - Almost the same as PrinterResolution, but keeps some peculiarities of the TQt 2.x printer driver. This is useful for applications ported from TQt 2.x to TQt 3.x.
.SH "QPrinter::PrinterOption"
This enum describes various printer options that appear in the printer setup dialog. It is used to enable and disable these options in the setup dialog.
.TP
@ -671,7 +671,7 @@ Under X11, the \fCPRINTER\fR environment variable defines the default printer. U
Sets the printer to use \fIoption\fR to select the printer. \fIoption\fR is null by default (which implies that Qt should be smart enough to guess correctly), but it can be set to other values to use a specific printer selection option.
Sets the printer to use \fIoption\fR to select the printer. \fIoption\fR is null by default (which implies that TQt should be smart enough to guess correctly), but it can be set to other values to use a specific printer selection option.
.PP
If the printer selection option is changed while the printer is active, the current print job may or may not be affected.
.PP
@ -722,8 +722,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
@ -145,7 +145,7 @@ Both start() and launch() can accept a string list of strings each of which has
.PP
You can test to see if a program is running with isRunning(). The program's process identifier is available from processIdentifier(). If you want to terminate a running program use tryTerminate(), but note that the program may ignore this. If you \fIreally\fR want to terminate the program, without it having any chance to clean up, you can use kill().
.PP
As an example, suppose we want to start the \fCuic\fR command (a Qt command line tool used with \fIQt Designer\fR) and perform some operations on the output (the \fCuic\fR outputs the code it generates to standard output by default). Suppose further that we want to run the program on the file "small_dialog.ui" with the command line options "-tr i18n". On the command line we would write:
As an example, suppose we want to start the \fCuic\fR command (a TQt command line tool used with \fIQt Designer\fR) and perform some operations on the output (the \fCuic\fR outputs the code it generates to standard output by default). Suppose further that we want to run the program on the file "small_dialog.ui" with the command line options "-tr i18n". On the command line we would write:
.PP
.nf
.br
@ -359,7 +359,7 @@ Note that you should not use the slots writeToStdin() and closeStdin() on proces
.PP
The process may or may not read the \fIbuf\fR data sent to its standard input.
.PP
You can call this function even when a process that was started with this instance is still running. Be aware that if you do this the standard input of the process that was launched first will be closed, with any pending data being deleted, and the process will be left to run out of your control. Similarly, if the process could not be started the standard input will be closed and the pending data deleted. (On operating systems that have zombie processes, Qt will also wait() on the old process.)
You can call this function even when a process that was started with this instance is still running. Be aware that if you do this the standard input of the process that was launched first will be closed, with any pending data being deleted, and the process will be left to run out of your control. Similarly, if the process could not be started the standard input will be closed and the pending data deleted. (On operating systems that have zombie processes, TQt will also wait() on the old process.)
.PP
The object emits the signal launchFinished() when this function call is finished. If the start was successful, this signal is emitted after all the data has been written to standard input. If the start failed, then this signal is emitted immediately.
.PP
@ -463,7 +463,7 @@ Returns TRUE if the process could be started; otherwise returns FALSE.
.PP
You can write data to the process's standard input with writeToStdin(). You can close standard input with closeStdin() and you can terminate the process with tryTerminate(), or with kill().
.PP
You can call this function even if you've used this instance to create a another process which is still running. In such cases, QProcess closes the old process's standard input and deletes pending data, i.e., you lose all control over the old process, but the old process is not terminated. This applies also if the process could not be started. (On operating systems that have zombie processes, Qt will also wait() on the old process.)
You can call this function even if you've used this instance to create a another process which is still running. In such cases, QProcess closes the old process's standard input and deletes pending data, i.e., you lose all control over the old process, but the old process is not terminated. This applies also if the process could not be started. (On operating systems that have zombie processes, TQt will also wait() on the old process.)
.PP
See also launch() and closeStdin().
.PP
@ -509,8 +509,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
The QPtrCollection class is the base class of most pointer-based Qt collections.
The QPtrCollection class is the base class of most pointer-based TQt collections.
.PP
The QPtrCollection class is an abstract base class for the Qt collection classes QDict, QPtrList, etc. Qt also includes value based collections, e.g. QValueList, QMap, etc.
The QPtrCollection class is an abstract base class for the TQt collection classes QDict, QPtrList, etc. TQt also includes value based collections, e.g. QValueList, QMap, etc.
.PP
A QPtrCollection only knows about the number of objects in the collection and the deletion strategy (see setAutoDelete()).
.PP
@ -133,8 +133,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
As a general rule, use a push button when the application or dialog window performs an action when the user clicks on it (such as Apply, Cancel, Close and Help) \fIand\fR when the widget is supposed to have a wide, rectangular shape with a text label. Small, typically square buttons that change the state of the window rather than performing an action (such as the buttons in the top-right corner of the QFileDialog) are not command buttons, but tool buttons. Qt provides a special class (QToolButton) for these buttons.
As a general rule, use a push button when the application or dialog window performs an action when the user clicks on it (such as Apply, Cancel, Close and Help) \fIand\fR when the widget is supposed to have a wide, rectangular shape with a text label. Small, typically square buttons that change the state of the window rather than performing an action (such as the buttons in the top-right corner of the QFileDialog) are not command buttons, but tool buttons. TQt provides a special class (QToolButton) for these buttons.
.PP
If you need toggle behavior (see setToggleButton()) or a button that auto-repeats the activation signal when being pushed down like the arrows in a scroll bar (see setAutoRepeat()), a command button is probably not what you want. When in doubt, use a tool button.
.PP
@ -358,7 +358,7 @@ This property holds whether the push button is the auto default button.
.PP
If this property is set to TRUE then the push button is the auto default button in a dialog.
.PP
In some GUI styles a default button is drawn with an extra frame around it, up to 3 pixels or more. Qt automatically keeps this space free around auto-default buttons, i.e. auto-default buttons may have a slightly larger size hint.
In some GUI styles a default button is drawn with an extra frame around it, up to 3 pixels or more. TQt automatically keeps this space free around auto-default buttons, i.e. auto-default buttons may have a slightly larger size hint.
.PP
This property's default is TRUE for buttons that have a QDialog parent; otherwise it defaults to FALSE.
.PP
@ -456,8 +456,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
@ -435,7 +435,7 @@ Coordinate conversion is provided by contentsToViewport() and viewportToContents
.PP
The contentsMoving() signal is emitted just before the contents are moved to a new position.
.PP
\fBWarning:\fR QScrollView currently does not erase the background when resized, i.e. you must always clear the background manually in scrollview subclasses. This will change in a future version of Qt and we recommend specifying the WNoAutoErase flag explicitly.
\fBWarning:\fR QScrollView currently does not erase the background when resized, i.e. you must always clear the background manually in scrollview subclasses. This will change in a future version of TQt and we recommend specifying the WNoAutoErase flag explicitly.
.PP
.ce 1
.B "[Image Omitted]"
@ -901,8 +901,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
@ -77,7 +77,7 @@ The session manager is responsible for session management, most importantly for
.PP
QSessionManager provides an interface between the application and the session manager so that the program can work well with the session manager. In Qt, session management requests for action are handled by the two virtual functions QApplication::commitData() and QApplication::saveState(). Both provide a reference to a session manager object as argument, to allow the application to communicate with the session manager.
.PP
During a session management action (i.e. within commitData() and saveState()), no user interaction is possible \fIunless\fR the application got explicit permission from the session manager. You ask for permission by calling allowsInteraction() or, if it's really urgent, allowsErrorInteraction(). Qt does not enforce this, but the session manager may.
During a session management action (i.e. within commitData() and saveState()), no user interaction is possible \fIunless\fR the application got explicit permission from the session manager. You ask for permission by calling allowsInteraction() or, if it's really urgent, allowsErrorInteraction(). TQt does not enforce this, but the session manager may.
.PP
You can try to abort the shutdown process by calling cancel(). The default commitData() function does this if some top-level window rejected its closeEvent().
.PP
@ -302,8 +302,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
@ -244,7 +244,7 @@ There is no universally accepted place for storing application settings under Un
.TP
\fC/opt/MyCompany/share/MyApplication/etc\fR
.TP
\fC$HOME/.qt\fR When reading settings the files are searched in the order shown above, with later settings overriding earlier settings. Files for which the user doesn't have read permission are ignored. When saving settings QSettings works in the order shown above, writing to the first settings file for which the user has write permission. (\fCINSTALL\fR is the directory where Qt was installed. This can be modified by using the configure script's -prefix argument )
\fC$HOME/.qt\fR When reading settings the files are searched in the order shown above, with later settings overriding earlier settings. Files for which the user doesn't have read permission are ignored. When saving settings QSettings works in the order shown above, writing to the first settings file for which the user has write permission. (\fCINSTALL\fR is the directory where TQt was installed. This can be modified by using the configure script's -prefix argument )
.PP
If you want to put the settings in a particular place in the filesystem you could do this:
.PP
@ -578,7 +578,7 @@ Writes the boolean entry \fIvalue\fR into key \fIkey\fR. The \fIkey\fR is create
.PP
If an error occurs the settings are left unchanged and FALSE is returned; otherwise TRUE is returned.
.PP
\fBWarning:\fR On certain platforms, keys are required to contain at least two components (e.g., "/foo/bar"). This limitation does not apply to Qt 4.
\fBWarning:\fR On certain platforms, keys are required to contain at least two components (e.g., "/foo/bar"). This limitation does not apply to TQt 4.
.PP
See also readListEntry(), readNumEntry(), readDoubleEntry(), readBoolEntry(), and removeEntry().
.PP
@ -642,8 +642,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
@ -62,7 +62,7 @@ QSimpleRichText \- Small displayable piece of rich text
.SH DESCRIPTION
The QSimpleRichText class provides a small displayable piece of rich text.
.PP
This class encapsulates simple rich text usage in which a string is interpreted as rich text and can be drawn. This is particularly useful if you want to display some rich text in a custom widget. A QStyleSheet is needed to interpret the tags and format the rich text. Qt provides a default HTML-like style sheet, but you may define custom style sheets.
This class encapsulates simple rich text usage in which a string is interpreted as rich text and can be drawn. This is particularly useful if you want to display some rich text in a custom widget. A QStyleSheet is needed to interpret the tags and format the rich text. TQt provides a default HTML-like style sheet, but you may define custom style sheets.
.PP
Once created, the rich text object can be queried for its width(), height(), and the actual width used (see widthUsed()). Most importantly, it can be drawn on any given QPainter with draw(). QSimpleRichText can also be used to implement hypertext or active text facilities by using anchorAt(). A hit test through inText() makes it possible to use simple rich text for text objects in editable drawing canvases.
.PP
@ -170,8 +170,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
All the functions in this class are reentrant when Qt is built with thread support.</p>
All the functions in this class are reentrant when TQt is built with thread support.</p>
.PP
\fC#include <ntqsjiscodec.h>\fR
.PP
@ -34,7 +34,7 @@ More precisely, the QSjisCodec class subclasses QTextCodec to provide support fo
.PP
The environment variable \fCUNICODEMAP_JP\fR can be used to fine-tune QJisCodec, QSjisCodec and QEucJpCodec. The QJisCodec documentation describes how to use this variable.
.PP
Most of the code here was written by Serika Kurusugawa, a.k.a. Junji Takagi, and is included in Qt with the author's permission and the grateful thanks of the Trolltech team. Here is the copyright statement for the code as it was at the point of contribution. Trolltech's subsequent modifications are covered by the usual copyright for Qt.
Most of the code here was written by Serika Kurusugawa, a.k.a. Junji Takagi, and is included in TQt with the author's permission and the grateful thanks of the Trolltech team. Here is the copyright statement for the code as it was at the point of contribution. Trolltech's subsequent modifications are covered by the usual copyright for Qt.
.PP
Copyright (C) 1999 Serika Kurusugawa. All rights reserved.
.PP
@ -71,8 +71,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
@ -169,7 +169,7 @@ QSocket inherits QIODevice, and reimplements some functions. In general, you can
.PP
\fBWarning:\fR QSocket is not suitable for use in threads. If you need to uses sockets in threads use the lower-level QSocketDevice class.
.PP
\fBWarning:\fR Because Qt doesn't use the native socketstream implementation on Mac OS X, QSocket has an implicit transfer latency of 100ms. You can achieve lower latency on Mac OS X by using QSocketDevice instead.
\fBWarning:\fR Because TQt doesn't use the native socketstream implementation on Mac OS X, QSocket has an implicit transfer latency of 100ms. You can achieve lower latency on Mac OS X by using QSocketDevice instead.
.PP
See also QSocketDevice, QHostAddress, QSocketNotifier, and Input/Output and Networking.
@ -74,7 +74,7 @@ The behavior of a write notifier that is left in enabled state after having emit
.PP
If you need a time-out for your sockets you can use either timer events or the QTimer class.
.PP
Socket action is detected in the main event loop of Qt. The X11 version of Qt has a single UNIX select() call that incorporates all socket notifiers and the X socket.
Socket action is detected in the main event loop of Qt. The X11 version of TQt has a single UNIX select() call that incorporates all socket notifiers and the X socket.
.PP
Note that on XFree86 for OS/2, select() works only in the thread in which main() is running; you should therefore use that thread for GUI operations.
.PP
@ -145,8 +145,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
@ -321,7 +321,7 @@ This virtual function is used by the spin box whenever it needs to interpret tex
.PP
Subclasses that need to display spin box values in a non-numeric way need to reimplement this function.
.PP
Note that Qt handles specialValueText() separately; this function is only concerned with the other values.
Note that TQt handles specialValueText() separately; this function is only concerned with the other values.
.PP
The default implementation tries to interpret the text() as an integer in the standard way and returns the integer value.
.PP
@ -329,7 +329,7 @@ See also interpretText() and mapValueToText().
.SH "QString QSpinBox::mapValueToText ( int v )\fC [virtual protected]\fR"
This virtual function is used by the spin box whenever it needs to display value \fIv\fR. The default implementation returns a string containing \fIv\fR printed in the standard way. Reimplementations may return anything. (See the example in the detailed description.)
.PP
Note that Qt does not call this function for specialValueText() and that neither prefix() nor suffix() are included in the return value.
Note that TQt does not call this function for specialValueText() and that neither prefix() nor suffix() are included in the return value.
.PP
If you reimplement this, you may also need to reimplement mapTextToValue().
.PP
@ -560,8 +560,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
QSql \- Namespace for Qt SQL identifiers that need to be global-like
QSql \- Namespace for TQt SQL identifiers that need to be global-like
.SH SYNOPSIS
\fC#include <ntqsql.h>\fR
.PP
@ -33,9 +33,9 @@ QSql \- Namespace for Qt SQL identifiers that need to be global-like
.br
.in -1c
.SH DESCRIPTION
The QSql class is a namespace for Qt SQL identifiers that need to be global-like.
The QSql class is a namespace for TQt SQL identifiers that need to be global-like.
.PP
Normally, you can ignore this class. Several Qt SQL classes inherit it, so all the identifiers in the Qt SQL namespace are visible without qualification.
Normally, you can ignore this class. Several TQt SQL classes inherit it, so all the identifiers in the TQt SQL namespace are visible without qualification.
.PP
See also Database Classes.
.SS "Member Type Documentation"
@ -83,7 +83,7 @@ This enum type describes types of tables
\fCQSql::AllTables\fR - All of the above
.SH MEMBER FUNCTION DOCUMENTATION
.SH "QSql::QSql ()"
Constructs a Qt SQL namespace class
Constructs a TQt SQL namespace class
.SH "SEE ALSO"
.BR http://doc.trolltech.com/ntqsql.html
@ -99,8 +99,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
(We assume that \fCqtdir\fR is the directory where Qt is installed.) This will pull in the code that is needed to use the PostgreSQL client library and to instantiate a QPSQLDriver object, assuming that you have the PostgreSQL headers somewhere in your include search path.
(We assume that \fCqtdir\fR is the directory where TQt is installed.) This will pull in the code that is needed to use the PostgreSQL client library and to instantiate a QPSQLDriver object, assuming that you have the PostgreSQL headers somewhere in your include search path.
.PP
.nf
.br
@ -245,7 +245,7 @@ This function is useful if you need to set up the database connection and instan
.br
.fi
.PP
The above code sets up a PostgreSQL connection and instantiates a QPSQLDriver object. Next, addDatabase() is called to add the connection to the known connections so that it can be used by the Qt SQL classes. When a driver is instantiated with a connection handle (or set of handles), Qt assumes that you have already opened the database connection.
The above code sets up a PostgreSQL connection and instantiates a QPSQLDriver object. Next, addDatabase() is called to add the connection to the known connections so that it can be used by the TQt SQL classes. When a driver is instantiated with a connection handle (or set of handles), TQt assumes that you have already opened the database connection.
.PP
Remember that you must link your application against the database client library as well. The simplest way to do this is to add lines like those below to your \fC.pro\fR file:
.PP
@ -288,7 +288,7 @@ Returns TRUE if the list of database connections contains \fIconnectionName\fR;
Returns the database connection called \fIconnectionName\fR. The database connection must have been previously added with addDatabase(). If \fIopen\fR is TRUE (the default) and the database connection is not already open it is opened now. If no \fIconnectionName\fR is specified the default connection is used. If \fIconnectionName\fR does not exist in the list of databases, 0 is returned. The pointer returned is owned by QSqlDatabase and should \fInot\fR be deleted.
.PP
\fBWarning:\fR There are restrictions on the use of database connections in threaded applications. Please see the Thread Support in Qt document for more information about threading and SQL databases.
\fBWarning:\fR There are restrictions on the use of database connections in threaded applications. Please see the Thread Support in TQt document for more information about threading and SQL databases.
.PP
Examples:
.)l sql/overview/basicbrowsing/main.cpp and sql/overview/create_connections/main.cpp.
@ -654,8 +654,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
@ -31,7 +31,7 @@ The QSqlDriverPlugin class provides an abstract base for custom QSqlDriver plugi
.PP
The SQL driver plugin is a simple plugin interface that makes it easy to create your own SQL driver plugins that can be loaded dynamically by Qt.
.PP
Writing a SQL plugin is achieved by subclassing this base class, reimplementing the pure virtual functions keys() and create(), and exporting the class with the \fCQ_EXPORT_PLUGIN\fR macro. See the SQL plugins that come with Qt for example implementations (in the \fCplugins/src/sqldrivers\fR subdirectory of the source distribution). Read the plugins documentation for more information on plugins.
Writing a SQL plugin is achieved by subclassing this base class, reimplementing the pure virtual functions keys() and create(), and exporting the class with the \fCQ_EXPORT_PLUGIN\fR macro. See the SQL plugins that come with TQt for example implementations (in the \fCplugins/src/sqldrivers\fR subdirectory of the source distribution). Read the plugins documentation for more information on plugins.
.PP
See also Plugins.
.SH MEMBER FUNCTION DOCUMENTATION
@ -40,7 +40,7 @@ Constructs a SQL driver plugin. This is invoked automatically by the \fCQ_EXPORT
.SH "QSqlDriverPlugin::~QSqlDriverPlugin ()"
Destroys the SQL driver plugin.
.PP
You never have to call this explicitly. Qt destroys a plugin automatically when it is no longer used.
You never have to call this explicitly. TQt destroys a plugin automatically when it is no longer used.
@ -152,7 +152,7 @@ Some sample code to initialize a form successfully:
.PP
If you want to use custom editors for displaying and editing data fields, you must install a custom QSqlPropertyMap. The form uses this object to get or set the value of a widget.
.PP
Note that Qt Designer provides a visual means of creating data-aware forms.
Note that TQt Designer provides a visual means of creating data-aware forms.
.PP
See also installPropertyMap(), QSqlPropertyMap, and Database Classes.
.SH MEMBER FUNCTION DOCUMENTATION
@ -232,8 +232,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
@ -44,7 +44,7 @@ QSqlPropertyMap \- Used to map widgets to SQL fields
.SH DESCRIPTION
The QSqlPropertyMap class is used to map widgets to SQL fields.
.PP
The SQL module uses Qt object properties to insert and extract values from editor widgets.
The SQL module uses TQt object properties to insert and extract values from editor widgets.
.PP
This class is used to map editors to SQL fields. This works by associating SQL editor class names to the properties used to insert and extract values to/from the editor.
.PP
@ -121,7 +121,7 @@ See also QDataTable, QSqlForm, QSqlEditorFactory, and Database Classes.
.SH "QSqlPropertyMap::QSqlPropertyMap ()"
Constructs a QSqlPropertyMap.
.PP
The default property mappings used by Qt widgets are: <center>.nf
The default property mappings used by TQt widgets are: <center>.nf
.TS
l - l. Widgets Property QCheckBox, QRadioButton checked QComboBox, QListBox currentItem QDateEdit date QDateTimeEdit dateTime QTextBrowser source QButton, QDial, QLabel, QLineEdit, QMultiLineEdit, QPushButton, QTextEdit, text QTimeEdit time QLCDNumber, QScrollBar QSlider, QSpinBox
.TE
@ -160,8 +160,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
To access the data returned by a query, use the value() method. Each field in the data returned by a SELECT statement is accessed by passing the field's position in the statement, starting from 0. Information about the fields can be obtained via QSqlDatabase::record(). For the sake of efficiency there are no functions to access a field by name. (The QSqlCursor class provides a higher-level interface with field access by name and automatic SQL generation.)
.PP
QSqlQuery supports prepared query execution and the binding of parameter values to placeholders. Some databases don't support these features, so for them Qt emulates the required functionality. For example, the Oracle and ODBC drivers have proper prepared query support, and Qt makes use of it; but for databases that don't have this support, Qt implements the feature itself, e.g. by replacing placeholders with actual values when a query is executed. The exception is positional binding using named placeholders, which requires that the database supports prepared queries.
QSqlQuery supports prepared query execution and the binding of parameter values to placeholders. Some databases don't support these features, so for them TQt emulates the required functionality. For example, the Oracle and ODBC drivers have proper prepared query support, and TQt makes use of it; but for databases that don't have this support, TQt implements the feature itself, e.g. by replacing placeholders with actual values when a query is executed. The exception is positional binding using named placeholders, which requires that the database supports prepared queries.
.PP
Oracle databases identify placeholders by using a colon-name syntax, e.g \fC:name\fR. ODBC simply uses \fC?\fR characters. Qt supports both syntaxes (although you can't mix them in the same query).
Oracle databases identify placeholders by using a colon-name syntax, e.g \fC:name\fR. ODBC simply uses \fC?\fR characters. TQt supports both syntaxes (although you can't mix them in the same query).
.PP
Below we present the same example using each of the four different binding approaches.
.PP
@ -555,8 +555,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
The QSqlSelectCursor class provides browsing of general SQL SELECT statements.
.PP
QSqlSelectCursor is a convenience class that makes it possible to display result sets from general SQL \fCSELECT\fR statements in data-aware Qt widgets. QSqlSelectCursor is read-only and does not support \fCINSERT\fR, \fCUPDATE\fR or \fCDELETE\fR operations.
QSqlSelectCursor is a convenience class that makes it possible to display result sets from general SQL \fCSELECT\fR statements in data-aware TQt widgets. QSqlSelectCursor is read-only and does not support \fCINSERT\fR, \fCUPDATE\fR or \fCDELETE\fR operations.
.PP
Pass the query in at construction time, or use the QSqlSelectCursor::exec() function.
.PP
@ -79,8 +79,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
QString \- Abstraction of Unicode text and the classic C '\0'-terminated char array
.SH SYNOPSIS
All the functions in this class are reentrant when Qt is built with thread support.</p>
All the functions in this class are reentrant when TQt is built with thread support.</p>
.PP
\fC#include <ntqstring.h>\fR
.PP
@ -945,7 +945,7 @@ This is an overloaded member function, provided for convenience. It behaves esse
.PP
Lexically compares this string with \fIs\fR and returns an integer less than, equal to, or greater than zero if it is less than, equal to, or greater than \fIs\fR.
.SH "void QString::compose ()"
\fBWarning:\fR This function is not supported in Qt 3.x. It is provided for experimental and illustrative purposes only. It is mainly of interest to those experimenting with Arabic and other composition-rich texts.
\fBWarning:\fR This function is not supported in TQt 3.x. It is provided for experimental and illustrative purposes only. It is mainly of interest to those experimenting with Arabic and other composition-rich texts.
.PP
Applies possible ligatures to a QString. Useful when composition-rich text requires rendering with glyph-poor fonts, but it also makes compositions such as QChar(0x0041) ('A') and QChar(0x0308) (Unicode accent diaresis), giving QChar(0x00c4) (German A Umlaut).
.SH "QChar QString::constref ( uint i ) const"
@ -1018,13 +1018,13 @@ See also find() and findRev().
.SH "QString QString::copy () const"
\fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
.PP
In Qt 2.0 and later, all calls to this function are needless. Just remove them.
In TQt 2.0 and later, all calls to this function are needless. Just remove them.
.SH "const char * QString::data () const"
\fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
.PP
Returns a pointer to a '\0'-terminated classic C string.
.PP
In Qt 1.x, this returned a char* allowing direct manipulation of the string as a sequence of bytes. In Qt 2.x where QString is a Unicode string, char* conversion constructs a temporary string, and hence direct character operations are meaningless.
In TQt 1.x, this returned a char* allowing direct manipulation of the string as a sequence of bytes. In TQt 2.x where QString is a Unicode string, char* conversion constructs a temporary string, and hence direct character operations are meaningless.
Returns TRUE if the string ends with \fIs\fR; otherwise returns FALSE.
.PP
@ -1460,7 +1460,7 @@ Returns ascii(). Be sure to see the warnings documented in the ascii() function.
.SH "QString::operator std::string () const"
Returns ascii() as a std::string.
.PP
\fBWarning:\fR The function may cause an application to crash if a static C run-time is in use. This can happen in Microsoft Visual C++ if Qt is configured as single-threaded. A safe alternative is to call ascii() directly and construct a std::string manually.
\fBWarning:\fR The function may cause an application to crash if a static C run-time is in use. This can happen in Microsoft Visual C++ if TQt is configured as single-threaded. A safe alternative is to call ascii() directly and construct a std::string manually.
.SH "bool QString::operator! () const"
Returns TRUE if this is a null string; otherwise returns FALSE.
.PP
@ -1688,7 +1688,7 @@ If \fIindex\fR is beyond the length of the string, nothing is deleted and \fIs\f
.br
.fi
.PP
\fBWarning:\fR Qt 3.3.3 and earlier had different semantics for the case \fIindex\fR >= length(), which contradicted the documentation. To avoid portability problems between Qt 3 versions and with Qt 4, we recommend that you never call the function with \fIindex\fR >= length().
\fBWarning:\fR TQt 3.3.3 and earlier had different semantics for the case \fIindex\fR >= length(), which contradicted the documentation. To avoid portability problems between TQt 3 versions and with TQt 4, we recommend that you never call the function with \fIindex\fR >= length().
.PP
See also insert() and remove().
.PP
@ -1960,7 +1960,7 @@ See also isNull() and isEmpty().
.PP
Sets the character at position \fIindex\fR to \fIc\fR and expands the string if necessary, filling with spaces.
.PP
This method is redundant in Qt 3.x, because operator[] will expand the string as necessary.
This method is redundant in TQt 3.x, because operator[] will expand the string as necessary.
.SH "QString & QString::setLatin1 ( const char * str, int len = -1 )"
Sets this string to \fIstr\fR, interpreted as a classic Latin-1 C string. If \fIlen\fR is -1 (the default), then it is set to strlen(str).
.PP
@ -2541,8 +2541,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
All the functions in this class are reentrant when Qt is built with thread support.</p>
All the functions in this class are reentrant when TQt is built with thread support.</p>
.PP
\fC#include <ntqstringlist.h>\fR
.PP
@ -69,7 +69,7 @@ Inherits QValueList<QString>.
.SH DESCRIPTION
The QStringList class provides a list of strings.
.PP
It is used to store and manipulate strings that logically belong together. Essentially QStringList is a QValueList of QString objects. Unlike QStrList, which stores pointers to characters, QStringList holds real QString objects. It is the class of choice whenever you work with Unicode strings. QStringList is part of the Qt Template Library.
It is used to store and manipulate strings that logically belong together. Essentially QStringList is a QValueList of QString objects. Unlike QStrList, which stores pointers to characters, QStringList holds real QString objects. It is the class of choice whenever you work with Unicode strings. QStringList is part of the TQt Template Library.
.PP
Like QString itself, QStringList objects are implicitly shared, so passing them around as value-parameters is both fast and safe.
.PP
@ -107,7 +107,7 @@ String lists have an iterator, QStringList::Iterator(), e.g.
.br
.fi
.PP
Many Qt functions return string lists by value; to iterate over these you should make a copy and iterate over the copy.
Many TQt functions return string lists by value; to iterate over these you should make a copy and iterate over the copy.
.PP
You can concatenate all the strings in a string list into a single string (with an optional separator) using join(), e.g.
.PP
@ -275,7 +275,7 @@ Examples:
.SH "void QStringList::sort ()"
Sorts the list of strings in ascending case-sensitive order.
.PP
Sorting is very fast. It uses the Qt Template Library's efficient HeapSort implementation that has a time complexity of O(n*log n).
Sorting is very fast. It uses the TQt Template Library's efficient HeapSort implementation that has a time complexity of O(n*log n).
.PP
If you want to sort your strings in an arbitrary order consider using a QMap. For example you could use a QMap<QString,QString> to create a case-insensitive ordering (e.g. mapping the lowercase text to the text), or a QMap<int,QString> to sort the strings by some integer index, etc.
.PP
@ -324,8 +324,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
@ -139,7 +139,7 @@ A large number of GUI elements are common to many widgets. The QStyle class allo
.PP
Although it is not possible to fully enumerate the look of graphical elements and the feel of widgets in a GUI, QStyle provides a considerable amount of control and customisability.
.PP
In Qt 1.x the look and feel option for widgets was specified by a single value: the GUIStyle. Starting with Qt 2.0, this notion was expanded to allow the look to be specified by virtual drawing functions.
In TQt 1.x the look and feel option for widgets was specified by a single value: the GUIStyle. Starting with TQt 2.0, this notion was expanded to allow the look to be specified by virtual drawing functions.
.PP
Derived classes may reimplement some or all of the drawing functions to modify the look of all widgets that use those functions.
.PP
@ -147,7 +147,7 @@ Languages written from right to left (such as Arabic and Hebrew) usually also mi
.PP
The actual reverse layout is performed automatically when possible. However, for the sake of flexibility, the translation cannot be performed everywhere. The documentation for each function in the QStyle API states whether the function expects/returns logical or screen coordinates. Using logical coordinates (in ComplexControls, for example) provides great flexibility in controlling the look of a widget. Use visualRect() when necessary to translate logical coordinates into screen coordinates for drawing.
.PP
In Qt versions prior to 3.0, if you wanted a low level route into changing the appearance of a widget, you would reimplement polish(). With the new 3.0 style engine the recommended approach is to reimplement the draw functions, for example drawItem(), drawPrimitive(), drawControl(), drawControlMask(), drawComplexControl() and drawComplexControlMask(). Each of these functions is called with a range of parameters that provide information that you can use to determine how to draw them, e.g. style flags, rectangle, color group, etc.
In TQt versions prior to 3.0, if you wanted a low level route into changing the appearance of a widget, you would reimplement polish(). With the new 3.0 style engine the recommended approach is to reimplement the draw functions, for example drawItem(), drawPrimitive(), drawControl(), drawControlMask(), drawComplexControl() and drawComplexControlMask(). Each of these functions is called with a range of parameters that provide information that you can use to determine how to draw them, e.g. style flags, rectangle, color group, etc.
.PP
For information on changing elements of an existing style or creating your own style see the Style overview.
.PP
@ -948,7 +948,7 @@ Initializes the appearance of a widget.
.PP
This function is called for every widget at some point after it has been fully created but just \fIbefore\fR it is shown the very first time.
.PP
Reasonable actions in this function might be to call QWidget::setBackgroundMode() for the widget. An example of highly unreasonable use would be setting the geometry! Reimplementing this function gives you a back-door through which you can change the appearance of a widget. With Qt 3.0's style engine you will rarely need to write your own polish(); instead reimplement drawItem(), drawPrimitive(), etc.
Reasonable actions in this function might be to call QWidget::setBackgroundMode() for the widget. An example of highly unreasonable use would be setting the geometry! Reimplementing this function gives you a back-door through which you can change the appearance of a widget. With TQt 3.0's style engine you will rarely need to write your own polish(); instead reimplement drawItem(), drawPrimitive(), etc.
.PP
The QWidget::inherits() function may provide enough information to allow class-specific customizations. But be careful not to hard-code things too much because new QStyle subclasses are expected to work reasonably with all current and \fIfuture\fR widgets.
.PP
@ -1077,8 +1077,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
@ -115,7 +115,7 @@ The QStyleOption class specifies optional parameters for QStyle functions.
.PP
Some QStyle functions take an optional argument specifying extra information that is required for a paritical primitive or control. So that the QStyle class can be extended, QStyleOption is used to provide a variable-argument for these options.
.PP
The QStyleOption class has constructors for each type of optional argument, and this set of constructors may be extended in future Qt releases. There are also corresponding access functions that return the optional arguments: these too may be extended.
The QStyleOption class has constructors for each type of optional argument, and this set of constructors may be extended in future TQt releases. There are also corresponding access functions that return the optional arguments: these too may be extended.
.PP
For each constructor, you should refer to the documentation of the QStyle functions to see the meaning of the arguments.
.PP
@ -210,8 +210,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
The Qt class is a namespace for miscellaneous identifiers that need to be global-like.
The TQt class is a namespace for miscellaneous identifiers that need to be global-like.
.PP
Normally, you can ignore this class. QObject and a few other classes inherit it, so all the identifiers in the Qt namespace are normally usable without qualification.
Normally, you can ignore this class. QObject and a few other classes inherit it, so all the identifiers in the TQt namespace are normally usable without qualification.
.PP
However, you may occasionally need to say \fCQt::black\fR instead of just \fCblack\fR, particularly in static utility functions (such as many class factories).
.PP
@ -355,7 +355,7 @@ ArrowCursor is the default for widgets in a normal state.
</center>
.SH "Qt::DateFormat"
.TP
\fCQt::TextDate\fR - (default) Qt format
\fCQt::TextDate\fR - (default) TQt format
.TP
\fCQt::ISODate\fR - ISO 8601 extended format (YYYY-MM-DD, or with time, YYYY-MM-DDTHH:MM:SS)
.TP
@ -1034,7 +1034,7 @@ This enum type describes the keyboard modifier keys supported by Qt.
.TP
\fCQt::MODIFIER_MASK\fR - is a mask of Shift, Ctrl, Alt and Meta.
.TP
\fCQt::UNICODE_ACCEL\fR - the accelerator is specified as a Unicode code point, not as a Qt Key.
\fCQt::UNICODE_ACCEL\fR - the accelerator is specified as a Unicode code point, not as a TQt Key.
.SH "Qt::Orientation"
This type is used to signify an object's orientation.
.TP
@ -1280,13 +1280,13 @@ There are also a number of flags which you can use to customize the appearance o
.PP
Modifier flags:
.TP
\fCQt::WDestructiveClose\fR - makes Qt delete this widget when the widget has accepted closeEvent(), or when the widget tried to ignore closeEvent() but could not.
\fCQt::WDestructiveClose\fR - makes TQt delete this widget when the widget has accepted closeEvent(), or when the widget tried to ignore closeEvent() but could not.
.TP
\fCQt::WPaintDesktop\fR - gives this widget paint events for the desktop.
.TP
\fCQt::WPaintUnclipped\fR - makes all painters operating on this widget unclipped. Children of this widget or other widgets in front of it do not clip the area the painter can paint on.
.TP
\fCQt::WPaintClever\fR - indicates that Qt should \fInot\fR try to optimize repainting for the widget, but instead pass on window system repaint events directly. (This tends to produce more events and smaller repaint regions.)
\fCQt::WPaintClever\fR - indicates that TQt should \fInot\fR try to optimize repainting for the widget, but instead pass on window system repaint events directly. (This tends to produce more events and smaller repaint regions.)
.TP
\fCQt::WMouseNoMask\fR - indicates that even if the widget has a mask, it wants mouse events for its entire rectangle.
.TP
@ -1439,8 +1439,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
The QTabBar class provides a tab bar, e.g. for use in tabbed dialogs.
.PP
QTabBar is straightforward to use; it draws the tabs using one of the predefined shapes, and emits a signal when a tab is selected. It can be subclassed to tailor the look and feel. Qt also provides a ready-made QTabWidget and a QTabDialog.
QTabBar is straightforward to use; it draws the tabs using one of the predefined shapes, and emits a signal when a tab is selected. It can be subclassed to tailor the look and feel. TQt also provides a ready-made QTabWidget and a QTabDialog.
.PP
The choice of tab shape is a matter of taste, although tab dialogs (for preferences and similar) invariably use RoundedAbove; nobody uses TriangularAbove. Tab controls in windows other than dialogs almost always use either RoundedBelow or TriangularBelow. Many spreadsheets and other tab controls in which all the pages are essentially similar use TriangularBelow, whereas RoundedBelow is used mostly when the pages are different (e.g. a multi-page tool palette).
.PP
@ -320,8 +320,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
@ -76,7 +76,7 @@ A tablet event contains a special accept flag that indicates whether the receive
.PP
The QWidget::setEnabled() function can be used to enable or disable mouse and keyboard events for a widget.
.PP
The event handler QWidget::tabletEvent() receives all three types of tablet events. Qt will first send a tabletEvent and then, if it is not accepted, it will send a mouse event. This allows applications that don't utilize tablets to use a tablet like a mouse while also enabling those who want to use both tablets and mouses differently.
The event handler QWidget::tabletEvent() receives all three types of tablet events. TQt will first send a tabletEvent and then, if it is not accepted, it will send a mouse event. This allows applications that don't utilize tablets to use a tablet like a mouse while also enabling those who want to use both tablets and mouses differently.
.PP
See also Event Classes.
.SS "Member Type Documentation"
@ -180,8 +180,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
Almost all the functions in this class are reentrant when Qt is built with thread support. The exceptions are \fB~QTextCodec\fR(), \fBsetCodecForTr\fR(), \fBsetCodecForCStrings\fR(), and \fBQTextCodec\fR(). </p>
Almost all the functions in this class are reentrant when TQt is built with thread support. The exceptions are \fB~QTextCodec\fR(), \fBsetCodecForTr\fR(), \fBsetCodecForCStrings\fR(), and \fBQTextCodec\fR(). </p>
.PP
\fC#include <ntqtextcodec.h>\fR
.PP
@ -273,7 +273,7 @@ The approach to use in these situations is to create a QTextDecoder object for t
.PP
The QTextDecoder object maintains state between chunks and therefore works correctly even if a multi-byte character is split between chunks.
.SH "Creating your own Codec class"
Support for new text encodings can be added to Qt by creating QTextCodec subclasses.
Support for new text encodings can be added to TQt by creating QTextCodec subclasses.
.PP
Built-in codecs can be overridden by custom codecs since more recently created QTextCodec objects take precedence over earlier ones.
.PP
@ -344,7 +344,7 @@ Finally, you must implement:
.fi
Gives a value indicating how likely it is that \fIlen\fR characters from \fIchars\fR are in the encoding.
.PP
A good model for this function is the QWindowsLocalCodec::heuristicContentMatch function found in the Qt sources.
A good model for this function is the QWindowsLocalCodec::heuristicContentMatch function found in the TQt sources.
.PP
A QTextCodec subclass might have improved performance if you also re-implement:
.PP
@ -376,7 +376,7 @@ See also Internationalization with Qt.
.SH "QTextCodec::QTextCodec ()\fC [protected]\fR"
\fBWarning:\fR This function is \fInot\fR reentrant.</p>
.PP
Constructs a QTextCodec, and gives it the highest precedence. The QTextCodec should always be constructed on the heap (i.e. with \fCnew\fR). Qt takes ownership and will delete it when the application terminates.
Constructs a QTextCodec, and gives it the highest precedence. The QTextCodec should always be constructed on the heap (i.e. with \fCnew\fR). TQt takes ownership and will delete it when the application terminates.
.SH "QTextCodec::~QTextCodec ()\fC [virtual]\fR"
\fBWarning:\fR This function is \fInot\fR reentrant.</p>
.PP
@ -458,7 +458,7 @@ Reads a POSIX2 charmap definition from \fIiod\fR. The parser recognizes the foll
.PP
The resulting QTextCodec is returned (and also added to the global list of codecs). The name() of the result is taken from the code_set_name.
.PP
Note that a codec constructed in this way uses much more memory and is slower than a hand-written QTextCodec subclass, since tables in code are kept in memory shared by all Qt applications.
Note that a codec constructed in this way uses much more memory and is slower than a hand-written QTextCodec subclass, since tables in code are kept in memory shared by all TQt applications.
.PP
See also loadCharmapFile().
.PP
@ -530,7 +530,7 @@ If the literal quoted text in the program is not in the Latin-1 encoding, this f
.br
.fi
.PP
Note that this is not the way to select the encoding that the \fIuser\fR has chosen. For example, to convert an application containing literal English strings to Korean, all that is needed is for the English strings to be passed through tr() and for translation files to be loaded. For details of internationalization, see the Qt internationalization documentation.
Note that this is not the way to select the encoding that the \fIuser\fR has chosen. For example, to convert an application containing literal English strings to Korean, all that is needed is for the English strings to be passed through tr() and for translation files to be loaded. For details of internationalization, see the TQt internationalization documentation.
QTextCodecPlugin \- Abstract base for custom QTextCodec plugins
.SH SYNOPSIS
All the functions in this class are reentrant when Qt is built with thread support.</p>
All the functions in this class are reentrant when TQt is built with thread support.</p>
.PP
\fC#include <ntqtextcodecplugin.h>\fR
.PP
@ -39,7 +39,7 @@ The QTextCodecPlugin class provides an abstract base for custom QTextCodec plugi
.PP
The text codec plugin is a simple plugin interface that makes it easy to create custom text codecs that can be loaded dynamically into applications.
.PP
Writing a text codec plugin is achieved by subclassing this base class, reimplementing the pure virtual functions names(), createForName(), mibEnums() and createForMib(), and exporting the class with the \fCQ_EXPORT_PLUGIN\fR macro. See the Qt Plugins documentation for details.
Writing a text codec plugin is achieved by subclassing this base class, reimplementing the pure virtual functions names(), createForName(), mibEnums() and createForMib(), and exporting the class with the \fCQ_EXPORT_PLUGIN\fR macro. See the TQt Plugins documentation for details.
.PP
See the IANA character-sets encoding file for more information on mime names and mib enums.
.PP
@ -50,7 +50,7 @@ Constructs a text codec plugin. This is invoked automatically by the \fCQ_EXPORT
.SH "QTextCodecPlugin::~QTextCodecPlugin ()"
Destroys the text codec plugin.
.PP
You never have to call this explicitly. Qt destroys a plugin automatically when it is no longer used.
You never have to call this explicitly. TQt destroys a plugin automatically when it is no longer used.
.SH "QTextCodec * QTextCodecPlugin::createForMib ( int mib )\fC [pure virtual]\fR"
Creates a QTextCodec object for the mib enum \fImib\fR.
.PP
@ -84,8 +84,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
@ -537,7 +537,7 @@ l - l. Mode Command Notes Plain Text Editor setTextFormat(PlainText) Set text wi
.fi
</center>
.PP
<sup>1.</sup><small>A more complete API that supports setting margins, images, etc., is planned for a later Qt release.</small>
<sup>1.</sup><small>A more complete API that supports setting margins, images, etc., is planned for a later TQt release.</small>
.PP
QTextEdit can be used as a syntax highlighting editor when used in conjunction with QSyntaxHighlighter.
.PP
@ -557,7 +557,7 @@ If you want a text browser with more navigation use QTextBrowser. If you just ne
.PP
If you create a new QTextEdit, and want to allow the user to edit rich text, call setTextFormat(Qt::RichText) to ensure that the text is treated as rich text. (Rich text uses HTML tags to set text formatting attributes. See QStyleSheet for information on the HTML tags that are supported.). If you don't call setTextFormat() explicitly the text edit will guess from the text itself whether it is rich text or plain text. This means that if the text looks like HTML or XML it will probably be interpreted as rich text, so you should call setTextFormat(Qt::PlainText) to preserve such text.
.PP
Note that we do not intend to add a full-featured web browser widget to Qt (because that would easily double Qt's size and only a few applications would benefit from it). The rich text support in Qt is designed to provide a fast, portable and efficient way to add reasonable online help facilities to applications, and to provide a basis for rich text editors.
Note that we do not intend to add a full-featured web browser widget to TQt (because that would easily double Qt's size and only a few applications would benefit from it). The rich text support in TQt is designed to provide a fast, portable and efficient way to add reasonable online help facilities to applications, and to provide a basis for rich text editors.
.SH "Using QTextEdit as a Display Widget"
QTextEdit can display a large HTML subset, including tables and images.
.PP
@ -674,7 +674,7 @@ If the text changes, the textChanged() signal is emitted, and if the user insert
.PP
QTextEdit provides command-based undo and redo. To set the depth of the command history use setUndoDepth() which defaults to 100 steps. To undo or redo the last operation call undo() or redo(). The signals undoAvailable() and redoAvailable() indicate whether the undo and redo operations can be executed.
.PP
The indent() function is used to reindent a paragraph. It is useful for code editors, for example in Qt Designer's code editor \fICtrl+I\fR invokes the indent() function.
The indent() function is used to reindent a paragraph. It is useful for code editors, for example in TQt Designer's code editor \fICtrl+I\fR invokes the indent() function.
.PP
<h4> Editing key bindings </h4>
.PP
@ -1292,7 +1292,7 @@ This property holds the enabled set of auto formatting features.
.PP
The value can be any combination of the values in the AutoFormatting enum. The default is AutoAll. Choose AutoNone to disable all automatic formatting.
.PP
Currently, the only automatic formatting feature provided is AutoBulletList; future versions of Qt may offer more.
Currently, the only automatic formatting feature provided is AutoBulletList; future versions of TQt may offer more.
.PP
Set this property's value with setAutoFormatting() and get this property's value with autoFormatting().
.SH "QString documentTitle"
@ -1440,8 +1440,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
@ -84,13 +84,13 @@ This can be used to do heavy work while providing a snappy user interface:
.br
.fi
.PP
myObject->processOneThing() will be called repeatedly and should return quickly (typically after processing one data item) so that Qt can deliver events to widgets and stop the timer as soon as it has done all its work. This is the traditional way of implementing heavy work in GUI applications; multi-threading is now becoming available on more and more platforms, and we expect that null events will eventually be replaced by threading.
myObject->processOneThing() will be called repeatedly and should return quickly (typically after processing one data item) so that TQt can deliver events to widgets and stop the timer as soon as it has done all its work. This is the traditional way of implementing heavy work in GUI applications; multi-threading is now becoming available on more and more platforms, and we expect that null events will eventually be replaced by threading.
.PP
Note that QTimer's accuracy depends on the underlying operating system and hardware. Most platforms support an accuracy of 20ms; some provide more. If Qt is unable to deliver the requested number of timer clicks, it will silently discard some.
Note that QTimer's accuracy depends on the underlying operating system and hardware. Most platforms support an accuracy of 20ms; some provide more. If TQt is unable to deliver the requested number of timer clicks, it will silently discard some.
.PP
An alternative to using QTimer is to call QObject::startTimer() for your object and reimplement the QObject::timerEvent() event handler in your class (which must, of course, inherit QObject). The disadvantage is that timerEvent() does not support such high-level features as single-shot timers or signals.
.PP
Some operating systems limit the number of timers that may be used; Qt tries to work around these limitations.
Some operating systems limit the number of timers that may be used; TQt tries to work around these limitations.
.PP
See also Event Classes and Time and Date.
.SH MEMBER FUNCTION DOCUMENTATION
@ -184,8 +184,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
@ -73,7 +73,7 @@ This extract from the application/application.cpp example shows the creation of
.PP
You may use most widgets within a toolbar, with QToolButton and QComboBox being the most common.
.PP
If you create a new widget on an already visible QToolBar, this widget will automatically become visible without needing a show() call. (This differs from every other Qt widget container. We recommend calling show() anyway since we hope to fix this anomaly in a future release.)
If you create a new widget on an already visible QToolBar, this widget will automatically become visible without needing a show() call. (This differs from every other TQt widget container. We recommend calling show() anyway since we hope to fix this anomaly in a future release.)
.PP
QToolBars, like QDockWindows, are located in QDockAreas or float as top-level windows. QMainWindow provides four QDockAreas (top, left, right and bottom). When you create a new toolbar (as in the example above) as a child of a QMainWindow the toolbar will be added to the top dock area. You can move it to another dock area (or float it) by calling QMainWindow::moveDockWindow(). QDock areas lay out their windows in Lines.
.PP
@ -151,8 +151,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
@ -214,7 +214,7 @@ This is an overloaded member function, provided for convenience. It behaves esse
.PP
\fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
.PP
Since Qt 3.0, QIconSet contains both the On and Off icons.
Since TQt 3.0, QIconSet contains both the On and Off icons.
.PP
For ease of porting, this function ignores the \fIon\fR parameter and returns the iconSet property. If you relied on the \fIon\fR parameter, you probably want to update your code to use the QIconSet On/Off mechanism.
.SH "QIconSet QToolButton::offIconSet () const"
@ -238,7 +238,7 @@ This is an overloaded member function, provided for convenience. It behaves esse
.PP
\fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
.PP
Since Qt 3.0, QIconSet contains both the On and Off icons.
Since TQt 3.0, QIconSet contains both the On and Off icons.
.PP
For ease of porting, this function ignores the \fIon\fR parameter and sets the iconSet property. If you relied on the \fIon\fR parameter, you probably want to update your code to use the QIconSet On/Off mechanism.
.PP
@ -317,7 +317,7 @@ This property holds the icon set that is used when the button is in an "off" sta
.PP
\fBThis property is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
.PP
Since Qt 3.0, QIconSet contains both the On and Off icons. There is now an QToolButton::iconSet property that replaces both QToolButton::onIconSet and QToolButton::offIconSet.
Since TQt 3.0, QIconSet contains both the On and Off icons. There is now an QToolButton::iconSet property that replaces both QToolButton::onIconSet and QToolButton::offIconSet.
.PP
For ease of porting, this property is a synonym for QToolButton::iconSet. You probably want to go over your application code and use the QIconSet On/Off mechanism.
.PP
@ -337,7 +337,7 @@ This property holds the icon set that is used when the button is in an "on" stat
.PP
\fBThis property is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
.PP
Since Qt 3.0, QIconSet contains both the On and Off icons. There is now an QToolButton::iconSet property that replaces both QToolButton::onIconSet and QToolButton::offIconSet.
Since TQt 3.0, QIconSet contains both the On and Off icons. There is now an QToolButton::iconSet property that replaces both QToolButton::onIconSet and QToolButton::offIconSet.
.PP
For ease of porting, this property is a synonym for QToolButton::iconSet. You probably want to go over your application code and use the QIconSet On/Off mechanism.
.PP
@ -407,8 +407,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
@ -75,7 +75,7 @@ The QTranslator class provides internationalization support for text output.
.PP
An object of this class contains a set of QTranslatorMessage objects, each of which specifies a translation from a source language to a target language. QTranslator provides functions to look up translations, add new ones, remove them, load and save them, etc.
.PP
The most common use of QTranslator is to: load a translator file created with Qt Linguist, install it using QApplication::installTranslator(), and use it via QObject::tr(). For example:
The most common use of QTranslator is to: load a translator file created with TQt Linguist, install it using QApplication::installTranslator(), and use it via QObject::tr(). For example:
.PP
.nf
.br
@ -133,7 +133,7 @@ The minimum for each item is just the information necessary for findMessage() to
.PP
For example, the "Cancel" in a dialog might have "Anuluj" when the program runs in Polish (in this case the source text would be" Cancel"). The context would (normally) be the dialog's class name; there would normally be no comment, and the translated text would be "Anuluj".
.PP
But it's not always so simple. The Spanish version of a printer dialog with settings for two-sided printing and binding would probably require both "Activado" and "Activada" as translations for "Enabled". In this case the source text would be "Enabled" in both cases, and the context would be the dialog's class name, but the two items would have disambiguating comments such as" two-sided printing" for one and "binding" for the other. The comment enables the translator to choose the appropriate gender for the Spanish version, and enables Qt to distinguish between translations.
But it's not always so simple. The Spanish version of a printer dialog with settings for two-sided printing and binding would probably require both "Activado" and "Activada" as translations for "Enabled". In this case the source text would be "Enabled" in both cases, and the context would be the dialog's class name, but the two items would have disambiguating comments such as" two-sided printing" for one and "binding" for the other. The comment enables the translator to choose the appropriate gender for the Spanish version, and enables TQt to distinguish between translations.
.PP
Note that when QTranslator loads a stripped file, most functions do not work. The functions that do work with stripped files are explicitly documented as such.
.PP
@ -285,8 +285,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
@ -77,7 +77,7 @@ QTranslatorMessage \- Translator message and its properties
.SH DESCRIPTION
The QTranslatorMessage class contains a translator message and its properties.
.PP
This class is of no interest to most applications. It is useful for translation tools such as Qt Linguist. It is provided simply to make the API complete and regular.
This class is of no interest to most applications. It is useful for translation tools such as TQt Linguist. It is provided simply to make the API complete and regular.
.PP
For a QTranslator object, a lookup key is a triple (\fIcontext\fR, \fIsource text\fR, \fIcomment\fR) that uniquely identifies a message. An extended key is a quadruple (\fIhash\fR, \fIcontext\fR, \fIsource text\fR, \fIcomment\fR), where \fIhash\fR is computed from the source text and the comment. Unless you plan to read and write messages yourself, you need not worry about the hash value.
.PP
@ -173,8 +173,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
QTsciiCodec \- Conversion to and from the Tamil TSCII encoding
.SH SYNOPSIS
All the functions in this class are reentrant when Qt is built with thread support.</p>
All the functions in this class are reentrant when TQt is built with thread support.</p>
.PP
\fC#include <ntqtsciicodec.h>\fR
.PP
@ -22,7 +22,7 @@ TSCII, formally the Tamil Standard Code Information Interchange specification, i
.PP
This codec uses the mapping table found at http://www.geocities.com/Athens/5180/tsciiset.html. Tamil uses composed Unicode which might cause some problems if you are using Unicode fonts instead of TSCII fonts.
.PP
Most of the code here was written by Hans Petter Bieker and is included in Qt with the author's permission and the grateful thanks of the Trolltech team. Here is the copyright statement for the code as it was at the point of contribution. Trolltech's subsequent modifications are covered by the usual copyright for Qt.
Most of the code here was written by Hans Petter Bieker and is included in TQt with the author's permission and the grateful thanks of the Trolltech team. Here is the copyright statement for the code as it was at the point of contribution. Trolltech's subsequent modifications are covered by the usual copyright for Qt.
.PP
Copyright (C) 2000 Hans Petter Bieker. All rights reserved.
.PP
@ -50,8 +50,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
QValueList \- Value-based template class that provides lists
.SH SYNOPSIS
All the functions in this class are reentrant when Qt is built with thread support.</p>
All the functions in this class are reentrant when TQt is built with thread support.</p>
.PP
\fC#include <ntqvaluelist.h>\fR
.PP
@ -228,7 +228,7 @@ Inherited by QCanvasItemList, QStringList, and QValueStack.
.SH DESCRIPTION
The QValueList class is a value-based template class that provides lists.
.PP
QValueList is a Qt implementation of an STL-like list container. It can be used in your application if the standard \fClist\fR is not available for your target platform(s). QValueList is part of the Qt Template Library.
QValueList is a TQt implementation of an STL-like list container. It can be used in your application if the standard \fClist\fR is not available for your target platform(s). QValueList is part of the TQt Template Library.
.PP
QValueList<T> defines a template instance to create a list of values that all have the class T. Note that QValueList does not store pointers to the members of the list; it holds a copy of every member. This is why these kinds of classes are called "value based"; QPtrList and QDict are "pointer based".
.PP
@ -246,7 +246,7 @@ Note that C++ defaults to field-by-field assignment operators and copy construct
.PP
In addition, some compilers (e.g. Sun CC) might require that the class provides an equality operator (operator==()).
.PP
QValueList's function naming is consistent with the other Qt classes (e.g. count(), isEmpty()). QValueList also provides extra functions for compatibility with STL algorithms, such as size() and empty(). Programmers already familiar with the STL \fClist\fR may prefer to use the STL-compatible functions.
QValueList's function naming is consistent with the other TQt classes (e.g. count(), isEmpty()). QValueList also provides extra functions for compatibility with STL algorithms, such as size() and empty(). Programmers already familiar with the STL \fClist\fR may prefer to use the STL-compatible functions.
.PP
Example:
.PP
@ -389,7 +389,7 @@ There are several ways to insert items into the list. The prepend() and append()
.PP
Items can also be removed from the list in several ways. There are several variants of the remove() function, which removes a specific item from the list. The remove() function will find and remove items according to a specific item value.
.PP
Lists can also be sorted using the Qt Template Library. For example with qHeapSort():
Lists can also be sorted using the TQt Template Library. For example with qHeapSort():
.PP
Example:
.PP
@ -409,7 +409,7 @@ Example:
.br
.fi
.PP
See also QValueListIterator, Qt Template Library Classes, Implicitly and Explicitly Shared Classes, and Non-GUI Classes.
See also QValueListIterator, TQt Template Library Classes, Implicitly and Explicitly Shared Classes, and Non-GUI Classes.
.SS "Member Type Documentation"
.SH "QValueList::ConstIterator"
This iterator is an instantiation of QValueListConstIterator for the same type as this QValueList. In other words, if you instantiate QValueList<int>, ConstIterator is a QValueListConstIterator<int>. Several member function use it, such as QValueList::begin(), which returns an iterator pointing to the first item in the list.
@ -744,8 +744,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
All the functions in this class are reentrant when Qt is built with thread support.</p>
All the functions in this class are reentrant when TQt is built with thread support.</p>
.PP
\fC#include <ntqvaluelist.h>\fR
.PP
@ -99,11 +99,11 @@ Example (see QValueList for the complete code):
.PP
QValueList is highly optimized for performance and memory usage. This means that you must be careful: QValueList does not know about all its iterators and the iterators don't know to which list they belong. This makes things very fast, but if you're not careful, you can get spectacular bugs. Always make sure iterators are valid before dereferencing them or using them as parameters to generic algorithms in the STL or the QTL.
.PP
Using an invalid iterator is undefined (your application will probably crash). Many Qt functions return const value lists; to iterate over these you should make a copy and iterate over the copy.
Using an invalid iterator is undefined (your application will probably crash). Many TQt functions return const value lists; to iterate over these you should make a copy and iterate over the copy.
.PP
For every Iterator there is a ConstIterator. When accessing a QValueList in a const environment or if the reference or pointer to the list is itself const, then you must use the ConstIterator. Its semantics are the same as the Iterator, but it only returns const references.
.PP
See also QValueList, QValueListConstIterator, Qt Template Library Classes, and Non-GUI Classes.
See also QValueList, QValueListConstIterator, TQt Template Library Classes, and Non-GUI Classes.
.SS "Member Type Documentation"
.SH "QValueListIterator::pointer"
Pointer to value_type.
@ -160,8 +160,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
QValueStack \- Value-based template class that provides a stack
.SH SYNOPSIS
All the functions in this class are reentrant when Qt is built with thread support.</p>
All the functions in this class are reentrant when TQt is built with thread support.</p>
.PP
\fC#include <ntqvaluestack.h>\fR
.PP
@ -39,7 +39,7 @@ Inherits QValueList<T>.
.SH DESCRIPTION
The QValueStack class is a value-based template class that provides a stack.
.PP
Define a template instance QValueStack<X> to create a stack of values that all have the class X. QValueStack is part of the Qt Template Library.
Define a template instance QValueStack<X> to create a stack of values that all have the class X. QValueStack is part of the TQt Template Library.
.PP
Note that QValueStack does not store pointers to the members of the stack; it holds a copy of every member. That is why these kinds of classes are called "value based"; QPtrStack, QPtrList, QDict, etc., are "pointer based".
.PP
@ -84,7 +84,7 @@ a default constructor, i.e. a constructor that does not take any arguments.
.PP
Note that C++ defaults to field-by-field assignment operators and copy constructors if no explicit version is supplied. In many cases this is sufficient.
.PP
See also Qt Template Library Classes, Implicitly and Explicitly Shared Classes, and Non-GUI Classes.
See also TQt Template Library Classes, Implicitly and Explicitly Shared Classes, and Non-GUI Classes.
.SH MEMBER FUNCTION DOCUMENTATION
.SH "QValueStack::QValueStack ()"
Constructs an empty stack.
@ -129,8 +129,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
QValueVector \- Value-based template class that provides a dynamic array
.SH SYNOPSIS
All the functions in this class are reentrant when Qt is built with thread support.</p>
All the functions in this class are reentrant when TQt is built with thread support.</p>
.PP
\fC#include <ntqvaluevector.h>\fR
.PP
@ -184,7 +184,7 @@ All the functions in this class are reentrant when Qt is built with thread suppo
.SH DESCRIPTION
The QValueVector class is a value-based template class that provides a dynamic array.
.PP
QValueVector is a Qt implementation of an STL-like vector container. It can be used in your application if the standard \fCvector\fR is not available for your target platforms. QValueVector is part of the Qt Template Library.
QValueVector is a TQt implementation of an STL-like vector container. It can be used in your application if the standard \fCvector\fR is not available for your target platforms. QValueVector is part of the TQt Template Library.
.PP
QValueVector<T> defines a template instance to create a vector of values that all have the class T. QValueVector does not store pointers to the members of the vector; it holds a copy of every member. QValueVector is said to be value based; in contrast, QPtrList and QDict are pointer based.
.PP
@ -298,7 +298,7 @@ Program output:
.PP
As you can see, the most recent change to Joe's salary did not affect the value in the vector because the vector created a copy of Joe's entry.
.PP
Many Qt functions return const value vectors; to iterate over these you should make a copy and iterate over the copy.
Many TQt functions return const value vectors; to iterate over these you should make a copy and iterate over the copy.
.PP
There are several ways to find items in the vector. The begin() and end() functions return iterators to the beginning and end of the vector. The advantage of getting an iterator is that you can move forward or backward from this position by incrementing/decrementing the iterator. The iterator returned by end() points to the element which is one past the last element in the container. The past-the-end iterator is still associated with the vector it belongs to, however it is \fInot\fR dereferenceable; operator*() will not return a well-defined value. If the vector is empty(), the iterator returned by begin() will equal the iterator returned by end().
.PP
@ -401,7 +401,7 @@ There are several ways to insert elements into the vector. The push_back() funct
.PP
Items can be also be removed from the vector in several ways. There are several variants of the erase() function which removes a specific element, or range of elements, from the vector.
.PP
Vectors can be also sorted with various STL algorithms , or it can be sorted using the Qt Template Library. For example with qHeapSort():
Vectors can be also sorted with various STL algorithms , or it can be sorted using the TQt Template Library. For example with qHeapSort():
.PP
Example:
.PP
@ -423,7 +423,7 @@ Example:
.PP
QValueVector stores its elements in contiguous memory. This means that you can use a QValueVector in any situation that requires an array.
.PP
See also Qt Template Library Classes, Implicitly and Explicitly Shared Classes, and Non-GUI Classes.
See also TQt Template Library Classes, Implicitly and Explicitly Shared Classes, and Non-GUI Classes.
.SS "Member Type Documentation"
.SH "QValueVector::ConstIterator"
The vector's const iterator type.
@ -623,8 +623,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
QVariant \- Acts like a union for the most common Qt data types
QVariant \- Acts like a union for the most common TQt data types
.SH SYNOPSIS
\fC#include <ntqvariant.h>\fR
.PP
@ -399,9 +399,9 @@ QVariant \- Acts like a union for the most common Qt data types
.br
.in -1c
.SH DESCRIPTION
The QVariant class acts like a union for the most common Qt data types.
The QVariant class acts like a union for the most common TQt data types.
.PP
Because C++ forbids unions from including types that have non-default constructors or destructors, most interesting Qt classes cannot be used in unions. Without QVariant, this would be a problem for QObject::property() and for database work, etc.
Because C++ forbids unions from including types that have non-default constructors or destructors, most interesting TQt classes cannot be used in unions. Without QVariant, this would be a problem for QObject::property() and for database work, etc.
.PP
A QVariant object holds a single value of a single type() at a time. (Some type()s are multi-valued, for example a string list.) You can find out what type, T, the variant holds, convert it to a different type using one of the asT() functions, e.g. asSize(), get its value using one of the toT() functions, e.g. toSize(), and check whether the type can be converted to a particular type using canCast().
.PP
@ -1143,8 +1143,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
Enters "What's this?" mode and returns immediately.
.PP
Qt will install a special cursor and take over mouse input until the user clicks somewhere. It then shows any help available and ends "What's this?" mode. Finally, Qt removes the special cursor and help window and then restores ordinary event processing, at which point the left mouse button is no longer pressed.
Qt will install a special cursor and take over mouse input until the user clicks somewhere. It then shows any help available and ends "What's this?" mode. Finally, TQt removes the special cursor and help window and then restores ordinary event processing, at which point the left mouse button is no longer pressed.
.PP
The user can also use the Esc key to leave "What's this?" mode.
.PP
@ -195,8 +195,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
@ -1005,7 +1005,7 @@ A widget that isn't embedded in a parent widget is called a top-level widget. Us
.PP
A widget without a parent widget is always a top-level widget.
.PP
Non-top-level widgets are child widgets. These are child windows in their parent widgets. You cannot usually distinguish a child widget from its parent visually. Most other widgets in Qt are useful only as child widgets. (It is possible to make, say, a button into a top-level widget, but most people prefer to put their buttons inside other widgets, e.g. QDialog.)
Non-top-level widgets are child widgets. These are child windows in their parent widgets. You cannot usually distinguish a child widget from its parent visually. Most other widgets in TQt are useful only as child widgets. (It is possible to make, say, a button into a top-level widget, but most people prefer to put their buttons inside other widgets, e.g. QDialog.)
.PP
If you want to use a QWidget to hold child widgets you will probably want to add a layout to the parent QWidget. (See Layouts.)
.PP
@ -1143,7 +1143,7 @@ The widget flags argument, \fIf\fR, is normally 0, but it can be set to customiz
.PP
If you add a child widget to an already visible widget you must explicitly show the child to make it visible.
.PP
Note that the X11 version of Qt may not be able to deliver all combinations of style flags on all systems. This is because on X11, Qt can only ask the window manager, and the window manager can override the application's settings. On Windows, Qt can set whatever flags you want.
Note that the X11 version of TQt may not be able to deliver all combinations of style flags on all systems. This is because on X11, TQt can only ask the window manager, and the window manager can override the application's settings. On Windows, TQt can set whatever flags you want.
.PP
Example:
.PP
@ -1489,7 +1489,7 @@ This widget receives all mouse events until releaseMouse() is called; other widg
.PP
\fBWarning:\fR Bugs in mouse-grabbing applications very often lock the terminal. Use this function with extreme caution, and consider using the \fC-nograb\fR command line option while debugging.
.PP
It is almost never necessary to grab the mouse when using Qt, as Qt grabs and releases it sensibly. In particular, Qt grabs the mouse when a mouse button is pressed and keeps it until the last button is released.
It is almost never necessary to grab the mouse when using Qt, as TQt grabs and releases it sensibly. In particular, TQt grabs the mouse when a mouse button is pressed and keeps it until the last button is released.
.PP
Note that only visible widgets can grab mouse input. If isVisible() returns FALSE for a widget, that widget cannot call grabMouse().
.PP
@ -1673,7 +1673,7 @@ See also raise() and stackUnder().
This special event handler can be reimplemented in a subclass to receive native Macintosh events.
.PP
In your reimplementation of this function, if you want to stop the event being handled by Qt, return TRUE. If you return FALSE, this native event is passed back to Qt, which translates the event into a Qt event and sends it to the widget.
In your reimplementation of this function, if you want to stop the event being handled by Qt, return TRUE. If you return FALSE, this native event is passed back to Qt, which translates the event into a TQt event and sends it to the widget.
.PP
\fBWarning:\fR This function is not portable.
.PP
@ -1804,7 +1804,7 @@ A paint event is a request to repaint all or part of the widget. It can happen a
.PP
Many widgets can simply repaint their entire surface when asked to, but some slow widgets need to optimize by painting only the requested region: QPaintEvent::region(). This speed optimization does not change the result, as painting is clipped to that region during event processing. QListView and QCanvas do this, for example.
.PP
Qt also tries to speed up painting by merging multiple paint events into one. When update() is called several times or the window system sends several paint events, Qt merges these events into one event with a larger region (see QRegion::unite()). repaint() does not permit this optimization, so we suggest using update() when possible.
Qt also tries to speed up painting by merging multiple paint events into one. When update() is called several times or the window system sends several paint events, TQt merges these events into one event with a larger region (see QRegion::unite()). repaint() does not permit this optimization, so we suggest using update() when possible.
.PP
When the paint event occurs, the update region has normally been erased, so that you're painting on the widget's background. There are a couple of exceptions and QPaintEvent::erased() tells you whether the widget has been erased or not.
.PP
@ -1853,7 +1853,7 @@ Returns the position of the widget within its parent widget. See the "pos" prope
This special event handler can be reimplemented in a subclass to receive native Qt/Embedded events.
.PP
In your reimplementation of this function, if you want to stop the event being handled by Qt, return TRUE. If you return FALSE, this native event is passed back to Qt, which translates the event into a Qt event and sends it to the widget.
In your reimplementation of this function, if you want to stop the event being handled by Qt, return TRUE. If you return FALSE, this native event is passed back to Qt, which translates the event into a TQt event and sends it to the widget.
\fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
.PP
This method is provided to aid porting from Qt 1.0 to 2.0. It has been renamed reparent() in Qt 2.0.
This method is provided to aid porting from TQt 1.0 to 2.0. It has been renamed reparent() in TQt 2.0.
.SH "QRect QWidget::rect () const"
Returns the internal geometry of the widget excluding any window frame. See the "rect" property for details.
.SH "void QWidget::releaseKeyboard ()"
@ -1883,11 +1883,11 @@ See also grabMouse(), grabKeyboard(), and releaseKeyboard().
.SH "void QWidget::repaint ( int x, int y, int w, int h, bool erase = TRUE )\fC [slot]\fR"
Repaints the widget directly by calling paintEvent() immediately, unless updates are disabled or the widget is hidden.
.PP
If \fIerase\fR is TRUE, Qt erases the area \fI(x, y, w, h)\fR before the paintEvent() call.
If \fIerase\fR is TRUE, TQt erases the area \fI(x, y, w, h)\fR before the paintEvent() call.
.PP
If \fIw\fR is negative, it is replaced with \fCwidth() - x\fR, and if \fIh\fR is negative, it is replaced width \fCheight() - y\fR.
.PP
We suggest only using repaint() if you need an immediate repaint, for example during animation. In almost all circumstances update() is better, as it permits Qt to optimize for speed and minimize flicker.
We suggest only using repaint() if you need an immediate repaint, for example during animation. In almost all circumstances update() is better, as it permits TQt to optimize for speed and minimize flicker.
.PP
\fBWarning:\fR If you call repaint() in a function which may itself be called from paintEvent(), you may get infinite recursion. The update() function never causes recursion.
.PP
@ -2112,7 +2112,7 @@ Sets enables or disables the use of input methods for this widget to \fIb\fR. Se
Enables key event compression, if \fIcompress\fR is TRUE, and disables it if \fIcompress\fR is FALSE.
.PP
Key compression is off by default (except for QLineEdit and QTextEdit), so widgets receive one key press event for each key press (or more, since autorepeat is usually on). If you turn it on and your program doesn't keep up with key input, Qt may try to compress key events so that more than one character can be processed in each event.
Key compression is off by default (except for QLineEdit and QTextEdit), so widgets receive one key press event for each key press (or more, since autorepeat is usually on). If you turn it on and your program doesn't keep up with key input, TQt may try to compress key events so that more than one character can be processed in each event.
.PP
For example, a word processor widget might receive 2, 3 or more characters in each QKeyEvent::text(), if the layout recalculation takes too long for the CPU.
.PP
@ -2289,7 +2289,7 @@ See also Qt::WindowState and windowState().
.SH "void QWidget::show ()\fC [virtual slot]\fR"
Shows the widget and its child widgets.
.PP
If its size or position has changed, Qt guarantees that a widget gets move and resize events just before it is shown.
If its size or position has changed, TQt guarantees that a widget gets move and resize events just before it is shown.
.PP
You almost never have to reimplement this function. If you need to change some settings before a widget is shown, use showEvent() instead. If you need to do some delayed initialization use polish().
.PP
@ -2427,7 +2427,7 @@ Resets the widget's palette. See the "palette" property for details.
.SH "void QWidget::update ()\fC [slot]\fR"
Updates the widget unless updates are disabled or the widget is hidden.
.PP
This function does not cause an immediate repaint; instead it schedules a paint event for processing when Qt returns to the main event loop. This permits Qt to optimize for more speed and less flicker than a call to repaint() does.
This function does not cause an immediate repaint; instead it schedules a paint event for processing when TQt returns to the main event loop. This permits TQt to optimize for more speed and less flicker than a call to repaint() does.
.PP
Calling update() several times normally results in just one paintEvent() call.
.PP
@ -2442,7 +2442,7 @@ This is an overloaded member function, provided for convenience. It behaves esse
.PP
Updates a rectangle (\fIx\fR, \fIy\fR, \fIw\fR, \fIh\fR) inside the widget unless updates are disabled or the widget is hidden.
.PP
This function does not cause an immediate repaint; instead it schedules a paint event for processing when Qt returns to the main event loop. This permits Qt to optimize for more speed and less flicker and a call to repaint() does.
This function does not cause an immediate repaint; instead it schedules a paint event for processing when TQt returns to the main event loop. This permits TQt to optimize for more speed and less flicker and a call to repaint() does.
.PP
Calling update() several times normally results in just one paintEvent() call.
.PP
@ -2456,7 +2456,7 @@ This is an overloaded member function, provided for convenience. It behaves esse
.PP
Updates a rectangle \fIr\fR inside the widget unless updates are disabled or the widget is hidden.
.PP
This function does not cause an immediate repaint; instead it schedules a paint event for processing when Qt returns to the main event loop. This permits Qt to optimize for more speed and less flicker and a call to repaint() does.
This function does not cause an immediate repaint; instead it schedules a paint event for processing when TQt returns to the main event loop. This permits TQt to optimize for more speed and less flicker and a call to repaint() does.
.PP
Calling update() several times normally results in just one paintEvent() call.
.SH "void QWidget::updateGeometry ()"
@ -2484,7 +2484,7 @@ Returns the width of the widget excluding any window frame. See the "width" prop
This special event handler can be reimplemented in a subclass to receive native Windows events.
.PP
In your reimplementation of this function, if you want to stop the event being handled by Qt, return TRUE. If you return FALSE, this native event is passed back to Qt, which translates the event into a Qt event and sends it to the widget.
In your reimplementation of this function, if you want to stop the event being handled by Qt, return TRUE. If you return FALSE, this native event is passed back to Qt, which translates the event into a TQt event and sends it to the widget.
.PP
\fBWarning:\fR This function is not portable.
.PP
@ -2514,7 +2514,7 @@ Returns the x coordinate of the widget relative to its parent including any wind
This special event handler can be reimplemented in a subclass to receive native X11 events.
.PP
In your reimplementation of this function, if you want to stop the event being handled by Qt, return TRUE. If you return FALSE, this native event is passed back to Qt, which translates the event into a Qt event and sends it to the widget.
In your reimplementation of this function, if you want to stop the event being handled by Qt, return TRUE. If you return FALSE, this native event is passed back to Qt, which translates the event into a TQt event and sends it to the widget.
.PP
\fBWarning:\fR This function is not portable.
.PP
@ -2751,7 +2751,7 @@ When changing the geometry, the widget, if visible, receives a move event (moveE
.PP
The size component is adjusted if it lies outside the range defined by minimumSize() and maximumSize().
.PP
setGeometry() is virtual, and all other overloaded setGeometry() implementations in Qt call it.
setGeometry() is virtual, and all other overloaded setGeometry() implementations in TQt call it.
.PP
\fBWarning:\fR Calling setGeometry() inside resizeEvent() or moveEvent() can lead to infinite recursion.
.PP
@ -2859,7 +2859,7 @@ This property holds whether this widget is maximized.
.PP
This property is only relevant for top-level widgets.
.PP
Note that due to limitations in some window-systems, this does not always report the expected results (e.g. if the user on X11 maximizes the window via the window manager, Qt has no way of distinguishing this from any other resize). This is expected to improve as window manager protocols evolve.
Note that due to limitations in some window-systems, this does not always report the expected results (e.g. if the user on X11 maximizes the window via the window manager, TQt has no way of distinguishing this from any other resize). This is expected to improve as window manager protocols evolve.
.PP
See also windowState(), showMaximized(), visible, show(), hide(), showNormal(), and minimized.
.PP
@ -3019,7 +3019,7 @@ If the widget is a top-level widget, the position is that of the widget on the d
.PP
When changing the position, the widget, if visible, receives a move event (moveEvent()) immediately. If the widget is not currently visible, it is guaranteed to receive an event before it is shown.
.PP
move() is virtual, and all other overloaded move() implementations in Qt call it.
move() is virtual, and all other overloaded move() implementations in TQt call it.
.PP
\fBWarning:\fR Calling move() or setGeometry() inside moveEvent() can lead to infinite recursion.
.PP
@ -3055,7 +3055,7 @@ The size is adjusted if it lies outside the range defined by minimumSize() and m
.PP
If you want a top-level window to have a fixed size, call setResizeMode( QLayout::FreeResize ) on its layout.
.PP
resize() is virtual, and all other overloaded resize() implementations in Qt call it.
resize() is virtual, and all other overloaded resize() implementations in TQt call it.
.PP
\fBWarning:\fR Calling resize() or setGeometry() inside resizeEvent() can lead to infinite recursion.
.PP
@ -3207,8 +3207,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
QWidgetFactory \- For the dynamic creation of widgets from Qt Designer .ui files
QWidgetFactory \- For the dynamic creation of widgets from TQt Designer .ui files
.SH SYNOPSIS
\fC#include <ntqwidgetfactory.h>\fR
.PP
@ -45,22 +45,22 @@ QWidgetFactory \- For the dynamic creation of widgets from Qt Designer .ui files
.br
.in -1c
.SH DESCRIPTION
The QWidgetFactory class provides for the dynamic creation of widgets from Qt Designer .ui files.
The QWidgetFactory class provides for the dynamic creation of widgets from TQt Designer .ui files.
.PP
This class basically offers two things:
.IP
.TP
Dynamically creating widgets from Qt Designer user interface description files. You can do this using the static function QWidgetFactory::create(). This function also performs signal and slot connections, tab ordering, etc., as defined in the .ui file, and returns the top-level widget in the .ui file. After creating the widget you can use QObject::child() and QObject::queryList() to access child widgets of this returned widget.
Dynamically creating widgets from TQt Designer user interface description files. You can do this using the static function QWidgetFactory::create(). This function also performs signal and slot connections, tab ordering, etc., as defined in the .ui file, and returns the top-level widget in the .ui file. After creating the widget you can use QObject::child() and QObject::queryList() to access child widgets of this returned widget.
.IP
.TP
Adding additional widget factories to be able to create custom widgets. See createWidget() for details.
.IP
.PP
This class is not included in the Qt library itself. To use it you must link against \fClibtqui.so\fR (Unix) or \fCtqui.lib\fR (Windows), which is built into \fCINSTALL/lib\fR if you built \fIQt Designer\fR (\fCINSTALL\fR is the directory where Qt is installed ).
This class is not included in the TQt library itself. To use it you must link against \fClibtqui.so\fR (Unix) or \fCtqui.lib\fR (Windows), which is built into \fCINSTALL/lib\fR if you built \fIQt Designer\fR (\fCINSTALL\fR is the directory where TQt is installed ).
.PP
If you create a QMainWindow using a QWidgetFactory, be aware that it already has a central widget. Therefore, you need to delete this one before setting another one.
.PP
See the "Creating Dynamic Dialogs from .ui Files" section of the Qt Designer manual for an example. See also the QWidgetPlugin class and the Plugins documentation.
See the "Creating Dynamic Dialogs from .ui Files" section of the TQt Designer manual for an example. See also the QWidgetPlugin class and the Plugins documentation.
.SH MEMBER FUNCTION DOCUMENTATION
.SH "QWidgetFactory::QWidgetFactory ()"
Constructs a QWidgetFactory.
@ -83,14 +83,14 @@ Loads the user interface description from device \fIdev\fR.
Creates a widget of the type \fIclassName\fR passing \fIparent\fR and \fIname\fR to its constructor.
.PP
If \fIclassName\fR is a widget in the Qt library, it is directly created by this function. If the widget isn't in the Qt library, each of the installed widget plugins is asked, in turn, to create the widget. As soon as a plugin says it can create the widget it is asked to do so. It may occur that none of the plugins can create the widget, in which case each installed widget factory is asked to create the widget (see addWidgetFactory()). If the widget cannot be created by any of these means, 0 is returned.
If \fIclassName\fR is a widget in the TQt library, it is directly created by this function. If the widget isn't in the TQt library, each of the installed widget plugins is asked, in turn, to create the widget. As soon as a plugin says it can create the widget it is asked to do so. It may occur that none of the plugins can create the widget, in which case each installed widget factory is asked to create the widget (see addWidgetFactory()). If the widget cannot be created by any of these means, 0 is returned.
.PP
If you have a custom widget, and want it to be created using the widget factory, there are two approaches you can use:
.PP
<ol type=1>
.IP
.TP
Write a widget plugin. This allows you to use the widget in \fIQt Designer\fR and in this QWidgetFactory. See the widget plugin documentation for further details. (See the "Creating Custom Widgets with Plugins" section of the Qt Designer manual for an example.
Write a widget plugin. This allows you to use the widget in \fIQt Designer\fR and in this QWidgetFactory. See the widget plugin documentation for further details. (See the "Creating Custom Widgets with Plugins" section of the TQt Designer manual for an example.
.IP
.TP
Subclass QWidgetFactory. Then reimplement this function to create and return an instance of your custom widget if \fIclassName\fR equals the name of your widget, otherwise return 0. Then at the beginning of your program where you want to use the widget factory to create widgets do a:
@ -123,8 +123,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
@ -47,13 +47,13 @@ QWidgetPlugin \- Abstract base for custom QWidget plugins
.SH DESCRIPTION
The QWidgetPlugin class provides an abstract base for custom QWidget plugins.
.PP
The widget plugin is a simple plugin interface that makes it easy to create custom widgets that can be included in forms using Qt Designer and used by applications.
The widget plugin is a simple plugin interface that makes it easy to create custom widgets that can be included in forms using TQt Designer and used by applications.
.PP
Writing a widget plugin is achieved by subclassing this base class, reimplementing the pure virtual functions keys(), create(), group(), iconSet(), includeFile(), toolTip(), whatsThis() and isContainer(), and exporting the class with the \fCQ_EXPORT_PLUGIN\fR macro.
.PP
See the Qt Designer manual's, 'Creating Custom Widgets' section in the 'Creating Custom Widgets' chapter, for a complete example of a QWidgetPlugin.
See the TQt Designer manual's, 'Creating Custom Widgets' section in the 'Creating Custom Widgets' chapter, for a complete example of a QWidgetPlugin.
.PP
See also the Plugins documentation and the QWidgetFactory class that is supplied with Qt Designer.
See also the Plugins documentation and the QWidgetFactory class that is supplied with TQt Designer.
.PP
See also Plugins.
.SH MEMBER FUNCTION DOCUMENTATION
@ -62,7 +62,7 @@ Constructs a widget plugin. This is invoked automatically by the \fCQ_EXPORT_PLU
.SH "QWidgetPlugin::~QWidgetPlugin ()"
Destroys the widget plugin.
.PP
You never have to call this explicitly. Qt destroys a plugin automatically when it is no longer used.
You never have to call this explicitly. TQt destroys a plugin automatically when it is no longer used.
Creates and returns a QWidget object for the widget key \fIkey\fR. The widget key is the class name of the required widget. The \fIname\fR and \fIparent\fR arguments are passed to the custom widget's constructor.
.PP
@ -112,8 +112,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
@ -78,9 +78,9 @@ The QWorkspace widget provides a workspace window that can contain decorated win
.PP
MDI (multiple document interface) applications typically have one main window with a menu bar and toolbar, and a central widget that is a QWorkspace. The workspace itself contains zero, one or more document windows, each of which is a widget.
.PP
The workspace itself is an ordinary Qt widget. It has a standard constructor that takes a parent widget and an object name. The parent window is usually a QMainWindow, but it need not be.
The workspace itself is an ordinary TQt widget. It has a standard constructor that takes a parent widget and an object name. The parent window is usually a QMainWindow, but it need not be.
.PP
Document windows (i.e. MDI windows) are also ordinary Qt widgets which have the workspace as their parent widget. When you call show(), hide(), showMaximized(), setCaption(), etc. on a document window, it is shown, hidden, etc. with a frame, caption, icon and icon text, just as you'd expect. You can provide widget flags which will be used for the layout of the decoration or the behaviour of the widget itself.
Document windows (i.e. MDI windows) are also ordinary TQt widgets which have the workspace as their parent widget. When you call show(), hide(), showMaximized(), setCaption(), etc. on a document window, it is shown, hidden, etc. with a frame, caption, icon and icon text, just as you'd expect. You can provide widget flags which will be used for the layout of the decoration or the behaviour of the widget itself.
.PP
To change or retrieve the geometry of MDI windows you must operate on the MDI widget's parentWidget(). (The parentWidget() provides access to the decorated window in which the MDI window's widget is shown.)
.PP
@ -184,8 +184,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
@ -46,7 +46,7 @@ Subclasses call this function to send a key event. The server may additionally f
.PP
<center>.nf
.TS
l - l. Parameter Meaning \fIunicode\fR The Unicode value for the key, or 0xFFFF is none is appropriate. \fIkeycode\fR The Qt keycode for the key (see Qt::Key for the list of codes). \fImodifiers\fR The set of modifier keys (see Qt::Modifier). \fIisPress\fR Whether this is a press or a release. \fIautoRepeat\fR
l - l. Parameter Meaning \fIunicode\fR The Unicode value for the key, or 0xFFFF is none is appropriate. \fIkeycode\fR The TQt keycode for the key (see Qt::Key for the list of codes). \fImodifiers\fR The set of modifier keys (see Qt::Modifier). \fIisPress\fR Whether this is a press or a release. \fIautoRepeat\fR
.TE
.fi
</center>
@ -65,8 +65,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
Returns the keyboard mapping table used to convert keyboard scancodes to Qt keycodes and Unicode values. It's used by the keyboard driver in \fCqkeyboard_qws.cpp\fR.
Returns the keyboard mapping table used to convert keyboard scancodes to TQt keycodes and Unicode values. It's used by the keyboard driver in \fCqkeyboard_qws.cpp\fR.
@ -247,7 +247,7 @@ Returns TRUE if the screensaver is active (i.e. the screen is blanked); otherwis
.SH "void QWSServer::sendIMEvent ( IMState state, const QString & txt, int cpos, int selLen )"
This function sends an input method event to the server. The current state is passed in \fIstate\fR and the current text in \fItxt\fR. The cursor's position in the text is given by \fIcpos\fR, and the selection length (which could be 0) is given in \fIselLen\fR.
.SH "void QWSServer::sendKeyEvent ( int unicode, int keycode, int modifiers, bool isPress, bool autoRepeat )\fC [static]\fR"
Send a key event. You can use this to send key events generated by" virtual keyboards". \fIunicode\fR is the Unicode value of the key to send, \fIkeycode\fR the Qt keycode (e.g. \fCKey_Left\fR), \fImodifiers\fR indicates whether, Shift/Alt/Ctrl keys are pressed, \fIisPress\fR is TRUE if this is a key down event and FALSE if it's a key up event, and \fIautoRepeat\fR is TRUE if this is an autorepeat event (i.e. the user has held the key down and this is the second or subsequent key event being sent).
Send a key event. You can use this to send key events generated by" virtual keyboards". \fIunicode\fR is the Unicode value of the key to send, \fIkeycode\fR the TQt keycode (e.g. \fCKey_Left\fR), \fImodifiers\fR indicates whether, Shift/Alt/Ctrl keys are pressed, \fIisPress\fR is TRUE if this is a key down event and FALSE if it's a key up event, and \fIautoRepeat\fR is TRUE if this is an autorepeat event (i.e. the user has held the key down and this is the second or subsequent key event being sent).
.SH "void QWSServer::setCursorVisible ( bool vis )\fC [static]\fR"
If \fIvis\fR is TRUE, makes the cursor visible; if \fIvis\fR is FALSE, makes the cursor invisible.
.PP
@ -299,8 +299,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
QXmlReader \- Interface for XML readers (i.e. parsers)
.SH SYNOPSIS
All the functions in this class are reentrant when Qt is built with thread support.</p>
All the functions in this class are reentrant when TQt is built with thread support.</p>
.PP
\fC#include <ntqxml.h>\fR
.PP
@ -83,7 +83,7 @@ The QXmlReader class provides an interface for XML readers (i.e. parsers).
.PP
This abstract class provides an interface for all of Qt's XML readers. Currently there is only one implementation of a reader included in Qt's XML module: QXmlSimpleReader. In future releases there might be more readers with different properties available (e.g. a validating parser).
.PP
The design of the XML classes follows the SAX2 Java interface, with the names adapted to fit Qt naming conventions. It should be very easy for anybody who has worked with SAX2 to get started with the Qt XML classes.
The design of the XML classes follows the SAX2 Java interface, with the names adapted to fit TQt naming conventions. It should be very easy for anybody who has worked with SAX2 to get started with the TQt XML classes.
.PP
All readers use the class QXmlInputSource to read the input document. Since you are normally interested in particular content in the XML document, the reader reports the content through special handler classes (QXmlDTDHandler, QXmlDeclHandler, QXmlContentHandler, QXmlEntityResolver, QXmlErrorHandler and QXmlLexicalHandler), which you must subclass, if you want to process the contents.
.PP
@ -194,8 +194,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
This module is part of the \link commercialeditions.html Qt Enterprise Edition \endlink.
This module is part of the \link commercialeditions.html TQt Enterprise Edition \endlink.
\endif
\tableofcontents
@ -265,7 +265,7 @@ It is not mandatory, of course, but it's good programming practice to cover erro
\section2 Info Url Client
It is time to illustrate how to use QNetworkProtocol, QNetworkOperation and QUrlOperator to register our communication protocol and make it on par to already implemented protocols, like QFtp, QHttp and QLocalFs. This will give us much larger flexibility in use and let us use Qt class that supports Network Protocols, e.g. QFileDialog.
It is time to illustrate how to use QNetworkProtocol, QNetworkOperation and QUrlOperator to register our communication protocol and make it on par to already implemented protocols, like QFtp, QHttp and QLocalFs. This will give us much larger flexibility in use and let us use TQt class that supports Network Protocols, e.g. QFileDialog.
First, here is the header file in which Qip (our custom Network
Protocol) is declared (\c network/infoprotocol/infourlclient/qip.h):
@ -374,11 +374,11 @@ We didn't use static function QFileDialog::getOpenFileName() because under Windo
### Rainer: have we an example that I can use?
\section1 Inter-Process Communication between Qt Applications
\section1 Inter-Process Communication between TQt Applications
### Rainer: have we an example that I can use?
\section1 Inter-Process Communication between Qt and non-Qt Applications
\section1 Inter-Process Communication between TQt and non-Qt Applications
### Rainer: have we an example that I can use?
Some files were not shown because too many files have changed in this diff
Show More
