diff options
Diffstat (limited to 'doc')
595 files changed, 955 insertions, 955 deletions
diff --git a/doc/3rdparty.doc b/doc/3rdparty.doc index 194a08a6..69991a30 100644 --- a/doc/3rdparty.doc +++ b/doc/3rdparty.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/accel.doc b/doc/accel.doc index 3597eec1..66412418 100644 --- a/doc/accel.doc +++ b/doc/accel.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/annotated.doc b/doc/annotated.doc index 52a16854..4c2131b8 100644 --- a/doc/annotated.doc +++ b/doc/annotated.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/application-walkthrough.doc b/doc/application-walkthrough.doc index 39247a6f..c39abe6f 100644 --- a/doc/application-walkthrough.doc +++ b/doc/application-walkthrough.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -244,7 +244,7 @@ will implement later. Now that we have done the File menu we shift our focus back to the menu bar and insert a separator. From now on further menu bar entries -will be aligned to the right if the windows system style retquires it. +will be aligned to the right if the windows system style requires it. \printline help \printuntil whatsThis diff --git a/doc/canvas.doc b/doc/canvas.doc index f3cf4c48..629aed57 100644 --- a/doc/canvas.doc +++ b/doc/canvas.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -52,7 +52,7 @@ QCanvasItem QCanvasItems \endlink. Canvas items can have an arbitrary shape, size and content, can be freely moved around in the canvas, and can be checked for collisions. Canvas items can be set to move across the canvas automatically and animated canvas items are -supported with QCanvasSprite. (If you retquire 3D graphics see Qt's +supported with QCanvasSprite. (If you require 3D graphics see Qt's \link opengl.html OpenGL module \endlink.) The canvas module uses a document/view model. The \l QCanvasView class diff --git a/doc/changes.doc b/doc/changes.doc index 0f79e217..34ecb37f 100644 --- a/doc/changes.doc +++ b/doc/changes.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -207,7 +207,7 @@ existing code which uses these classes will continue to work. \section2 Regular Expressions Qt has always provided regular expression support, but that support -was pretty much limited to what was retquired in common GUI control +was pretty much limited to what was required in common GUI control elements such as file dialogs. Qt 3.0 introduces a new regular expression engine, QRegExp, that supports most of Perl's regex features and is Unicode based. The most useful additions are support diff --git a/doc/charinput-qws.doc b/doc/charinput-qws.doc index 96be08ec..329026af 100644 --- a/doc/charinput-qws.doc +++ b/doc/charinput-qws.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/classchart.doc b/doc/classchart.doc index 43456bd6..59862ce2 100644 --- a/doc/classchart.doc +++ b/doc/classchart.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/classes.doc b/doc/classes.doc index 580d82f3..6a169eae 100644 --- a/doc/classes.doc +++ b/doc/classes.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/collect.doc b/doc/collect.doc index 604740d7..7e050478 100644 --- a/doc/collect.doc +++ b/doc/collect.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/commercialeditions.doc b/doc/commercialeditions.doc index 31af3c57..438afac7 100644 --- a/doc/commercialeditions.doc +++ b/doc/commercialeditions.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/coordsys.doc b/doc/coordsys.doc index f614116a..01726f39 100644 --- a/doc/coordsys.doc +++ b/doc/coordsys.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/credits.doc b/doc/credits.doc index 58385cd0..de118d86 100644 --- a/doc/credits.doc +++ b/doc/credits.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/customstyles.doc b/doc/customstyles.doc index e3ce114b..0c196da2 100644 --- a/doc/customstyles.doc +++ b/doc/customstyles.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/datastreamformat.doc b/doc/datastreamformat.doc index e2c062fd..fee35173 100644 --- a/doc/datastreamformat.doc +++ b/doc/datastreamformat.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/debug.doc b/doc/debug.doc index 882c8d32..d8779b94 100644 --- a/doc/debug.doc +++ b/doc/debug.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/distributingqt.doc b/doc/distributingqt.doc index b7b24cca..9223eb0d 100644 --- a/doc/distributingqt.doc +++ b/doc/distributingqt.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -43,7 +43,7 @@ This document lists the platform-specific files needed to distribute Qt applications. We do not include any compiler-specific files that -may also be retquired. (See also, \link winsystem.html Window +may also be required. (See also, \link winsystem.html Window System-specific Notes\endlink.) \tableofcontents @@ -85,7 +85,7 @@ version is prefixed with \e {-mt}. \section2 Distributing Plugins -You must include any plugin files retquired by the application. +You must include any plugin files required by the application. Plugins must be put into a subdirectory under a directory known to Qt as a plugin directory. The subdirectory must have the name of the diff --git a/doc/dnd.doc b/doc/dnd.doc index 9bddd90e..45acf8ad 100644 --- a/doc/dnd.doc +++ b/doc/dnd.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/editions.doc b/doc/editions.doc index 1128c968..bc3e65ae 100644 --- a/doc/editions.doc +++ b/doc/editions.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/embclasses.doc b/doc/embclasses.doc index 99d98b1b..f0430818 100644 --- a/doc/embclasses.doc +++ b/doc/embclasses.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -129,7 +129,7 @@ typically 2-20KB in size; they can be mmap'd direct from disk in order to save memory). If a QPF font is found which matches a font request no new QRenderedFont need be created for it. It's possible to strip out all QFontFactory support and simply use QPFs if your font needs are modest -(for instance, if you only retquire a few fixed point sizes). Note that +(for instance, if you only require a few fixed point sizes). Note that no best-match loading is performed with QPFs, as opposed to those loaded via QFontManager, so if you don't have the correct QPF for a point size, text in that size will simply not be displayed. diff --git a/doc/embporting.doc b/doc/embporting.doc index 37e39af6..a066a35f 100644 --- a/doc/embporting.doc +++ b/doc/embporting.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/envvars.doc b/doc/envvars.doc index 950582a5..b2950f11 100644 --- a/doc/envvars.doc +++ b/doc/envvars.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/faq.doc b/doc/faq.doc index e36d7504..5b097da1 100644 --- a/doc/faq.doc +++ b/doc/faq.doc @@ -229,7 +229,7 @@ project. Can we transfer the license to another developer? Yes. Qt licences are for the individual use of named developers. If the developer associated with a licence leaves the organization, or -moves on to another project that does not retquire a Qt license, +moves on to another project that does not require a Qt license, another developer can take over the licence. You can change the name of the developer using a licence at any time, but after a change you must wait at least six (6) months before changing again. @@ -342,7 +342,7 @@ software pool to do so without paying license fees. Although it is possible to write free software for internal use, it is difficult to ensure that such software is used and distributed legally. For example, if your free software -retquires any modules that impose conditions on you that +requires any modules that impose conditions on you that contradict the conditions of the GNU GPL, including, but not limited to, software patents, commercial license agreements, copyrighted interface definitions or any sort of diff --git a/doc/features.doc b/doc/features.doc index f6bf05f4..d049f0b7 100644 --- a/doc/features.doc +++ b/doc/features.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/focus.doc b/doc/focus.doc index fe4ed09f..6ba2c1b4 100644 --- a/doc/focus.doc +++ b/doc/focus.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/framebuffer-howto.doc b/doc/framebuffer-howto.doc index 4c855ddf..e37c22b2 100644 --- a/doc/framebuffer-howto.doc +++ b/doc/framebuffer-howto.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/functions.doc b/doc/functions.doc index 5f813903..266c763c 100644 --- a/doc/functions.doc +++ b/doc/functions.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/headers.doc b/doc/headers.doc index 1b412820..42420e83 100644 --- a/doc/headers.doc +++ b/doc/headers.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/hierarchy.doc b/doc/hierarchy.doc index 0dabdb06..1664efb9 100644 --- a/doc/hierarchy.doc +++ b/doc/hierarchy.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/how-to-learn-qt.doc b/doc/how-to-learn-qt.doc index f93986e5..8c5254fe 100644 --- a/doc/how-to-learn-qt.doc +++ b/doc/how-to-learn-qt.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/activeqt-dotnet.html b/doc/html/activeqt-dotnet.html index a65d0d3c..e0cfa0d8 100644 --- a/doc/html/activeqt-dotnet.html +++ b/doc/html/activeqt-dotnet.html @@ -106,7 +106,7 @@ is presented, which includes using a thin MC++ wrapper class around the normal TQt/C++ class. Then, the automated way is presented, which utilizes the <a href="activeqt.html#ActiveTQt">ActiveTQt</a> framework as a generic bridge. The advantage of the first method is that it gives the application developer full -control, while the second method retquires less coding and relieves the +control, while the second method requires less coding and relieves the developer of dealing with the conversion between managed and normal data objects. <p> The impatient reader, who right away wants to see a <a href="qpushbutton.html">TQPushButton</a> and a @@ -405,7 +405,7 @@ available to .NET. This has the positive side effect that the same API is automatically available in <a href="http://www.trolltech.com/products/qsa">TQSA</a>, the cross platform scripting solution for TQt applications, and to COM clients in general. <p> When using the "IJW" method, in priciple the only limitation is the -time retquired to write the wrapper classes and data type conversion +time required to write the wrapper classes and data type conversion functions. <p> <h3> Performance Considerations </h3> diff --git a/doc/html/activeqt-tools-idc.html b/doc/html/activeqt-tools-idc.html index aeec4bee..36ccb3f5 100644 --- a/doc/html/activeqt-tools-idc.html +++ b/doc/html/activeqt-tools-idc.html @@ -59,7 +59,7 @@ type library wll have version x.y. <td valign="top">Unregister the COM server <em>dll</em> </table></center> <p> It is usually never necessary to invoke IDC manually, as the -<tt>qmake</tt> build system takes care of adding the retquired post +<tt>qmake</tt> build system takes care of adding the required post processing steps to the build process. See the <a href="qaxserver.html#4">ActiveTQt build system</a> documentation for details. diff --git a/doc/html/activeqt-tools-testcon.html b/doc/html/activeqt-tools-testcon.html index ca30181a..eea112aa 100644 --- a/doc/html/activeqt-tools-testcon.html +++ b/doc/html/activeqt-tools-testcon.html @@ -51,7 +51,7 @@ VBScript, Perl and Python to program the controls loaded. Example script files using the TQAxWidget2 class are available in the <tt>scripts</tt> subdirectory. <p> Note that the qmake project of this example includes a resource file -<tt>testcon.rc</tt> with a version resource. This is retquired by some +<tt>testcon.rc</tt> with a version resource. This is required by some ActiveX controls (ie. Shockwave ActiveX Controls), which might crash or misbehave otherwise if such version information is missing. <p> To build the tool you must first build the diff --git a/doc/html/assistant-6.html b/doc/html/assistant-6.html index 044ff206..266490db 100644 --- a/doc/html/assistant-6.html +++ b/doc/html/assistant-6.html @@ -81,7 +81,7 @@ body { background: #ffffff; color: black; } <li><p>Start Page- This property specifies which page <em>TQt Assistant</em> should initially display when the profile is used. Usually, this is the HTML file which contains the documentation's table of contents. This property also describes the default location to go to when pressing the home button in <em>TQt Assistant</em>'s main user interface. The start page is specified relative to the location of the profile. The property name is <tt>startpage</tt></p> <li><p>About Menu Text- This property describes the text that appears in the <b>Help</b> menu, e.g. About Application. The property name is <tt>aboutmenutext</tt></p> <li><p>About URL- This property can be used to point to an HTML file that describes the contents in the About dialog that is opened for the <b>Help</b> menu, e.g. About Application. The url is specified relative to the location of the profile. The property name is <tt>abouturl</tt></p> -<li><p><em>TQt Assistant</em> Documentation- This property describes the location of the <em>TQt Assistant</em> documentation. This is retquired since <em>TQt Assistant</em> provides self help, such as the full text search help and the <em>TQt Assistant</em> Manual option in the <b>Help</b> menu. The location is a directory relative to the location of the profile. The property name is <tt>assistantdocs</tt>.</p> +<li><p><em>TQt Assistant</em> Documentation- This property describes the location of the <em>TQt Assistant</em> documentation. This is required since <em>TQt Assistant</em> provides self help, such as the full text search help and the <em>TQt Assistant</em> Manual option in the <b>Help</b> menu. The location is a directory relative to the location of the profile. The property name is <tt>assistantdocs</tt>.</p> </ul><p>To define a profile, one needs to specify a <em>TQt Assistant</em> Document Profile, usually abbreviated <tt>.adp</tt>. The profile is an extension of the Documentation Content File described above. We add a <tt>profile</tt> tag containing <tt>property</tt> tags to the format.</p> <p>An example of a document profile file is shown below:</p> <p><tt>helpdemo.adp</tt></p> diff --git a/doc/html/canvas.html b/doc/html/canvas.html index a005896a..2e2dcf10 100644 --- a/doc/html/canvas.html +++ b/doc/html/canvas.html @@ -39,7 +39,7 @@ body { background: #ffffff; color: black; } shape, size and content, can be freely moved around in the canvas, and can be checked for collisions. Canvas items can be set to move across the canvas automatically and animated canvas items are -supported with <a href="qcanvassprite.html">TQCanvasSprite</a>. (If you retquire 3D graphics see TQt's +supported with <a href="qcanvassprite.html">TQCanvasSprite</a>. (If you require 3D graphics see TQt's <a href="opengl.html">OpenGL module</a>.) <p> The canvas module uses a document/view model. The <a href="qcanvasview.html">TQCanvasView</a> class is used to show a particular view of a canvas. Multiple views can operate diff --git a/doc/html/commonproblems.html b/doc/html/commonproblems.html index 2c14de6a..9670d1cf 100644 --- a/doc/html/commonproblems.html +++ b/doc/html/commonproblems.html @@ -75,7 +75,7 @@ tools are usually located in the <tt>bin</tt> subdirectory of TQt distributions. Either run <tt>"$QTDIR"/bin/moc</tt> and <tt>"$QTDIR"/bin/uic</tt> or add <tt>"$QTDIR"/bin</tt> to your <tt>PATH</tt> and run <a href="moc.html#moc">moc</a> and <tt>uic</tt>. If you use <tt>qmake</tt> the appropriate lines will be added to your Makefiles so that <em>uic</em> and -<em>moc</em> will be executed as retquired. +<em>moc</em> will be executed as required. <p> <dt>Static or shared libraries - Link time <p> <dd>Programmers need to link with the TQt static or shared libraries. The TQt libraries are usually located in the <tt>lib</tt> subdirectory of TQt distributions. diff --git a/doc/html/customlayout.html b/doc/html/customlayout.html index b846fe30..188b7f2b 100644 --- a/doc/html/customlayout.html +++ b/doc/html/customlayout.html @@ -136,7 +136,7 @@ TQLayoutIterator CardLayout::iterator() It must be implemented. It is used by <a href="qlayout.html#add">TQLayout::add</a>(), by the <a href="qlayout.html">TQLayout</a> constructor that takes a layout as parent, and it is used to implement the <a href="qlayout.html#autoAdd">auto-add</a> feature. If your layout -has advanced placement options that retquire parameters, you must +has advanced placement options that require parameters, you must provide extra access functions such as <a href="qgridlayout.html#addMultiCell">TQGridLayout::addMultiCell</a>(). <p> <pre> void CardLayout::addItem( <a href="qlayoutitem.html">TQLayoutItem</a> *item ) diff --git a/doc/html/designer-manual-1.html b/doc/html/designer-manual-1.html index 54ac5563..c6153854 100644 --- a/doc/html/designer-manual-1.html +++ b/doc/html/designer-manual-1.html @@ -32,12 +32,12 @@ body { background: #ffffff; color: black; } <td align="right" valign="center"><img src="logo32.png" align="right" width="64" height="32" border="0"></td></tr></table><p align="right">[<a href="designer-manual.html">Home</a>] [<a href="designer-manual-2.html">Next: Quick Start</a>]</p> <h2 align="center">Preface</h2> <h3><a name="1"></a>Introduction</h3> -<p>This manual presents <em>TQt Designer</em>, a tool for designing and implementing user interfaces built with the TQt multiplatform GUI toolkit. <em>TQt Designer</em> makes it easy to experiment with user interface design. At any time you can generate the code retquired to reproduce the user interface from the files <em>TQt Designer</em> produces, changing your design as often as you like. If you used an earlier version you will find yourself immediately productive in the new version since the interface is very similar. And you will also find new widgets and new and improved functionality which have been developed as a result of your feedback.</p> +<p>This manual presents <em>TQt Designer</em>, a tool for designing and implementing user interfaces built with the TQt multiplatform GUI toolkit. <em>TQt Designer</em> makes it easy to experiment with user interface design. At any time you can generate the code required to reproduce the user interface from the files <em>TQt Designer</em> produces, changing your design as often as you like. If you used an earlier version you will find yourself immediately productive in the new version since the interface is very similar. And you will also find new widgets and new and improved functionality which have been developed as a result of your feedback.</p> <p><em>TQt Designer</em> helps you build user interfaces with layout tools that move and scale your widgets (<em>controls</em> in Windows terminology) automatically at runtime. The resulting interfaces are both functional and attractive, comfortably suiting your users' operating environments and preferences. <em>TQt Designer</em> supports TQt's signals and slots mechanism for type-safe communication between widgets. <em>TQt Designer</em> includes a code editor which you can use to embed your own custom slots inside the generated code. Those who prefer to separate generated code from hand crafted code can continue to use the subclassing approach pioneered in the first version of <em>TQt Designer</em>.<!-- index Controls!Widgets --></p> <p>The manual introduces you to <em>TQt Designer</em> by leading you through the development of example applications. The first seven chapters are tutorials, each designed to be as self-contained as possible. Every chapter, except the first three, assumes that you are familiar with the material in chapters two and three which cover the basics of building a TQt application with <em>TQt Designer</em>. Here's a brief overview of the chapters:</p> <ul><li><p>Chapter one, <a href="designer-manual-2.html">Quick Start</a>, is a fast hands-on tutorial that takes you through the creation of a short, simple dialog application. The aim of this chapter is to give you a feel for how <em>TQt Designer</em> works, with explanations and details deferred to later chapters.</p> <li><p>Chapter two, <a href="designer-manual-3.html">Creating a Main Window Application</a>, introduces <em>TQt Designer</em> and takes you step by step through the creation of a small but fully functional application. Along the way you will learn how to create a main window with menus, toolbars and a status bar. Most of the application's implementation will be covered, but the custom dialogs are deferred until chapter three. In the course of this chapter you will use the form and property editors to customize the application. You'll also learn how to use TQt's signals and slots mechanism and <em>TQt Designer</em>'s built-in code editor to make the application functional. We will also explain how to use <tt>qmake</tt> to generate a Makefile so that you can compile and run the application.</p> -<li><p>In chapter three, <a href="designer-manual-4.html">Creating Dialogs</a>, we will create the custom dialogs retquired by the main window application created in chapter two. In addition to demonstrating various ways of creating dialogs, you will also learn how to lay out forms using the layout tools.</p> +<li><p>In chapter three, <a href="designer-manual-4.html">Creating Dialogs</a>, we will create the custom dialogs required by the main window application created in chapter two. In addition to demonstrating various ways of creating dialogs, you will also learn how to lay out forms using the layout tools.</p> <li><p>Chapter four, <a href="designer-manual-5.html#the-designer-approach">The Designer Approach</a>, provides information on the <em>TQt Designer</em> approach to developing applications, and explains some of the rationale behind <em>TQt Designer</em>.</p> <li><p>Chapter five, <a href="designer-manual-6.html">Subclassing and Dynamic Dialogs</a>, will show you how to subclass a form; this allows you to clearly separate the user interface from the underlying code that implements its functionality. Additional information on <tt>qmake</tt> and <tt>uic</tt> is included in this chapter. This chapter will also explain how you can dynamically load dialogs from<!-- index .ui --> <tt>.ui</tt> files into your application using <a href="qwidgetfactory.html">TQWidgetFactory</a> and how to access the widgets and sub-widgets of these dialogs.</p> <li><p>Chapter six, <a href="designer-manual-7.html">Creating Custom Widgets</a>, explains how you can create your own custom widgets. Both the simple method, that was introduced with the first version of <em>TQt Designer</em>, and the new more powerful method using plugins, are explained.</p> @@ -46,7 +46,7 @@ body { background: #ffffff; color: black; } </ul><p>The remaining chapters provide reference material that explains <em>TQt Designer</em>'s <a href="designer-manual-11.html#reference-menu-options">menu options</a>, <a href="designer-manual-12.html#reference-toolbar-buttons">toolbars</a>, <a href="designer-manual-10.html#reference-key-bindings">key bindings</a>, <a href="designer-manual-13.html#reference-dialogs">dialogs</a>, <a href="designer-manual-14.html#reference-wizards">wizards</a>, and <a href="designer-manual-15.html#reference-windows">windows</a> in detail.</p> <h3><a name="2"></a>What You Should Know</h3> <p>This manual assumes that you have some basic knowledge of C++ and the TQt GUI toolkit. If you need to learn more about C++ or TQt there are a vast number of C++ books available, and a small but increasing number of TQt books. TQt comes with extensive online documentation and many example applications that you can try.</p> -<p>The Enterprise Edition of TQt includes the TQt SQL module. In <a href="designer-manual-8.html">Creating Database Applications</a> we demonstrate how to build SQL applications with <em>TQt Designer</em>; this chapter retquires some knowledge of SQL and relational databases.</p> +<p>The Enterprise Edition of TQt includes the TQt SQL module. In <a href="designer-manual-8.html">Creating Database Applications</a> we demonstrate how to build SQL applications with <em>TQt Designer</em>; this chapter requires some knowledge of SQL and relational databases.</p> <h3><a name="3"></a>What's New in <em>TQt Designer</em> for TQt 3.0?</h3> <p>This version of <em>TQt Designer</em> has a great deal more functionality than its predecessor. For example, the code for custom slots can be edited directly in <em>TQt Designer</em>; main windows with actions, toolbars and menus can be created; layouts that incorporate splitters can be used; and plugins allow you to package any number of custom widgets and make them available to <em>TQt Designer</em>. Many other enhancements have been incorporated, from small improvements in the user interface to improved efficiency, for example the ability to share pixmaps across all the forms in an application.</p> <p>This version of <em>TQt Designer</em> introduces project files which make it easy to switch between all the forms in an application, and to maintain a common set of database settings and images. Although subclassing is fully supported, writing code directly in <em>TQt Designer</em> offers a number of benefits which are covered in <a href="designer-manual-5.html#the-designer-approach">The Designer Approach</a> chapter. A new library, <tt>libtqui</tt>, has also been introduced which allows you to load dialogs dynamically at runtime from <em>TQt Designer</em>'s <tt>.ui</tt> files. This allows you to provide your application's users with considerable interface customizability without them needing to use C++.</p> diff --git a/doc/html/designer-manual-13.html b/doc/html/designer-manual-13.html index c52bbb45..19f2fb74 100644 --- a/doc/html/designer-manual-13.html +++ b/doc/html/designer-manual-13.html @@ -127,7 +127,7 @@ body { background: #ffffff; color: black; } </p> <blockquote><p align="center"><em>Edit Functions</em></p></blockquote> <p>Click <b>Edit|Slots</b> to invoke the <em>Edit Functions</em> dialog. Use this dialog to edit or create slots and functions which are used in conjunction with signals to provide communication between objects.</p> -<p>When this dialog is invoked, all existing slots and functions are shown in the listview. The column headers Function, Return Type, Specifier, Access, Type, and In Use provide details about each function that is listed. Click on any of the column headers to sort the functions. To create a new function, click the <b>New Function</b> button. The new function has a default name that you should replace by typing the new name in the 'Function' line edit. The 'Return Type' is also a default that can be changed by typing in the line edit. To change the 'Specifier' or 'Access', click the combobox and choose the retquired specifier or access. To change the type of a function (function or slot), click the Type combobox. To remove a function, click the function you want to delete, and then click the <b>Delete Function</b> button.</p> +<p>When this dialog is invoked, all existing slots and functions are shown in the listview. The column headers Function, Return Type, Specifier, Access, Type, and In Use provide details about each function that is listed. Click on any of the column headers to sort the functions. To create a new function, click the <b>New Function</b> button. The new function has a default name that you should replace by typing the new name in the 'Function' line edit. The 'Return Type' is also a default that can be changed by typing in the line edit. To change the 'Specifier' or 'Access', click the combobox and choose the required specifier or access. To change the type of a function (function or slot), click the Type combobox. To remove a function, click the function you want to delete, and then click the <b>Delete Function</b> button.</p> <p>Click <b>OK</b> to save all changes made to the functions. Click <b>Cancel</b> to leave the dialog without making any changes to the functions.</p> <a name="dialog-view-connections"></a><h4><a name="4-2"></a>View and Edit Connections Dialog</h4> <p align="center"><img align="middle" src="qs-editconn1.png" width="608" height="391"> @@ -142,10 +142,10 @@ body { background: #ffffff; color: black; } <blockquote><p align="center"><em>Form Settings</em></p></blockquote> <p>Click <b>Edit|Form Settings</b> to invoke the <em>Form Settings</em> dialog. Use this dialog to save the form's settings, pixmap, and layout properties.</p> <h5><a name="4-3-1"></a>Settings</h5> -<p>In the Settings section, you can change or add the name of the class that will be created by typing in the 'Class Name' line edit. Note that the default name is the form name, but it can be changed. You can also enter text to the 'Comment' and 'Author' line edits or leave them blank, since they are not retquired.</p> +<p>In the Settings section, you can change or add the name of the class that will be created by typing in the 'Class Name' line edit. Note that the default name is the form name, but it can be changed. You can also enter text to the 'Comment' and 'Author' line edits or leave them blank, since they are not required.</p> <h5><a name="4-3-2"></a>Pixmaps</h5> <p>The default (for projects) is 'Project Imagefile'. This is the recommended option. Images are handled automatically, with <em>TQt Designer</em> storing the images in a subdirectory, and <tt>uic</tt> producing code that contains the images and the necessary supporting code. Each image is stored just once, no matter how many forms it is used in.</p> -<p>If you do not want <em>TQt Designer</em> to handle the images, (or are not using a project) choose either 'Save Inline' or 'Use Function'. 'Save Inline' saves the pixmaps in the <tt>.ui</tt> files. The disadvantage of this approach is that it stores images in the forms in which they're used, meaning that images cannot be shared across forms. Click 'Use Function' to use your own icon-loader function for loading pixmaps. Type the function's name (with no signature) in the 'Use Function' line edit. This function will be used in the generated code for loading pixmaps. Your function will be called with the text you put in the pixmap property (e.g. the image name) whenever an image is retquired.</p> +<p>If you do not want <em>TQt Designer</em> to handle the images, (or are not using a project) choose either 'Save Inline' or 'Use Function'. 'Save Inline' saves the pixmaps in the <tt>.ui</tt> files. The disadvantage of this approach is that it stores images in the forms in which they're used, meaning that images cannot be shared across forms. Click 'Use Function' to use your own icon-loader function for loading pixmaps. Type the function's name (with no signature) in the 'Use Function' line edit. This function will be used in the generated code for loading pixmaps. Your function will be called with the text you put in the pixmap property (e.g. the image name) whenever an image is required.</p> <h5><a name="4-3-3"></a>Layouts</h5> <p>Click the 'Default Margin' spinbox or the 'Default Spacing' spinbox to change the default layout settings of the current form.</p> <p>To use the functions in the generated code to dynamically retrieve values for the layout's default margin and spacing, check the Use Functions chechbox. In the Margin and Spacing line edits, specify the function names (no signatures or parantheses) which should be used to retrieve the margin and spacing.</p> @@ -233,7 +233,7 @@ body { background: #ffffff; color: black; } <h3><a name="7"></a>The Tools Dialog</h3> <a name="dialog-edit-custom-widgets"></a><h4><a name="7-1"></a>Edit Custom Widgets Dialog</h4> <p>The <em>Edit Custom Widgets</em> dialog is invoked by clicking <b>Tools|Custom|Edit Custom Widgets</b>. Use this dialog to create custom widgets.</p> -<p>Custom widgets are created in code. They may contain a combination of existing widgets but with additional functionality, slots and signals, or they may be written from scratch, or a mixture of both. A custom widget is often a specialization (subclass) of another widget or a combination of widgets working together or a blend of both these approaches. If you simply want a collection of widgets in a particular configuration it is easiest to create them, select them as a group, and copy and paste them as retquired within <em>TQt Designer</em>. Custom widgets are generally created when you need to add new functionality to existing widgets or groups of widgets. To add create a new widget, click the <b>New Widget</b> button. You will find more information about adding new widgets in the 'Definitions Section'. To load a file which contains descriptions of custom widgets, click the <b>Load Descriptions</b> button. Clicking this button invokes the <em>Open Dialog</em>. To save the descriptions of the listed custom widgets, click the <b>Save Descriptions</b> button, which invokes the <em>Save As Dialog</em>. To delete a widget, click the widget in the listbox and then click the <b>Delete Widget</b> button.</p> +<p>Custom widgets are created in code. They may contain a combination of existing widgets but with additional functionality, slots and signals, or they may be written from scratch, or a mixture of both. A custom widget is often a specialization (subclass) of another widget or a combination of widgets working together or a blend of both these approaches. If you simply want a collection of widgets in a particular configuration it is easiest to create them, select them as a group, and copy and paste them as required within <em>TQt Designer</em>. Custom widgets are generally created when you need to add new functionality to existing widgets or groups of widgets. To add create a new widget, click the <b>New Widget</b> button. You will find more information about adding new widgets in the 'Definitions Section'. To load a file which contains descriptions of custom widgets, click the <b>Load Descriptions</b> button. Clicking this button invokes the <em>Open Dialog</em>. To save the descriptions of the listed custom widgets, click the <b>Save Descriptions</b> button, which invokes the <em>Save As Dialog</em>. To delete a widget, click the widget in the listbox and then click the <b>Delete Widget</b> button.</p> <p>Click <b>Close</b> to leave the Edit Custom Widgets dialog.</p> <h5><a name="7-1-1"></a>The Definition Tab</h5> <p align="center"><img align="middle" src="rd-cwidgdef.png" width="720" height="412"> diff --git a/doc/html/designer-manual-14.html b/doc/html/designer-manual-14.html index c58d13c9..471ff732 100644 --- a/doc/html/designer-manual-14.html +++ b/doc/html/designer-manual-14.html @@ -43,7 +43,7 @@ body { background: #ffffff; color: black; } <p align="center"><img align="middle" src="qd-mainwinwzdpage2.png" width="658" height="418"> </p> <h4><a name="2-2"></a>Setup Toolbar</h4> -<p>The 'Setup Toolbar' wizard page is used to populate a toolbar with actions from each of the default action categories. Click the Category combobox to select which set of actions you wish to work on. The Actions listbox lists the actions available for the current category. The Toolbar listbox lists the toolbar buttons you want to create. Click the blue left and right arrow buttons to move actions into or out of the Toolbar list box. Click the blue up and down arrow buttons to move actions up and down within the Toolbar list box. Note that the '<Separator>' item in the Actions list box may be moved to the Toolbar list box as often as retquired and will cause a separator to appear in the finished toolbar.</p> +<p>The 'Setup Toolbar' wizard page is used to populate a toolbar with actions from each of the default action categories. Click the Category combobox to select which set of actions you wish to work on. The Actions listbox lists the actions available for the current category. The Toolbar listbox lists the toolbar buttons you want to create. Click the blue left and right arrow buttons to move actions into or out of the Toolbar list box. Click the blue up and down arrow buttons to move actions up and down within the Toolbar list box. Note that the '<Separator>' item in the Actions list box may be moved to the Toolbar list box as often as required and will cause a separator to appear in the finished toolbar.</p> <p>Click <b>Back</b> if you want to return to the 'Choose available menus and toolbars' wizard page. Click <b>Finish</b> to populate the main window and to exit the wizard. Click <b>Cancel</b> on any of the wizard pages to leave the wizard without making any changes.</p> <h3><a name="3"></a>Data Table Wizard</h3> <p>The Data Table Wizard is automatically invoked by clicking the datatable widget and placing it on the form. The datatable widget is used to create tabular views of database data.</p> diff --git a/doc/html/designer-manual-16.html b/doc/html/designer-manual-16.html index 7d472cbc..df37d5e9 100644 --- a/doc/html/designer-manual-16.html +++ b/doc/html/designer-manual-16.html @@ -123,7 +123,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -185,7 +185,7 @@ body { background: #ffffff; color: black; } </pre> <a name="exportmacro"></a><h4><a name="1-7"></a>exportmacro</h4> <p>This tag is only relevant to Windows users.</p> -<p>If you have a class that retquires some Windows-specific export macro, e.g. for classes in a DLL that need to be declared like this: <tt>class win_specific_declaration_goes_here Class</tt>, you can use the <tt><exportmacro></tt> tag. (In standard TQt we use the <tt>Q_EXPORT</tt> macro, e.g. <tt>class Q_EXPORT TQWidget</tt>.) If you use this tag you must also:</p> +<p>If you have a class that requires some Windows-specific export macro, e.g. for classes in a DLL that need to be declared like this: <tt>class win_specific_declaration_goes_here Class</tt>, you can use the <tt><exportmacro></tt> tag. (In standard TQt we use the <tt>Q_EXPORT</tt> macro, e.g. <tt>class Q_EXPORT TQWidget</tt>.) If you use this tag you must also:</p> <ol type=1><li><p><a href="designer-manual-16.html#1-11">include</a> the file which contains the macro definition;</p> <li><p>add the export macro to the form -- this is achieved by entering the macro's name in the 'export macro' sub-property of the form's name property.</p> </ol><p>Following these steps will ensure that <a href="uic.html">uic</a> will create the correct <tt>class YOUR_MACRO Form</tt> declarations.</p> diff --git a/doc/html/designer-manual-3.html b/doc/html/designer-manual-3.html index 4d584665..c46a8a8c 100644 --- a/doc/html/designer-manual-3.html +++ b/doc/html/designer-manual-3.html @@ -87,7 +87,7 @@ body { background: #ffffff; color: black; } <p align="center"><img align="middle" src="mw-menuwiz.png" width="616" height="420"> </p> <blockquote><p align="center"><em>Main Window Wizard- Choosing menus and toolbars</em></p></blockquote> -<li><!-- index Creating Toolbars --><!-- index Toolbars, Creating --><!-- index Toolbar Buttons!Adding --><!-- index Adding!Toolbar Buttons --><!-- index Separator!Menu item --><!-- index Separator!Toolbar button --><p>The <em>Setup Toolbar</em> wizard page is used to populate a toolbar with actions from each of the default action categories. The Category combobox is used to select which set of actions you wish to choose from. The Actions list box lists the actions available for the current category. The Toolbar listbox lists the toolbar buttons you want to create. The blue left and right arrow buttons are used to move actions into or out of the Toolbar list box. The blue up and down arrow buttons are used to move actions up and down within the Toolbar list box. Note that the '<Separator>' item in the Actions list box may be moved to the Toolbar list box as often as retquired and will cause a separator to appear in the finished toolbar.</p> +<li><!-- index Creating Toolbars --><!-- index Toolbars, Creating --><!-- index Toolbar Buttons!Adding --><!-- index Adding!Toolbar Buttons --><!-- index Separator!Menu item --><!-- index Separator!Toolbar button --><p>The <em>Setup Toolbar</em> wizard page is used to populate a toolbar with actions from each of the default action categories. The Category combobox is used to select which set of actions you wish to choose from. The Actions list box lists the actions available for the current category. The Toolbar listbox lists the toolbar buttons you want to create. The blue left and right arrow buttons are used to move actions into or out of the Toolbar list box. The blue up and down arrow buttons are used to move actions up and down within the Toolbar list box. Note that the '<Separator>' item in the Actions list box may be moved to the Toolbar list box as often as required and will cause a separator to appear in the finished toolbar.</p> <p>Copy the New, Open, and Save Actions to the Toolbar list box. Copy a <Separator> to the Toolbar list box. Change the Category to Edit and copy the Cut, Copy, and Find actions to the Toolbar list box. Click <b>Next</b> and then click <b>Finish</b>.</p> <p>Click <b>File|Save</b> and save the form as <tt>mainform.ui</tt>.</p> <p align="center"><img align="middle" src="mw-settoolwiz.png" width="616" height="420"> @@ -126,8 +126,8 @@ body { background: #ffffff; color: black; } <p align="center"><img align="middle" src="mw-objexplor.png" width="328" height="465"> </p> <blockquote><p align="center"><em>Object Explorer</em></p></blockquote> -<!-- index Code Editing --><!-- index Subclassing --><!-- index Forward declarations --><!-- index Includes --><!-- index Adding!Code --><!-- index Adding!Forward declarations --><!-- index Adding!Includes --><!-- index Adding!Class variables --><!-- index Class variables --><!-- index Deleting!Forward declarations --><!-- index Deleting!Includes --><!-- index Deleting!Class variables --><!-- index Forms!Forward declarations --><!-- index Forms!Class variables --><!-- index Forms!Code editing --><!-- index Forms!destructor --><!-- index Forms!constructor --><p>In the original version of <em>TQt Designer</em> if you wanted to provide code for a form you had to subclass the form and put your code in the subclass. This version fully supports the subclassing approach, but now provides an alternative: placing your code directly into forms. Writing code in <em>TQt Designer</em> is not quite the same as subclassing, for example you cannot get direct access to the form's constructor or destructor. If you need code to be executed by the constructor create a slot called<!-- index init() --> <tt>void init()</tt>; if it exists it will be called from the constructor. Similarly, if you need code to be executed before destruction create a slot called<!-- index destroy() --> <tt>void destroy()</tt>. You can also add your own class variables which will be put in the generated constructor's code, and you can add forward declarations and any includes you retquire. To add a variable or declaration, right click the appropriate item, e.g. Class Variables, then click <b>New</b> then enter your text, e.g. <tt>TQString m_filename</tt>. If one or more items exist, right click to pop up a menu that has New, Edit and Delete options. If you want to enter multiple items, e.g. multiple include files or multiple data members, it is easiest to right click in the relevant section, then click <b>Edit</b> to invoke an Edit dialog. To edit code, just click the name of a function to invoke the code editor. Code editing and creating slots are covered later in the chapter.</p> -<!-- index Subclassing --><p>If you subclass the form you create your own<!-- index .cpp --> <tt>.cpp</tt> files which can contain your own constructor, destructor, functions, slots, declarations and variables as your retquirements dictate. (See <a href="designer-manual-6.html#1">Subclassing</a> for more information.)</p> +<!-- index Code Editing --><!-- index Subclassing --><!-- index Forward declarations --><!-- index Includes --><!-- index Adding!Code --><!-- index Adding!Forward declarations --><!-- index Adding!Includes --><!-- index Adding!Class variables --><!-- index Class variables --><!-- index Deleting!Forward declarations --><!-- index Deleting!Includes --><!-- index Deleting!Class variables --><!-- index Forms!Forward declarations --><!-- index Forms!Class variables --><!-- index Forms!Code editing --><!-- index Forms!destructor --><!-- index Forms!constructor --><p>In the original version of <em>TQt Designer</em> if you wanted to provide code for a form you had to subclass the form and put your code in the subclass. This version fully supports the subclassing approach, but now provides an alternative: placing your code directly into forms. Writing code in <em>TQt Designer</em> is not quite the same as subclassing, for example you cannot get direct access to the form's constructor or destructor. If you need code to be executed by the constructor create a slot called<!-- index init() --> <tt>void init()</tt>; if it exists it will be called from the constructor. Similarly, if you need code to be executed before destruction create a slot called<!-- index destroy() --> <tt>void destroy()</tt>. You can also add your own class variables which will be put in the generated constructor's code, and you can add forward declarations and any includes you require. To add a variable or declaration, right click the appropriate item, e.g. Class Variables, then click <b>New</b> then enter your text, e.g. <tt>TQString m_filename</tt>. If one or more items exist, right click to pop up a menu that has New, Edit and Delete options. If you want to enter multiple items, e.g. multiple include files or multiple data members, it is easiest to right click in the relevant section, then click <b>Edit</b> to invoke an Edit dialog. To edit code, just click the name of a function to invoke the code editor. Code editing and creating slots are covered later in the chapter.</p> +<!-- index Subclassing --><p>If you subclass the form you create your own<!-- index .cpp --> <tt>.cpp</tt> files which can contain your own constructor, destructor, functions, slots, declarations and variables as your requirements dictate. (See <a href="designer-manual-6.html#1">Subclassing</a> for more information.)</p> </blockquote> <h4><a name="4-3"></a>Adding Custom Actions</h4> <p>We want to provide the user with actions that are specific to our application. We want to provide the ability to switch between the two views we will be offering, and allow the user to add colors and set their preferred options. We'll prepare the way by creating a new menu for the view options and by adding a separator to the toolbar.</p> @@ -301,7 +301,7 @@ body { background: #ffffff; color: black; } <p align="center"><img align="middle" src="mw-conn4.png" width="600" height="407"> </p> <h4><a name="6-5"></a>Editing the Code: Setting Up</h4> -<p>There is quite a lot of code to include in the application, but this does not mean that a lot of typing is retquired! All the code is reproduced here so, if you're reading an electronic copy, you can simply cut and paste. If you're reading a print copy, all the code is provided in <tt>/tools/designer/examples/colortool</tt>; simply open the relevant <tt>.ui.h</tt> files and copy and paste from there into your own version of the project.</p> +<p>There is quite a lot of code to include in the application, but this does not mean that a lot of typing is required! All the code is reproduced here so, if you're reading an electronic copy, you can simply cut and paste. If you're reading a print copy, all the code is provided in <tt>/tools/designer/examples/colortool</tt>; simply open the relevant <tt>.ui.h</tt> files and copy and paste from there into your own version of the project.</p> <blockquote> <p align="center"><b> Cutting & Pasting Into the Code Editor</b></p> <p>If you cut and paste code from this manual, because we've indented the code for readability, the code will be over-indented in <em>TQt Designer</em>. This is easily solved. Simply select the function containing the pasted code (either with the mouse, or <b>Shift+Arrow</b>s) and press <b>Tab</b>: this will make <em>TQt Designer</em> fix the indentation. Note that you must select the <em>entire</em> function, including its name and parameters.</p> @@ -421,7 +421,7 @@ body { background: #ffffff; color: black; } } } </pre> - <p>This function is at the heart of the application. It visually presents the data to the user. If the table is "dirty" (e.g. if the user has added or deleted colors in the icon view, or has opened a color file) we will populate the table. We start by deleting the contents of every cell. Next we change the number of rows to equal the number of colors in the colors map. For each color we want to display a little square that shows the color, so we create a pixmap of the retquired size.</p> + <p>This function is at the heart of the application. It visually presents the data to the user. If the table is "dirty" (e.g. if the user has added or deleted colors in the icon view, or has opened a color file) we will populate the table. We start by deleting the contents of every cell. Next we change the number of rows to equal the number of colors in the colors map. For each color we want to display a little square that shows the color, so we create a pixmap of the required size.</p> <p>We now create an iterator for our colors map, and iterate over every color. The colors map has the user's color names as its keys, and <a href="qcolor.html">TQColor</a> instances as values. We retrieve the color and fill our pixmap with that color. We then set the "Name" column (column <tt>COL_NAME</tt>), to have the color's name (<tt>it.key()</tt>) and the pixmap we've just filled with that color. <a href="qcolor.html">TQColor</a>'s <tt>name()</tt> function returns a string that is the hex representation of a color, e.g. "#12AB2F"; we retrieve this and set the second ("Hex") column to this value.</p> <p>If the user wants to see if which colors are web colors we create a <a href="qchecktableitem.html">TQCheckTableItem</a>, and check it if it is a web color. (We'll cover <tt>isWebColor()</tt> shortly.) We then insert this <a href="qchecktableitem.html">TQCheckTableItem</a> into the "Web" column.</p> <p>Having populated the table we call <tt>adjustColumn()</tt> to ensure that each column is just wide enough to show its widest entry, and show or hide the "Web" column depending on the user's preference.</p> @@ -762,7 +762,7 @@ Captures: cap(1) cap(2) cap(3) cap(4) <p>This is the second revision of this function. Now we only exit if the user has had the opportunity to save any unsaved changes. (We'll make a third and final version of this function later, when we deal with saving user settings.)</p> <p>Try making and running the program. If you have <tt>rgb.txt</tt> on your system try loading it and saving it under a new name for testing purposes. If you don't have this file, save the standard colors and use those. In the next section we'll cover adding and deleting colors so that you can create your own color files. (If it doesn't build see the <a href="designer-manual-4.html#6">Troubleshooting</a> section.)</p> <h4><a name="6-28"></a>Editing the Code: The Edit Options</h4> -<p>Adding a new color, finding a color and handling user options all retquire custom dialogs, so we'll defer them until chapter three when we deal with dialogs.</p> +<p>Adding a new color, finding a color and handling user options all require custom dialogs, so we'll defer them until chapter three when we deal with dialogs.</p> <h4><a name="6-29"></a>editCut()</h4> <pre> void MainForm::editCut() { diff --git a/doc/html/designer-manual-4.html b/doc/html/designer-manual-4.html index 17b27fcf..4f1f7102 100644 --- a/doc/html/designer-manual-4.html +++ b/doc/html/designer-manual-4.html @@ -396,7 +396,7 @@ body { background: #ffffff; color: black; } } } </pre> - <p>We create a new options form, passing it TRUE to make it modal. We set the radio buttons depending on the current setting of the <tt>m_clip_as</tt> variable. We set the check box to correspond with the <tt>m_show_web</tt> variable. We execute the form, and if the user clicks <b>OK</b>, we reflect their choices back into the relevant main form variables. If the user changed the <tt>m_show_web</tt> variable (by clicking the webCheckBox), we mark the table as "dirty" since it will need updating. We then call <tt>populate()</tt> which will update the table view if retquired.</p> + <p>We create a new options form, passing it TRUE to make it modal. We set the radio buttons depending on the current setting of the <tt>m_clip_as</tt> variable. We set the check box to correspond with the <tt>m_show_web</tt> variable. We execute the form, and if the user clicks <b>OK</b>, we reflect their choices back into the relevant main form variables. If the user changed the <tt>m_show_web</tt> variable (by clicking the webCheckBox), we mark the table as "dirty" since it will need updating. We then call <tt>populate()</tt> which will update the table view if required.</p> <p>Because we use our OptionsForm and access its radio buttons and checkbox we must add "optionsform.h", "qradiobutton.h" and "qcheckbox.h" to our includes in implementation. (Click Object Explorer's Members tab, right click "Includes (in Implementation)", then click <b>Edit</b>. Click <b>Add</b> and enter "optionsform.h"; click <b>Add</b> again and enter "qradiobutton.h"; click <b>Add</b> again and enter "qcheckbox.h". Press <b>Enter</b>, then click <b>Close</b>.)</p> <p>You should now have added the following declarations to your includes (in implementation):</p> <ul><li><p>"optionsform.h"</p> diff --git a/doc/html/designer-manual-5.html b/doc/html/designer-manual-5.html index 61b38dff..96337521 100644 --- a/doc/html/designer-manual-5.html +++ b/doc/html/designer-manual-5.html @@ -45,11 +45,11 @@ body { background: #ffffff; color: black; } <ul><li><p>Grouping forms that belong together.</p> <li><p>Sharing images between different forms.</p> <li><p>Sharing database information between different forms.</p> -</ul><p>The following sections explain these benefits in more detail, and why project management is retquired to achieve them.</p> +</ul><p>The following sections explain these benefits in more detail, and why project management is required to achieve them.</p> <h4><a name="2-1"></a>Grouping forms</h4> <p>Grouping forms means that <em>TQt Designer</em> maintains a list of the <tt>.ui</tt> files that belong to the same project. This makes it easy to switch between forms with a single mouse click.</p> <h4><a name="2-2"></a>Sharing images in a image collection</h4> -<p>In TQt 2.x's <em>TQt Designer</em> each form included the images it retquired and no images were shared. This led to duplication when several forms needed to use the same images. Furthermore the images were stored in the XML <tt>.ui</tt> files which made them large.</p> +<p>In TQt 2.x's <em>TQt Designer</em> each form included the images it required and no images were shared. This led to duplication when several forms needed to use the same images. Furthermore the images were stored in the XML <tt>.ui</tt> files which made them large.</p> <p>As a workaround, we introduced a pixmap-loading function that you could define in <em>TQt Designer</em>. It then was your responsibility to provide the implementation of this function in your application code. The big disadvantage of this approach was that you couldn't see the images during the design process in <em>TQt Designer</em>. This not only makes designing a form less visually interesting, but also has a noticeable impact on geometry management.</p> <p>In the TQt 3.0 version of <em>TQt Designer</em> we've introduced the concept of a project image collection. If you use a project you can add images to the project's image collection, and these images can be shared and used by any of the forms you include in the project. The images are stored as PNGs (portable network graphics) in a subdirectory, <tt>images/</tt>, inside the project's directory. Whenever you modify the image collection, <em>TQt Designer</em> creates a source file which contains both the image data in binary format and a function to instantiate the images. The images are accessible by all forms in the project and the data is shared.</p> <p>A further benefit of using an image collection is that the images are added to the default TQMimeSourceFactory. This way they are accessible from rich-text labels, What's This? context help and even tooltips through standard HTML image tags. The <em>source</em> argument of the image tag is simply the image's name in the image collection. This also works during the design process in <em>TQt Designer</em>.</p> @@ -59,7 +59,7 @@ body { background: #ffffff; color: black; } <p>In most non-trivial database applications you will want to access the database from more than one form. This is why the <tt>.db</tt> file is part of a project, not just part of a single form.</p> <h4><a name="2-4"></a>.pro files</h4> <p><em>TQt Designer</em> needs to store information on projects, for example, the list of forms, the image collection and information about available databases and how to access them. The majority of TQt users already use a project file format to create multiplatform makefiles: <tt>tmake</tt> (and with TQt 3.0 <tt>qmake</tt>) project <tt>.pro</tt> files. These files already contain the list of forms, <tt>.ui</tt> files, used in the project for <tt>uic</tt>.</p> -<p>We've extended the sections in the <tt>.pro</tt> file to include the extra information that <em>TQt Designer</em> needs to manage projects. For example, when you add a form to your project in <em>TQt Designer</em>, it is automatically added to the FORMS section of the project file, and thus <tt>qmake</tt> will generate the retquired build rules without any further work. Similarly, the images are added to the IMAGES section and thus gets automatically compiled into your executable.</p> +<p>We've extended the sections in the <tt>.pro</tt> file to include the extra information that <em>TQt Designer</em> needs to manage projects. For example, when you add a form to your project in <em>TQt Designer</em>, it is automatically added to the FORMS section of the project file, and thus <tt>qmake</tt> will generate the required build rules without any further work. Similarly, the images are added to the IMAGES section and thus gets automatically compiled into your executable.</p> <p>We don't force you to use <tt>qmake</tt>; if you prefer another build system, for example automake/autoconf or jam, you can still continue to use it. Look upon the <tt>.pro</tt> file as a file that describes the GUI part of your application. All you need to do -- as previously -- is add the <tt>.ui</tt> files and the images collection to your own Makefiles.</p> <h3><a name="3"></a>Extending the functionality of a form</h3> <p>First let us look at a small figure that shows the relationship between <tt>.ui</tt> files, generated code and application code:</p> diff --git a/doc/html/designer-manual-6.html b/doc/html/designer-manual-6.html index 9c9845df..e6825b8e 100644 --- a/doc/html/designer-manual-6.html +++ b/doc/html/designer-manual-6.html @@ -95,7 +95,7 @@ int main( int argc, char *argv[] ) } </pre> <p>Note that we're including <tt>creditformbase.h</tt> and instantiating a CreditFormBase object; once we've written our subclass we'll replace the header with our subclass, <tt>creditform.h</tt>, and instantiate a CreditForm.</p> -<p>We can now generate the application with <tt>qmake</tt>, e.g. <tt>qmake -o Makefile credit.pro</tt>, make it and run it. The form should run fine, but doesn't yet have the behaviour we retquire.</p> +<p>We can now generate the application with <tt>qmake</tt>, e.g. <tt>qmake -o Makefile credit.pro</tt>, make it and run it. The form should run fine, but doesn't yet have the behaviour we require.</p> <h5><a name="1-3-3"></a>Creating the Subclass</h5> <p>We need to create a header and an implementation file for our subclass. The code for our subclass is minimal. The header file is <tt>qt/tools/designer/examples/credit/creditform.h</tt>:</p> <pre> #include "creditformbase.h" @@ -174,7 +174,7 @@ FORMS = mainform.ui LANGUAGE = C++ INCLUDEPATH += $(QTDIR)/tools/designer/uilib </pre> -<p>We do <em>not</em> include the <tt>creditformbase.ui</tt> file since this file will be read at runtime, as we'll see shortly. We must include the <tt>tqui</tt> library since the functionality we retquire is not part of the standard TQt library.</p> +<p>We do <em>not</em> include the <tt>creditformbase.ui</tt> file since this file will be read at runtime, as we'll see shortly. We must include the <tt>tqui</tt> library since the functionality we require is not part of the standard TQt library.</p> <h4><a name="2-2"></a>Creating main.cpp</h4> <p>The<!-- index main.cpp --> <tt>main.cpp</tt> is quite standard. It will invoke the form we're going to create in <em>TQt Designer</em> as its main form. This form will then load and execute the dynamic dialog.</p> <pre> #include <<a href="qapplication-h.html">qapplication.h</a>> @@ -217,7 +217,7 @@ INCLUDEPATH += $(QTDIR)/tools/designer/uilib delete creditForm; } </pre> - <p>The<!-- index create() --> <tt>create()</tt> function is a static <a href="qwidgetfactory.html">TQWidgetFactory</a> function. It loads the specified<!-- index .ui --> <tt>.ui</tt> file and returns a pointer to the toplevel <a href="qwidget.html">TQWidget</a> created from the<!-- index .ui --> <tt>.ui</tt> file. We have cast the pointer to <a href="qdialog.html">TQDialog</a> since we know that the <tt>creditformbase.ui</tt> file defines a <a href="qdialog.html">TQDialog</a>. After creating the dialog we<!-- index exec() --> <tt>exec()</tt> it. If the user clicked <b>OK</b> the dialog returns Accepted and we enter the body of the <tt>if</tt> statement. We want to know the amount of credit that the user selected. We call the<!-- index child() --> <tt>child()</tt> function on the dialog passing it the name of the widget we're interested in. The<!-- index child() --> <tt>child()</tt> function returns a pointer to the widget with the name we passed, or returns 0 if no widget of that name was found. In the example we call<!-- index child() --> <tt>child()</tt> to get a pointer to the 'amountSpinBox'. If the pointer we get back is not 0 we set the rating text to the amount in the dialog's spin box. At the end we delete the dynamic dialog. Deleting the dialog ensures that we free up its resources as soon as it is no longer retquired.</p> + <p>The<!-- index create() --> <tt>create()</tt> function is a static <a href="qwidgetfactory.html">TQWidgetFactory</a> function. It loads the specified<!-- index .ui --> <tt>.ui</tt> file and returns a pointer to the toplevel <a href="qwidget.html">TQWidget</a> created from the<!-- index .ui --> <tt>.ui</tt> file. We have cast the pointer to <a href="qdialog.html">TQDialog</a> since we know that the <tt>creditformbase.ui</tt> file defines a <a href="qdialog.html">TQDialog</a>. After creating the dialog we<!-- index exec() --> <tt>exec()</tt> it. If the user clicked <b>OK</b> the dialog returns Accepted and we enter the body of the <tt>if</tt> statement. We want to know the amount of credit that the user selected. We call the<!-- index child() --> <tt>child()</tt> function on the dialog passing it the name of the widget we're interested in. The<!-- index child() --> <tt>child()</tt> function returns a pointer to the widget with the name we passed, or returns 0 if no widget of that name was found. In the example we call<!-- index child() --> <tt>child()</tt> to get a pointer to the 'amountSpinBox'. If the pointer we get back is not 0 we set the rating text to the amount in the dialog's spin box. At the end we delete the dynamic dialog. Deleting the dialog ensures that we free up its resources as soon as it is no longer required.</p> <p>We used the<!-- index child() --> <tt>child()</tt> to gain access to a widget within the dynamic dialog, passing it the name of the widget we were interested in. In some situations we might not know what a widget is called. We can access the first widget of a specified class by calling<!-- index child() --> <tt>child()</tt> with a null widget name and a classname, e.g. <tt>child(0,"TQPushButton")</tt>. This will return a pointer to the first <a href="qpushbutton.html">TQPushButton</a> it finds (or 0 if there isn't one). If you want pointers to all the widgets of a given class you can call the<!-- index TQObject::queryList() --> <tt>TQObject::queryList()</tt> function, passing it the name of the class. It returns a <a href="qobjectlist.html">TQObjectList</a> pointer which points to every object in the dialog that is derived from the given class. See the online <a href="http://doc.trolltech.com/qobject.html">TQObject</a> documentation for further details.</p> <h5><a name="2-3-3"></a>Implementing Slots for Dynamic Dialogs</h5> <!-- index Signals and Slots!Dynamic Dialogs --><!-- index Dynamic Dialogs --><p>There is one outstanding issue that we haven't addressed: the dynamic dialog does not have the behaviour of the original credit dialog because we have not implemented the <tt>setAmount()</tt> slot. We can implement slots for dynamic dialogs by creating a <a href="qobject.html">TQObject</a> subclass. We then create an instance of this subclass and pass a pointer to it to the<!-- index TQWidgetFactory::create() --> <tt>TQWidgetFactory::create()</tt> function which will connect the dynamic dialog's signals to the slots implemented in our subclass.</p> @@ -260,7 +260,7 @@ private: }; </pre> <!-- index Macros!Q_OBJECT --><!-- index Q_OBJECT!Macros --><p>Our class must be a <a href="qobject.html">TQObject</a> subclass and because we're using signals and slots it must include the <tt>Q_OBJECT</tt> macro. We declare a function and the <tt>setAmount()</tt> slot that we wish to implement as well as a private <a href="qdialog.html">TQDialog</a> pointer.</p> -<p>The implementation retquires the header files of the classes it uses:</p> +<p>The implementation requires the header files of the classes it uses:</p> <pre> #include <<a href="qradiobutton-h.html">qradiobutton.h</a>> #include <<a href="qspinbox-h.html">qspinbox.h</a>> #include "receiver.h" diff --git a/doc/html/designer-manual-7.html b/doc/html/designer-manual-7.html index 8471e5eb..5f28e2d8 100644 --- a/doc/html/designer-manual-7.html +++ b/doc/html/designer-manual-7.html @@ -68,8 +68,8 @@ body { background: #ffffff; color: black; } <a href="qpushbutton.html">TQPushButton</a> *rewind = new <a href="qpushbutton.html">TQPushButton</a>( TQPixmap( rewind_xpm ), 0, this, "vcr_rewind" ); layout-><a href="qboxlayout.html#addWidget">addWidget</a>( rewind ); </pre> - <p>We create a <a href="qhboxlayout.html">TQHBoxLayout</a> in which we'll place the buttons. We've only shown the rewind button in the code above since all the others are identical except for the names of the buttons, pixmaps and signals. For each of the buttons we retquire we call the <a href="qpushbutton.html">TQPushButton</a> constructor passing it the appropriate embedded pixmap. We then add it to the layout. Finally we connect the button's<!-- index clicked() --> <tt>clicked()</tt> signal to the appropriate <em>signal</em>. Since the<!-- index clicked() --> <tt>clicked()</tt> signals aren't specific to our widget we want to emit signals that reflect the widget's use. The <tt>rewind()</tt>, <tt>play()</tt>, etc. signals are meaningful in the context of our widget so we propagate each button's<!-- index clicked() --> <tt>clicked()</tt> signal to the appropriate widget-specific signal.</p> -<!-- index Forms!Creating Test Harnesses --><p>The implementation is complete, but to make sure that our widget compiles and runs we'll create a tiny test harness. The test harness will retquire two files, a<!-- index .pro --> <tt>.pro</tt> project file and a<!-- index main.cpp --> <tt>main.cpp</tt>. The <tt>qt/tools/designer/examples/vcr/vcr.pro</tt> project file:</p> + <p>We create a <a href="qhboxlayout.html">TQHBoxLayout</a> in which we'll place the buttons. We've only shown the rewind button in the code above since all the others are identical except for the names of the buttons, pixmaps and signals. For each of the buttons we require we call the <a href="qpushbutton.html">TQPushButton</a> constructor passing it the appropriate embedded pixmap. We then add it to the layout. Finally we connect the button's<!-- index clicked() --> <tt>clicked()</tt> signal to the appropriate <em>signal</em>. Since the<!-- index clicked() --> <tt>clicked()</tt> signals aren't specific to our widget we want to emit signals that reflect the widget's use. The <tt>rewind()</tt>, <tt>play()</tt>, etc. signals are meaningful in the context of our widget so we propagate each button's<!-- index clicked() --> <tt>clicked()</tt> signal to the appropriate widget-specific signal.</p> +<!-- index Forms!Creating Test Harnesses --><p>The implementation is complete, but to make sure that our widget compiles and runs we'll create a tiny test harness. The test harness will require two files, a<!-- index .pro --> <tt>.pro</tt> project file and a<!-- index main.cpp --> <tt>main.cpp</tt>. The <tt>qt/tools/designer/examples/vcr/vcr.pro</tt> project file:</p> <pre>TEMPLATE = app LANGUAGE = C++ TARGET = vcr @@ -104,12 +104,12 @@ DBFILE = vcr.db </ol><p>The remaining items to be completed will depend on the characteristics of the widget you've created. If, for example, your widget can be used to contain other widgets you'd check the Container Widget checkbox. In the case of our Vcr example the only items we need to add are its signals.</p> <p>Click the Signals tab. Click the <b>New Signal</b> button and type in the signal name 'rewind()'. Click <b>New Signal</b> again and this time type in 'play()'. Add the 'next()' and 'stop()' signals in the same way.</p> <p>Since our example hasn't any slots or properties we've finished and can click <b>Close</b>. A new icon will appear in <em>TQt Designer</em>'s toolbars which represents the new widget. If you create a new form you can add Vcr widgets and connect the Vcr's signals to your slots.</p> -<p>Incorporating custom widgets that have their own slots and properties is achieved in a similar way to adding signals. All the retquired information is in our custom widget's header file.</p> +<p>Incorporating custom widgets that have their own slots and properties is achieved in a similar way to adding signals. All the required information is in our custom widget's header file.</p> <a name="creatingplugins"></a><h3><a name="2"></a>Creating Custom Widgets with Plugins</h3> <!-- index Custom Widgets!Plugins --><!-- index Plugins!Implementing Custom Widgets --><p>This section will show you how to write a custom widget and how to embed the custom widget into a plugin. There are no restrictions or special considerations that must be taken into account when creating a widget that is destined to become a plugin. If you are an experienced TQt programmer you can safely skip the section on creating a custom widget and go directly to <a href="designer-manual-7.html#2-2">Creating a Plugin</a>.</p> <p>Be aware that if you use the plugin approach to custom widgets, the plugin needs to be available not only to <em>TQt Designer</em> but also to <tt>uic</tt> at compile-time.</p> <h4><a name="2-1"></a>Creating a Custom Widget</h4> -<!-- index Creating Custom Widgets --><!-- index Widgets!Creating a Custom Widget --><!-- index Subclassing!Widgets --><p>A custom widget is often a specialization (subclass) of another widget or a combination of widgets working together or a blend of both these approaches. If you simply want a collection of widgets in a particular configuration it is easiest to create them, select them as a group, and copy and paste them as retquired within <em>TQt Designer</em>. Custom widgets are generally created when you need to add new functionality to existing widgets or groups of widgets.</p> +<!-- index Creating Custom Widgets --><!-- index Widgets!Creating a Custom Widget --><!-- index Subclassing!Widgets --><p>A custom widget is often a specialization (subclass) of another widget or a combination of widgets working together or a blend of both these approaches. If you simply want a collection of widgets in a particular configuration it is easiest to create them, select them as a group, and copy and paste them as required within <em>TQt Designer</em>. Custom widgets are generally created when you need to add new functionality to existing widgets or groups of widgets.</p> <!-- index Properties!Creating Custom Properties --><p>We have two recommendations that you should consider when creating a custom widget for a plugin:</p> <ol type=1><li><p>Using TQt's property system will provide <em>TQt Designer</em> users with a direct means of configuring the widget through the property editor. (See the <a href="http://doc.trolltech.com/properties.html">TQt Properties</a> documentation.)</p> <li><p>Consider making your widget's public 'set' functions into public slots so that you can perform signal-slot connections with the widget in <em>TQt Designer</em>.</p> @@ -128,7 +128,7 @@ DBFILE = vcr.db </pre> <p>Our widget will be derived from <a href="qwidget.html">TQWidget</a> so we include the <tt>qwidget.h</tt> header file. We also forward declare the two classes that our widget will be built from.</p> <pre></pre> -<!-- index Macros!Q_OBJECT --><!-- index Q_OBJECT --><!-- index Macros!Q_ENUMS --><!-- index Q_ENUMS --> <p>We include the <tt>Q_OBJECT</tt> macro since this is retquired for classes that declare signals or slots. The <tt>Q_ENUMS</tt> declaration is used to register the Mode enumeration. Our widget has two properties, mode, to store whether the user should select a File or a Directory and fileName which stores the file or directory they chose.</p> +<!-- index Macros!Q_OBJECT --><!-- index Q_OBJECT --><!-- index Macros!Q_ENUMS --><!-- index Q_ENUMS --> <p>We include the <tt>Q_OBJECT</tt> macro since this is required for classes that declare signals or slots. The <tt>Q_ENUMS</tt> declaration is used to register the Mode enumeration. Our widget has two properties, mode, to store whether the user should select a File or a Directory and fileName which stores the file or directory they chose.</p> <pre> class QT_WIDGET_PLUGIN_EXPORT FileChooser : public <a href="qwidget.html">TQWidget</a> { Q_OBJECT @@ -222,7 +222,7 @@ DBFILE = vcr.db <p>When <tt>chooseFile()</tt> is called it presents the user with a file or directory dialog depending on the mode. If the user chooses a file or directory the <a href="qlineedit.html">TQLineEdit</a> is updated with the chosen file or directory and the <tt>fileNameChanged()</tt> signal is emitted.</p> <p>Although these two files complete the implementation of the FileChooser widget it is good practice to write a test harness to check that the widget behaves as expected before attempting to put it into a plugin.</p> <h5><a name="2-1-3"></a>Testing the Implementation</h5> -<!-- index main.cpp --><!-- index Forms!Creating Test Harnesses --><p>We present a rudimentary test harness which will allow us to run our custom widget. The test harness retquires two files, a <tt>main.cpp</tt> to contain the FileChooser, and a <tt>.pro</tt> file to create the Makefile from. Here is <tt>qt/tools/designer/examples/filechooser/widget/main.cpp</tt>:</p> +<!-- index main.cpp --><!-- index Forms!Creating Test Harnesses --><p>We present a rudimentary test harness which will allow us to run our custom widget. The test harness requires two files, a <tt>main.cpp</tt> to contain the FileChooser, and a <tt>.pro</tt> file to create the Makefile from. Here is <tt>qt/tools/designer/examples/filechooser/widget/main.cpp</tt>:</p> <pre> #include <<a href="qapplication-h.html">qapplication.h</a>> #include "filechooser.h" @@ -245,13 +245,13 @@ CONFIG += qt warn_on release DBFILE = filechooser.db DEFINES += FILECHOOSER_IS_WIDGET </pre> -<p>We can create the makefile using <tt>qmake</tt>: <tt>qmake -o Makefile filechooser.pro</tt>, then we can make and run the harness to test our new widget. Once we're satisfied that the custom widget is robust and has the behaviour we retquire we can embed it into a plugin.</p> +<p>We can create the makefile using <tt>qmake</tt>: <tt>qmake -o Makefile filechooser.pro</tt>, then we can make and run the harness to test our new widget. Once we're satisfied that the custom widget is robust and has the behaviour we require we can embed it into a plugin.</p> <h4><a name="2-2"></a>Creating a Plugin</h4> <!-- index Creating Plugins --><!-- index Plugins!Creating a Plugin --><!-- index Component!Plugins --><p>TQt Plugins can be used to provide self-contained software components for TQt applications. TQt currently supports the creation of five kinds of plugins: codecs, image formats, database drivers, styles and custom widgets. In this section we will explain how to convert our filechooser custom widget into a <em>TQt Designer</em> custom widget plugin.</p> <p>A <em>TQt Designer</em> custom widget plugin is always derived from <a href="qwidgetplugin.html">TQWidgetPlugin</a>. The amout of code that needs to be written is minimal.</p> -<p>To make your own plugin it is probably easiest to start by copying our example<!-- index plugin.h --> <tt>plugin.h</tt> and<!-- index plugin.cpp --> <tt>plugin.cpp</tt> files and changing 'CustomWidgetPlugin' to the name you wish to use for your widget plugin implementation class. Below we provide an introduction to the header file although it needs no changes beyond class renaming. The implementation file retquires simple changes, mostly more class renaming; we will review each function in turn and explain what you need to do.</p> +<p>To make your own plugin it is probably easiest to start by copying our example<!-- index plugin.h --> <tt>plugin.h</tt> and<!-- index plugin.cpp --> <tt>plugin.cpp</tt> files and changing 'CustomWidgetPlugin' to the name you wish to use for your widget plugin implementation class. Below we provide an introduction to the header file although it needs no changes beyond class renaming. The implementation file requires simple changes, mostly more class renaming; we will review each function in turn and explain what you need to do.</p> <h5><a name="2-2-1"></a>The <b>CustomWidgetPlugin</b> Implementation</h5> -<p>We have called our header file<!-- index plugin.h --> <tt>plugin.h</tt> and we've called our plugin class <b>CustomWidgetPlugin</b> since we will be using our plugin class to wrap our custom widgets. We present the entire header file to give you an impression of the scope of the implementation retquired. Most of the functions retquire just a few lines of code.</p> +<p>We have called our header file<!-- index plugin.h --> <tt>plugin.h</tt> and we've called our plugin class <b>CustomWidgetPlugin</b> since we will be using our plugin class to wrap our custom widgets. We present the entire header file to give you an impression of the scope of the implementation required. Most of the functions require just a few lines of code.</p> <pre> #include <<a href="qwidgetplugin-h.html">qwidgetplugin.h</a>> class CustomWidgetPlugin : public <a href="qwidgetplugin.html">TQWidgetPlugin</a> diff --git a/doc/html/designer-manual-8.html b/doc/html/designer-manual-8.html index 9886c384..5f2cd553 100644 --- a/doc/html/designer-manual-8.html +++ b/doc/html/designer-manual-8.html @@ -113,7 +113,7 @@ bool createConnections() <!-- index TQSqlDatabase::database() --><p>You do not need to keep a reference to database connections. If you use a single database connection, this becomes the default connection and database functions will use this connection automatically. We can always get a pointer to any of our connections by calling <tt>TQSqlDatabase::database()</tt>.</p> <p>If you create a <tt>main.cpp</tt> file using <em>TQt Designer</em>, this file will <em>not</em> include <tt>createConnections()</tt>. We do not include this function because it needs the username and password for the database connection, and you may prefer to handle these differently from our simple example function. As a result, applications that preview correctly in <em>TQt Designer</em> will not run unless you implement your own database connections function.</p> <h3><a name="2"></a>Using <a href="qdatatable.html">TQDataTable</a></h3> -<p><a href="qdatatable.html">TQDataTable</a>s may be placed on any form to provide browsing of database tables and views. <a href="qdatatable.html">TQDataTable</a>s can also be used to update or delete records in-place, i.e. inside the cells themselves. Inserting records via a <a href="qdatatable.html">TQDataTable</a> usually retquires connecting to the<!-- index primeInsert() --> <tt>primeInsert()</tt> signal, so that we can generate primary keys for example, or provide default values. If we wish to present records using a form view (perhaps combining data from several tables and views) we might use several <a href="qdatabrowser.html">TQDataBrowser</a>s and <a href="qdataview.html">TQDataView</a>s.</p> +<p><a href="qdatatable.html">TQDataTable</a>s may be placed on any form to provide browsing of database tables and views. <a href="qdatatable.html">TQDataTable</a>s can also be used to update or delete records in-place, i.e. inside the cells themselves. Inserting records via a <a href="qdatatable.html">TQDataTable</a> usually requires connecting to the<!-- index primeInsert() --> <tt>primeInsert()</tt> signal, so that we can generate primary keys for example, or provide default values. If we wish to present records using a form view (perhaps combining data from several tables and views) we might use several <a href="qdatabrowser.html">TQDataBrowser</a>s and <a href="qdataview.html">TQDataView</a>s.</p> <h4><a name="2-1"></a>Quickly Viewing a Database Table</h4> <p>This example, along with all the other examples in this chapter, has the project name 'book' and uses the database created by the<!-- index book.sql --> <tt>book.sql</tt> script. As we work through the chapter we will build the 'book' application step by step. Create or copy the <tt>qt/tools/designer/examples/book/book1/main.cpp</tt> file shown earlier. The project file for this first example is <tt>qt/tools/designer/examples/book/book1/book.pro</tt>. Start a new project by clicking <b>File|New</b>, then click the 'C++ Project' icon to invoke the <em>Project Settings</em> dialog. Click the ellipsis button to invoke the <em>Save As</em> dialog; navigate to the project's directory (creating it if necessary). Make sure you're in the project's directory, then enter a project name of 'book.pro'. Click the <b>Save</b> button to return to the <em>Project Settings</em> dialog, then click <b>OK</b>. Now click <b>Project|Database Connections</b>. Fill in the connection information appropriate to your database then press <b>Connect</b>. The connection name should now appear in the left hand list box. (If this doesn't happen you'll need to contact your database systems administrator for help.) Close the dialog.</p> <p>We will now create a new form with a <a href="qdatatable.html">TQDataTable</a> that's connected to one of our database tables.</p> @@ -144,7 +144,7 @@ bool createConnections() <!-- index Foreign Keys --><!-- index Databases!Foreign Keys --><p>In most relational databases tables contain fields which are foreign keys into other tables. In our 'book' database example the authorid in the book table is a foreign key into the author table. When we present a form to the end user we do not usually want the foreign key itself to be visible but rather the text associated with it. Thus, we would want the author's name to appear rather than the author id when we show book information. In many databases, this can be achieved by using a view. See your database's documentation for details.</p> </blockquote> <h4><a name="2-2"></a>Inserting Records in <a href="qdatatable.html">TQDataTable</a>s</h4> -<!-- index Inserting Records --><!-- index Databases!Inserting Records --><p>Record insertion into a relational database usually retquires the generation of a primary key value which uniquely identifies the record in the table. Also we often want to create default values for some fields to minimize the user's work. We will create a slot to capture the <a href="qdatatable.html">TQDataTable</a>s<!-- index primeInsert() --> <tt>primeInsert()</tt> signal and populate the <a href="qsqlrecord.html">TQSqlRecord</a> insertion buffer with a unique primary key.</p> +<!-- index Inserting Records --><!-- index Databases!Inserting Records --><p>Record insertion into a relational database usually requires the generation of a primary key value which uniquely identifies the record in the table. Also we often want to create default values for some fields to minimize the user's work. We will create a slot to capture the <a href="qdatatable.html">TQDataTable</a>s<!-- index primeInsert() --> <tt>primeInsert()</tt> signal and populate the <a href="qsqlrecord.html">TQSqlRecord</a> insertion buffer with a unique primary key.</p> <ol type=1><li><p>Click <b>Edit|Slots</b> to invoke the <em>Edit Functions</em> dialog. Click <b>New Function</b>, then enter the slot name <tt>primeInsertAuthor(TQSqlRecord*)</tt> into the Function Properties' Function line edit box. Click <b>OK</b>.</p> <li><p>Click the <b>Connect Signals/Slots</b> toolbar button, then click the AuthorDataTable, drag to the form and release the mouse. The <em>Edit Connections</em> dialog will now appear. Click the<!-- index primeInsert() --> <tt>primeInsert()</tt> signal and then the <tt>primeInsertAuthor()</tt> slot to make the connection. Now click <b>OK</b>.</p> <li><p>Click the Members tab of the Object Explorer window (click <b>Window|Views|Object Explorer</b> to make the window visible if necessary). Click the <tt>primeInsertAuthor()</tt> slot and an editor window will appear.</p> @@ -161,15 +161,15 @@ bool createConnections() </pre> <p>A <a href="qsqlquery.html">TQSqlQuery</a> object is used to increment and retrieve a unique 'sequence' number for the author table. The signal passed us a pointer to the insertion buffer and we then put the value we've retrieved, i.e. the next sequence number, into the buffer's id field. (Again, note that SQL databases often support a native 'sequence' function. The method used here is inappropriate for production systems, and is for example purposes only. See your database's documentation for details on how to generate unique keys in code. In many cases, the database can generate them automatically, or the database may provide a special syntax for dealing with sequences.)</p> </ol><!-- index Deleting!Records!Databases --><!-- index Databases!Deleting Records --><!-- index Updating Records --><!-- index Databases!Updating Records --><p>If we rebuild the application it will now support <tt>INSERT</tt> as well as <tt>UPDATE</tt> and <tt>DELETE</tt>. We could easily have added additional code to insert default values, e.g. today's date into a date field, if necessary.</p> -<!-- index Databases!Browsing --><!-- index Databases!Confirmations --><!-- index Browsing Databases --><p>Browsing is supported by clicking records and by using the arrow keys. Once a record is active (highlighted) we can edit the it. Press the <b>Insert</b> key to <tt>INSERT</tt> a new record; press <b>F2</b> to <tt>UPDATE</tt> the current record; press the <b>Del</b> key to <tt>DELETE</tt> the current record. All these operations take place immediately. Users can be given the opportunity to confirm their edits by setting the <a href="qdatatable.html">TQDataTable</a>'s confirmEdits property to True. If the confirmEdits property is True then user confirmation will be retquired for all insertions, updates and deletes. For finer control you can set the confirmInsert, confirmUpdate and confirmDelete properties individually.</p> +<!-- index Databases!Browsing --><!-- index Databases!Confirmations --><!-- index Browsing Databases --><p>Browsing is supported by clicking records and by using the arrow keys. Once a record is active (highlighted) we can edit the it. Press the <b>Insert</b> key to <tt>INSERT</tt> a new record; press <b>F2</b> to <tt>UPDATE</tt> the current record; press the <b>Del</b> key to <tt>DELETE</tt> the current record. All these operations take place immediately. Users can be given the opportunity to confirm their edits by setting the <a href="qdatatable.html">TQDataTable</a>'s confirmEdits property to True. If the confirmEdits property is True then user confirmation will be required for all insertions, updates and deletes. For finer control you can set the confirmInsert, confirmUpdate and confirmDelete properties individually.</p> <blockquote> <p align="center"><b> <a href="qdatatable.html">TQDataTable</a> User Interface Interaction</b></p> <!-- index Databases!User Interface Interaction --><!-- index User Interface Interaction, Databases --><p>The default user-interface behavior for <a href="qdatatable.html">TQDataTable</a>s is as follows:</p> <ul><li><p>Users can move to records by clicking the scrollbar and clicking records with the mouse. They can also use the keyboard's navigation keys, e.g. <b>Left Arrow</b>, <b>Right Arrow</b>, <b>Up Arrow</b>, <b>Down Arrow</b>, <b>Page Up</b>, <b>Page Down</b>, <b>Home</b> and <b>End</b>.</p> -<li><p><tt>INSERT</tt> is initiated by right-clicking the record and clicking Insert or by pressing the <b>Ins</b> (Insert) key. The user moves between fields using <b>Tab</b> and <b>Shift+Tab</b>. The <tt>INSERT</tt> will take place if the user presses <b>Enter</b> or <b>Tab</b>s off the last field. If autoEdit is TRUE the insert will take place if the user navigates to another record. <tt>INSERT</tt> is cancelled by pressing <b>Esc</b> (Escape). If autoEdit is FALSE navigating to another record also cancels the <tt>INSERT</tt>. Setting confirmInsert to TRUE will retquire the user to confirm each <tt>INSERT</tt>.</p> -<li><p><tt>UPDATE</tt> is initiated by right-clicking the record and clicking Update or by pressing <b>F2</b>. The update will take place if the user presses Enter or Tabs off the last field. If autoEdit is TRUE the update will take place if the user navigates to another record. <tt>UPDATE</tt> is cancelled by pressing <b>Esc</b>. If autoEdit is FALSE navigating to another record also cancels the <tt>UPDATE</tt>. Setting confirmUpdate to TRUE will retquire the user to confirm each <tt>UPDATE</tt>.</p> -<li><p><tt>DELETE</tt> is achieved by right-clicking the record and clicking Delete or by pressing the <b>Del</b> (Delete) key. Setting confirmDelete to TRUE will retquire the user to confirm each <tt>DELETE</tt>.</p> -</ul><p>You can change this default behavior programmatically if retquired.</p> +<li><p><tt>INSERT</tt> is initiated by right-clicking the record and clicking Insert or by pressing the <b>Ins</b> (Insert) key. The user moves between fields using <b>Tab</b> and <b>Shift+Tab</b>. The <tt>INSERT</tt> will take place if the user presses <b>Enter</b> or <b>Tab</b>s off the last field. If autoEdit is TRUE the insert will take place if the user navigates to another record. <tt>INSERT</tt> is cancelled by pressing <b>Esc</b> (Escape). If autoEdit is FALSE navigating to another record also cancels the <tt>INSERT</tt>. Setting confirmInsert to TRUE will require the user to confirm each <tt>INSERT</tt>.</p> +<li><p><tt>UPDATE</tt> is initiated by right-clicking the record and clicking Update or by pressing <b>F2</b>. The update will take place if the user presses Enter or Tabs off the last field. If autoEdit is TRUE the update will take place if the user navigates to another record. <tt>UPDATE</tt> is cancelled by pressing <b>Esc</b>. If autoEdit is FALSE navigating to another record also cancels the <tt>UPDATE</tt>. Setting confirmUpdate to TRUE will require the user to confirm each <tt>UPDATE</tt>.</p> +<li><p><tt>DELETE</tt> is achieved by right-clicking the record and clicking Delete or by pressing the <b>Del</b> (Delete) key. Setting confirmDelete to TRUE will require the user to confirm each <tt>DELETE</tt>.</p> +</ul><p>You can change this default behavior programmatically if required.</p> </blockquote> <h4><a name="2-3"></a>Relating Two Tables Together (Master-Detail)</h4> <!-- index Databases!Master-Detail Relationships --><!-- index Master-Detail Relationships --><p>Databases often have pairs of tables that are related. For example, an invoice table might list the numbers, dates and customers for invoices, but not the actual invoice items, which an invoice item table might store. In the 'book' application we wish to have a <a href="qdatatable.html">TQDataTable</a> that we can use to browse through the authors table and a second <a href="qdatatable.html">TQDataTable</a> to show the books they've written.</p> @@ -210,7 +210,7 @@ bool createConnections() BookDataTable->refresh(); } </pre> - <p>All that's retquired now is to change the BookDataTable's filter and refresh the <a href="qdatatable.html">TQDataTable</a> to show the results of the filter.</p> + <p>All that's required now is to change the BookDataTable's filter and refresh the <a href="qdatatable.html">TQDataTable</a> to show the results of the filter.</p> </ol><h5><a name="2-3-2"></a>Preparing the Interface for Drilldown</h5> <!-- index Databases!Drilldown --><!-- index Drilldown --><p>We can now browse and edit authors and see their books in the BookDataTable. In the next section we explore <a href="qdatabrowser.html">TQDataBrowser</a>, which will allow us to drill down to a dialog through which we can edit books. For now we will add some buttons to the main BookForm which we will use to invoke the book editing dialog.</p> <ol type=1><li><p>Click the form, then click the <b>Break Layout</b> toolbar button. Resize the form to make room for some buttons at the bottom.</p> @@ -250,9 +250,9 @@ bool createConnections() <li><!-- index readFields() --><p><tt>readFields()</tt> to read data from the cursor's edit buffer and<!-- index writeFields() --> <tt>writeFields()</tt> to write the form's data to the cursor's edit buffer;</p> <li><!-- index clearValues() --><p><tt>clearValues()</tt> to clear the form's values.</p> </ul><p>If you use <em>TQt Designer</em>'s <a href="qdatabrowser.html">TQDataBrowser</a> wizard you will be given the option of creating a default set of buttons for navigation and editing. The behavior of these buttons is set up using the slots described above to provide the following functionality:</p> -<ul><li><p><tt>INSERT</tt> is initiated by pressing the <b>Ins</b> (Insert) key. The user moves between fields using <b>Tab</b> and <b>Shift+Tab</b>. If the user presses the Update button the <tt>INSERT</tt> will take place and the user will be taken to the record they have just inserted. If the user presses the Insert button (i.e. a second time) the <tt>INSERT</tt> will take place and a new insertion will be initiated. If autoEdit is TRUE the <tt>INSERT</tt> will take place if the user navigates to another record. <tt>INSERT</tt> is cancelled by pressing the <b>Esc</b> key or by pressing the <b>Del</b> (Delete) key. If autoEdit is FALSE then navigating to another record also cancels the <tt>INSERT</tt>. Setting confirmInsert to TRUE will retquire the user to confirm each <tt>INSERT</tt>.</p> -<li><p><tt>UPDATE</tt> is automatically initiated whenever the user navigates to a record. An update will take place if the user presses the Update button. If autoEdit is TRUE the update will take place if the user navigates to another record. <tt>UPDATE</tt> is cancelled by pressing the <b>Esc</b> key or by pressing the <b>Del</b> button. If autoEdit is FALSE then navigating to another record also cancels the <tt>UPDATE</tt>. Setting confirmUpdate to TRUE will retquire the user to confirm each <tt>UPDATE</tt>.</p> -<li><p><tt>DELETE</tt> is achieved by pressing the <b>Del</b> key. Setting confirmDelete to TRUE will retquire the user to confirm each <tt>DELETE</tt>.</p> +<ul><li><p><tt>INSERT</tt> is initiated by pressing the <b>Ins</b> (Insert) key. The user moves between fields using <b>Tab</b> and <b>Shift+Tab</b>. If the user presses the Update button the <tt>INSERT</tt> will take place and the user will be taken to the record they have just inserted. If the user presses the Insert button (i.e. a second time) the <tt>INSERT</tt> will take place and a new insertion will be initiated. If autoEdit is TRUE the <tt>INSERT</tt> will take place if the user navigates to another record. <tt>INSERT</tt> is cancelled by pressing the <b>Esc</b> key or by pressing the <b>Del</b> (Delete) key. If autoEdit is FALSE then navigating to another record also cancels the <tt>INSERT</tt>. Setting confirmInsert to TRUE will require the user to confirm each <tt>INSERT</tt>.</p> +<li><p><tt>UPDATE</tt> is automatically initiated whenever the user navigates to a record. An update will take place if the user presses the Update button. If autoEdit is TRUE the update will take place if the user navigates to another record. <tt>UPDATE</tt> is cancelled by pressing the <b>Esc</b> key or by pressing the <b>Del</b> button. If autoEdit is FALSE then navigating to another record also cancels the <tt>UPDATE</tt>. Setting confirmUpdate to TRUE will require the user to confirm each <tt>UPDATE</tt>.</p> +<li><p><tt>DELETE</tt> is achieved by pressing the <b>Del</b> key. Setting confirmDelete to TRUE will require the user to confirm each <tt>DELETE</tt>.</p> </ul></blockquote> <h5><a name="3-1-2"></a>Performing the Drilldown</h5> <!-- index Databases!Drilldown --><!-- index Drilldown --><p>We now have a working form for editing book records. We need to start the form when the user clicks our 'Edit Books' button, and to navigate to the record they have selected in the BookDataTable. We also need to provide a means of editing the foreign keys, e.g. authorid.</p> @@ -344,7 +344,7 @@ bool createConnections() } </pre> <p>Firstly we look up the book's author and secondly we iterate through the <em>ComboBox</em>'s items until we find the author and set the <em>ComboBox</em>'s current item to the matching author.</p> -</ul></ol><p>If the author name has changed or been deleted the query will fail and no author id will be inserted into the buffer causing the <tt>INSERT</tt> to fail. An alternative is to record the author id's as we populate the <em>ComboBox</em> and store them in a <a href="qmap.html">TQMap</a> which we can then look up as retquired. This approach retquires changes to the<!-- index init() --> <tt>init()</tt>, <tt>beforeUpdateBook()</tt> and <tt>primeInsertBook()</tt> functions and the addition of a new function, <tt>mapAuthor()</tt>. The relevant code from <tt>qt/tools/designer/examples/book/book8/editbook.ui</tt> is shown below.</p> +</ul></ol><p>If the author name has changed or been deleted the query will fail and no author id will be inserted into the buffer causing the <tt>INSERT</tt> to fail. An alternative is to record the author id's as we populate the <em>ComboBox</em> and store them in a <a href="qmap.html">TQMap</a> which we can then look up as required. This approach requires changes to the<!-- index init() --> <tt>init()</tt>, <tt>beforeUpdateBook()</tt> and <tt>primeInsertBook()</tt> functions and the addition of a new function, <tt>mapAuthor()</tt>. The relevant code from <tt>qt/tools/designer/examples/book/book8/editbook.ui</tt> is shown below.</p> <ol type=1><li><p>First we need to create a class variable to map author names to author id's. Click in the Members tab of the Object Explorer, then right click the Class Variables item and click <b>New</b>. Type in 'TQMap<TQString,int> authorMap;'.</p> <li><p>We now record the author id's in the<!-- index init() --> <tt>init()</tt> function.</p> <pre> void EditBookForm::init() @@ -389,7 +389,7 @@ bool createConnections() } } </pre> -</ol><!-- index Databases!Foreign Keys --><!-- index Foreign Keys --> <p>Another approach which is especially useful if the same foreign key lookups are retquired in different parts of the application is to subclass a cursor and use this for our lookups. This is described in the <a href="http://doc.trolltech.com/sql.html">TQt SQL Module documentation</a>, particulary the section on subclassing <a href="qsqlcursor.html">TQSqlCursor</a>.</p> +</ol><!-- index Databases!Foreign Keys --><!-- index Foreign Keys --> <p>Another approach which is especially useful if the same foreign key lookups are required in different parts of the application is to subclass a cursor and use this for our lookups. This is described in the <a href="http://doc.trolltech.com/sql.html">TQt SQL Module documentation</a>, particulary the section on subclassing <a href="qsqlcursor.html">TQSqlCursor</a>.</p> <p>The 'book' example demonstrates the basic techniques needed for SQL programming with TQt. Additional information on the TQt SQL classes, especially the <a href="qsqlquery.html">TQSqlQuery</a> and <a href="qsqlcursor.html">TQSqlCursor</a> classes is provided in the <a href="http://doc.trolltech.com/sql.html">TQt SQL Module documentation</a>.</p> <!-- eof --> <p align="right">[<a href="designer-manual-7.html">Prev: Creating Custom Widgets</a>] [<a href="designer-manual.html">Home</a>] [<a href="designer-manual-9.html">Next: Customizing and Integrating TQt Designer</a>]</p> diff --git a/doc/html/designer-manual-9.html b/doc/html/designer-manual-9.html index 3900eb31..ac66684e 100644 --- a/doc/html/designer-manual-9.html +++ b/doc/html/designer-manual-9.html @@ -82,7 +82,7 @@ body { background: #ffffff; color: black; } <h3><a name="2"></a>Creating and Using Templates</h3> <!-- index Creating Templates --><!-- index Templates!Creating and Using --><p><em>TQt Designer</em> supports two approaches to creating template forms. The simplest approach involves little more than saving a<!-- index .ui --> <tt>.ui</tt> file into the templates directory. The second approach involves creating a container widget class to be used as a base class for forms that use the template. We will explain both techniques.</p> <h4><a name="2-1"></a>Simple Templates</h4> -<p>These templates are most useful when you want to create a whole set of forms which all have some common widgets. For example, you might have a project that will retquire many forms, all of which need to be branded with a company name and logo.</p> +<p>These templates are most useful when you want to create a whole set of forms which all have some common widgets. For example, you might have a project that will require many forms, all of which need to be branded with a company name and logo.</p> <p>First we'll create the simple template.</p> <ol type=1><li><p>Click <b>File|New</b> to invoke the <em>New File</em> dialog. Click the Dialog template then click <b>OK</b>.</p> <li><p>Click the <b>Text Label</b> toolbar button, then click near the top left of the form. Change the font Point Size property to 16 and change the <em>text</em> property to your or your company's name. Click the <b>Line</b> toolbar button, then click the form below the label; click Horizontal on the pop-up menu.</p> @@ -111,7 +111,7 @@ body { background: #ffffff; color: black; } <p>If you wish to delete the add-in remove it from the toolbar then delete the<!-- index qmsdev.dll --> <tt>qmsdev.dll</tt> file from the add-ins directory.</p> <h4><a name="3-1"></a>Creating Makefiles without qmake</h4> <!-- index Makefiles --><p>The <tt>qmake</tt> tool provided with TQt can create Makefiles appropriate to your platform based on<!-- index .pro --> <tt>.pro</tt> project files. This section describes the dependencies involved in building a TQt application and gives a couple of simple example Makefiles. This section assumes that you have a good understanding of Makefiles.</p> -<!-- index Macros!Q_OBJECT --><!-- index Q_OBJECT --><p><em>TQt Designer</em> produces<!-- index .ui --> <tt>.ui</tt> files which are used to generate<!-- index .h --> <tt>.h</tt> and<!-- index .cpp --> <tt>.cpp</tt> files for the compiler to compile. The<!-- index .ui --> <tt>.ui</tt> files are processed by <tt>uic</tt>. Classes which inherit from <a href="qobject.html">TQObject</a>, e.g. those which use slots and signals, retquire an additional<!-- index .cpp --> <tt>.cpp</tt> file to be generated. These files are generated by the <tt>moc</tt> and are named '<em>moc_</em>file.cpp' where the original<!-- index .cpp --> <tt>.cpp</tt> file is called 'file.cpp'. If your<!-- index .cpp --> <tt>.cpp</tt> file contains the <tt>Q_OBJECT</tt> macro an additional file 'file.moc' should be generated which must be <tt>#include</tt>d in the<!-- index .cpp --> <tt>.cpp</tt>, normally at the end. This retquires an extra dependency being created.</p> +<!-- index Macros!Q_OBJECT --><!-- index Q_OBJECT --><p><em>TQt Designer</em> produces<!-- index .ui --> <tt>.ui</tt> files which are used to generate<!-- index .h --> <tt>.h</tt> and<!-- index .cpp --> <tt>.cpp</tt> files for the compiler to compile. The<!-- index .ui --> <tt>.ui</tt> files are processed by <tt>uic</tt>. Classes which inherit from <a href="qobject.html">TQObject</a>, e.g. those which use slots and signals, require an additional<!-- index .cpp --> <tt>.cpp</tt> file to be generated. These files are generated by the <tt>moc</tt> and are named '<em>moc_</em>file.cpp' where the original<!-- index .cpp --> <tt>.cpp</tt> file is called 'file.cpp'. If your<!-- index .cpp --> <tt>.cpp</tt> file contains the <tt>Q_OBJECT</tt> macro an additional file 'file.moc' should be generated which must be <tt>#include</tt>d in the<!-- index .cpp --> <tt>.cpp</tt>, normally at the end. This requires an extra dependency being created.</p> <p>Processing<!-- index .ui --> <tt>.ui</tt> files with <tt>uic</tt> is done <em>twice</em>:</p> <pre> uic myform.ui -o myform.h @@ -172,7 +172,7 @@ myform.h: myform.ui </pre> <p>To see more sophisticated Makefiles simply generate them using <tt>qmake</tt> on any of your TQt projects or any of the examples supplied with TQt.</p> <h3><a name="4"></a>Importing Foreign File Formats</h3> -<!-- index Foreign File Formats --><p>To import a file in a supported foreign file format click <b>File|Open</b>, then click the File Type combobox to choose the file type you wish to load. Click the retquired file and <em>TQt Designer</em> will convert and load the file.</p> +<!-- index Foreign File Formats --><p>To import a file in a supported foreign file format click <b>File|Open</b>, then click the File Type combobox to choose the file type you wish to load. Click the required file and <em>TQt Designer</em> will convert and load the file.</p> <p>The filters that <em>TQt Designer</em> uses to read foreign file formats are 'works in progress'. You may have different filters available in your version of <em>TQt Designer</em> than those described here. The easiest way to see which filters are available is to invoke the file open dialog; all your filters are listed in the File Type combobox.</p> <h4><a name="4-1"></a>Importing TQt Architect Files</h4> <!-- index Foreign File Formats!TQt Architect --><!-- index TQt Architect --><p><a href="http://qtarch.sourceforge.net/">TQt Architect</a> is a free GUI builder for TQt written by Jeff Harris and Klaus Ebner. The<!-- index .dlg --> <tt>.dlg</tt> extension is associated with TQt Architect dialog files.</p> diff --git a/doc/html/distributingqt.html b/doc/html/distributingqt.html index a002535d..5e040bd7 100644 --- a/doc/html/distributingqt.html +++ b/doc/html/distributingqt.html @@ -35,7 +35,7 @@ body { background: #ffffff; color: black; } <p> This document lists the platform-specific files needed to distribute TQt applications. We do not include any compiler-specific files that -may also be retquired. (See also, <a href="winsystem.html">Window +may also be required. (See also, <a href="winsystem.html">Window System-specific Notes</a>.) <p> <!-- toc --> <ul> @@ -81,7 +81,7 @@ path. version is prefixed with <em>-mt</em>. <p> <h3> Distributing Plugins </h3> -<a name="2-1"></a><p> You must include any plugin files retquired by the application. +<a name="2-1"></a><p> You must include any plugin files required by the application. <p> Plugins must be put into a subdirectory under a directory known to TQt as a plugin directory. The subdirectory must have the name of the plugin category (e.g. <tt>styles</tt>, <tt>sqldrivers</tt>, <tt>designer</tt>, etc.). diff --git a/doc/html/emb-classes.html b/doc/html/emb-classes.html index 0b9001bf..57ef5180 100644 --- a/doc/html/emb-classes.html +++ b/doc/html/emb-classes.html @@ -163,7 +163,7 @@ typically 2-20KB in size; they can be mmap'd direct from disk in order to save memory). If a TQPF font is found which matches a font request no new TQRenderedFont need be created for it. It's possible to strip out all TQFontFactory support and simply use TQPFs if your font needs are modest -(for instance, if you only retquire a few fixed point sizes). Note that +(for instance, if you only require a few fixed point sizes). Note that no best-match loading is performed with TQPFs, as opposed to those loaded via <a href="qfontmanager.html">TQFontManager</a>, so if you don't have the correct TQPF for a point size, text in that size will simply not be displayed. diff --git a/doc/html/emb-performance.html b/doc/html/emb-performance.html index 51904cf1..3311941c 100644 --- a/doc/html/emb-performance.html +++ b/doc/html/emb-performance.html @@ -35,7 +35,7 @@ body { background: #ffffff; color: black; } When building embedded applications on low-powered devices, a number of options are available that would not be considered in a desktop application environment. These options reduce the memory and/or CPU -retquirements at the cost of other factors. +requirements at the cost of other factors. <p> <ul> <li> <a href="emb-features.html"><b>Tuning the functionality of TQt</a> <li> <a href="#general">General programming style</a> diff --git a/doc/html/emb-porting.html b/doc/html/emb-porting.html index 0e1081b4..a48584ee 100644 --- a/doc/html/emb-porting.html +++ b/doc/html/emb-porting.html @@ -32,7 +32,7 @@ body { background: #ffffff; color: black; } <td align="right" valign="center"><img src="logo32.png" align="right" width="64" height="32" border="0"></td></tr></table><h1 align=center>Porting your applications to TQt/Embedded</h1> -<p> Existing TQt applications should retquire no porting provided there is no +<p> Existing TQt applications should require no porting provided there is no platform dependent code. Platform dependent code includes system calls, calls to the underlying window system (Windows or X11), and TQt platform specific methods such as <a href="qapplication.html#x11EventFilter">TQApplication::x11EventFilter</a>(). @@ -45,7 +45,7 @@ using <tt>#ifdef</tt> directives: <tr bgcolor="#d0d0d0"> <td valign="top">TQt/Windows <td valign="top">Q_WS_WIN <tr bgcolor="#f0f0f0"> <td valign="top">TQt/Embedded <td valign="top">Q_WS_QWS </table></center> -<p> TQt/Embedded also retquires the following flags to be defined when compiling +<p> TQt/Embedded also requires the following flags to be defined when compiling applications: <pre> -DTQWS -fno-exceptions -fno-rtti diff --git a/doc/html/emb-running.html b/doc/html/emb-running.html index 44a20c04..e1d887ea 100644 --- a/doc/html/emb-running.html +++ b/doc/html/emb-running.html @@ -32,7 +32,7 @@ body { background: #ffffff; color: black; } <td align="right" valign="center"><img src="logo32.png" align="right" width="64" height="32" border="0"></td></tr></table><h1 align=center>Running TQt/Embedded applications</h1> -<p> A TQt/Embedded application retquires a master application to be running +<p> A TQt/Embedded application requires a master application to be running or to be a master application itself. The master application is primarily responsible for managing top-level window regions, and pointer and keyboard input. diff --git a/doc/html/faq.html b/doc/html/faq.html index d49d3985..f05c2263 100644 --- a/doc/html/faq.html +++ b/doc/html/faq.html @@ -330,7 +330,7 @@ project. Can we transfer the license to another developer? </h3> <a name="4-1"></a><p> Yes. TQt licences are for the individual use of named developers. If the developer associated with a licence leaves the organization, or -moves on to another project that does not retquire a TQt license, +moves on to another project that does not require a TQt license, another developer can take over the licence. You can change the name of the developer using a licence at any time, but after a change you must wait at least six (6) months before changing again. @@ -420,7 +420,7 @@ software pool to do so without paying license fees. <p> Although it is possible to write free software for internal use, it is difficult to ensure that such software is used and distributed legally. For example, if your free software -retquires any modules that impose conditions on you that +requires any modules that impose conditions on you that contradict the conditions of the GNU GPL, including, but not limited to, software patents, commercial license agreements, copyrighted interface definitions or any sort of diff --git a/doc/html/gpl.html b/doc/html/gpl.html index fd4e7874..752e94e1 100644 --- a/doc/html/gpl.html +++ b/doc/html/gpl.html @@ -151,9 +151,9 @@ above, provided that you also meet all of these conditions: these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on - the Program is not retquired to print an announcement.) + the Program is not required to print an announcement.) -These retquirements apply to the modified work as a whole. If +These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those @@ -219,7 +219,7 @@ However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. - 5. You are not retquired to accept this License, since you have not + 5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by diff --git a/doc/html/helpsystem-example.html b/doc/html/helpsystem-example.html index 2c24cfc6..3713cea6 100644 --- a/doc/html/helpsystem-example.html +++ b/doc/html/helpsystem-example.html @@ -476,7 +476,7 @@ and use the make tool to build the library. <hr> <ol> <li><a name="footnote1"></a> -Note that <a href="moc.html#moc">moc</a> retquires that <a href="qobject.html">TQObject</a> +Note that <a href="moc.html#moc">moc</a> requires that <a href="qobject.html">TQObject</a> is the first base class. <a href="#footnote-call1">Back...</a> <li><a name="footnote2"></a> Note that we have to explicitly scope the orientation diff --git a/doc/html/i18n.html b/doc/html/i18n.html index 6f81c334..c2203cf8 100644 --- a/doc/html/i18n.html +++ b/doc/html/i18n.html @@ -73,10 +73,10 @@ the application usable by people in countries other than one's own. <!-- endtoc --> <p> In some cases internationalization is simple, for example, making a US -application accessible to Australian or British users may retquire +application accessible to Australian or British users may require little more than a few spelling corrections. But to make a US application usable by Japanese users, or a Korean application usable -by German users, will retquire that the software operate not only in +by German users, will require that the software operate not only in different languages, but use different input techniques, character encodings and presentation conventions. <p> TQt tries to make internationalization as painless as possible for @@ -94,7 +94,7 @@ time. <li> Greek <li> Hebrew <li> Thai and Lao -<li> All scripts in Unicode 3.2 that do not retquire special processing +<li> All scripts in Unicode 3.2 that do not require special processing </ul> <p> On Windows NT/2000/XP and Unix/X11 with Xft (client side font support) the following languages are also supported: @@ -149,7 +149,7 @@ takes a <a href="qrect.html">TQRect</a> since this will align in accordance with <p> <li> When you write your own text input controls, use <a href="qfontmetrics.html#charWidth">TQFontMetrics::charWidth</a>() to determine the width of a character in a string. In some languages (e.g. Arabic or languages from the Indian subcontinent), the width and shape of a glyph changes depending on the -surrounding characters. Writing input controls usually retquires a +surrounding characters. Writing input controls usually requires a certain knowledge of the scripts it is going to be used in. Usually the easiest way is to subclass <a href="qlineedit.html">TQLineEdit</a> or <a href="qtextedit.html">TQTextEdit</a>. <p> </ul> @@ -394,7 +394,7 @@ support many input and output encodings for your users' data. When an application starts, the locale of the machine will determine the 8-bit encoding used when dealing with 8-bit data: such as for font selection, text display, 8-bit text I/O and character input. -<p> The application may occasionally retquire encodings other than the +<p> The application may occasionally require encodings other than the default local 8-bit encoding. For example, an application in a Cyrillic KOI8-R locale (the de-facto standard locale in Russia) might need to output Cyrillic in the ISO 8859-5 encoding. Code for this diff --git a/doc/html/keyfeatures30.html b/doc/html/keyfeatures30.html index 84118941..0a549956 100644 --- a/doc/html/keyfeatures30.html +++ b/doc/html/keyfeatures30.html @@ -151,7 +151,7 @@ existing code which uses these classes will continue to work. <p> <h3> Regular Expressions </h3> <a name="1-6"></a><p> TQt has always provided <a href="qregexp.html#regular-expression">regular expression</a> support, but that support -was pretty much limited to what was retquired in common GUI control +was pretty much limited to what was required in common GUI control elements such as file dialogs. TQt 3.0 introduces a new regular expression engine, <a href="qregexp.html">TQRegExp</a>, that supports most of Perl's regex features and is Unicode based. The most useful additions are support diff --git a/doc/html/layout.html b/doc/html/layout.html index 12de2a5c..749cd3c4 100644 --- a/doc/html/layout.html +++ b/doc/html/layout.html @@ -103,11 +103,11 @@ only get more space if no other widgets want the space. Of these, space is allocated to widgets with an <tt>Expanding</tt> size policy first. <li> Any widgets that are allocated less space than their minimum size (or minimum size hint if no minimum size is specified) are allocated -this minimum size they retquire. (Widgets don't have to have a minimum +this minimum size they require. (Widgets don't have to have a minimum size or minimum size hint in which case the strech factor is their determining factor.) <li> Any widgets that are allocated more space than their maximum size -are allocated the maximum size space they retquire. (Widgets don't have +are allocated the maximum size space they require. (Widgets don't have to have a maximum size in which case the strech factor is their determining factor.) </ol> @@ -201,7 +201,7 @@ layout, you should reimplement the following <a href="qwidget.html">TQWidget</a> <li> <a href="qwidget.html#sizeHint">TQWidget::sizeHint</a>() returns the preferred size of the widget. <li> <a href="qwidget.html#minimumSizeHint">TQWidget::minimumSizeHint</a>() returns the smallest size the widget can have. <li> <a href="qwidget.html#sizePolicy">TQWidget::sizePolicy</a>() returns a <a href="qsizepolicy.html">TQSizePolicy</a>; a value describing -the space retquirements of the widget. +the space requirements of the widget. </ul> <p> Call <a href="qwidget.html#updateGeometry">TQWidget::updateGeometry</a>() whenever the size hint, minimum size hint or size policy changes. This will cause a layout recalculation. @@ -215,12 +215,12 @@ of the widget, and it is used by <a href="qlayout.html">TQLayout</a> subclasses support heightForWidth() (both <a href="qgridlayout.html">TQGridLayout</a> and <a href="qboxlayout.html">TQBoxLayout</a> support it). <p> For further guidance when implementing these functions, see their implementations in existing TQt classes that have similar layout -retquirements to your new widget. +requirements to your new widget. <p> <h2> Manual Layout </h2> <a name="6"></a><p> If you are making a one-of-a-kind special layout, you can also make a custom widget as described above. Reimplement <a href="qwidget.html#resizeEvent">TQWidget::resizeEvent</a>() -to calculate the retquired distribution of sizes and call <a href="qwidget.html#setGeometry">setGeometry</a>() on each child. +to calculate the required distribution of sizes and call <a href="qwidget.html#setGeometry">setGeometry</a>() on each child. <p> The widget will get an event with <a href="qevent.html#type">type</a> <tt>LayoutHint</tt> when the layout needs to be recalculated. Reimplement <a href="qwidget.html#event">TQWidget::event</a>() to be notified of <tt>LayoutHint</tt> events. diff --git a/doc/html/license.html b/doc/html/license.html index 74950aba..9b1bc08c 100644 --- a/doc/html/license.html +++ b/doc/html/license.html @@ -107,7 +107,7 @@ or by others. <p> 6. You may develop application programs, reusable components and other software items that link with the original or modified versions of the Software. These items, when distributed, are subject to the following -retquirements: +requirements: <p> <blockquote> a. You must ensure that all recipients of machine-executable forms of these items are also able to receive and use the complete diff --git a/doc/html/licenses.html b/doc/html/licenses.html index c5b008fb..6813b516 100644 --- a/doc/html/licenses.html +++ b/doc/html/licenses.html @@ -302,13 +302,13 @@ above. </ul> <hr> <p> TQt supports GIF reading if it is configured that way during -installation (see qgif.h). If it is, we are retquired to state that +installation (see qgif.h). If it is, 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." <p> <b>Warning:</b> 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 retquire you to +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. <p> GIF support may be removed completely in a future version of TQt. diff --git a/doc/html/linguist-manual-1.html b/doc/html/linguist-manual-1.html index 6980fb07..f2c8bf79 100644 --- a/doc/html/linguist-manual-1.html +++ b/doc/html/linguist-manual-1.html @@ -33,11 +33,11 @@ body { background: #ffffff; color: black; } <h2 align="center">Introduction</h2> <p>TQt provides excellent support for translating applications into local languages. This Guide explains how to use TQt's translation tools for each of the roles involved in translating an application. The Guide begins with a brief overview of the issues that must be considered, followed by chapters devoted to each role and the supporting tools provided.</p> <p><a href="linguist-manual-2.html">Chapter 2: Release Manager</a> is aimed at the person with overall responsibility for the release of the application. They will typically coordinate the work of the software engineers and the translator. The chapter describes the use of two tools. The <a href="linguist-manual-2.html#2">lupdate</a> tool is used to synchronize source code and translations. The <a href="linguist-manual-2.html#3">lrelease</a> tool is used to create runtime translation files for use by the released application.</p> -<p><a href="linguist-manual-3.html">Chapter 3: Translators</a> is for translators. It describes the use of the <em>TQt Linguist</em> tool. No computer knowledge beyond the ability to start a program and use a text editor or word processor is retquired.</p> +<p><a href="linguist-manual-3.html">Chapter 3: Translators</a> is for translators. It describes the use of the <em>TQt Linguist</em> tool. No computer knowledge beyond the ability to start a program and use a text editor or word processor is required.</p> <p><a href="linguist-manual-4.html">Chapter 4: Programmers</a> is for TQt programmers. It explains how to create TQt applications that are able to use translated text. It also provides guidance on how to help the translator identify the context in which phrases appear. This chapter's three short tutorials cover everything the programmer needs to do.</p> <h3><a name="1"></a>Overview of the Translation Process</h3> <p>Most of the text that must be translated in an application program consists of either single words or short phrases. These typically appear as window titles, menu items, pop-up help text (balloon help), and labels to buttons, check boxes and radio buttons.</p> -<p>The phrases are entered into the source code by the programmer in their native language using a simple but special syntax to identify that the phrases retquire translation. The TQt tools provide context information for each of the phrases to help the translator, and the programmer is able to add additional context information to phrases when necessary. The release manager generates a set of translation files that are produced from the source files and passes these to the translator. The translator opens the translation files using <em>TQt Linguist</em>, enters their translations and saves the results back into the translation files, which they pass back to the release manager. The release manager then generates fast compact versions of these translation files ready for use by the application. The tools are designed to be used in repeated cycles as applications change and evolve, preserving existing translations and making it easy to identify which new translations are retquired. <em>TQt Linguist</em> also provides a phrase book facility to help ensure consistent translations across multiple applications and projects.</p> +<p>The phrases are entered into the source code by the programmer in their native language using a simple but special syntax to identify that the phrases require translation. The TQt tools provide context information for each of the phrases to help the translator, and the programmer is able to add additional context information to phrases when necessary. The release manager generates a set of translation files that are produced from the source files and passes these to the translator. The translator opens the translation files using <em>TQt Linguist</em>, enters their translations and saves the results back into the translation files, which they pass back to the release manager. The release manager then generates fast compact versions of these translation files ready for use by the application. The tools are designed to be used in repeated cycles as applications change and evolve, preserving existing translations and making it easy to identify which new translations are required. <em>TQt Linguist</em> also provides a phrase book facility to help ensure consistent translations across multiple applications and projects.</p> <p>Translators and programmers must address a number of issues because of the subtleties and complexities of human language:</p> <ul><li><p>A single phrase may need to be translated into several different forms depending on context, e.g. <em>open</em> in English might become <em></em><em>öffnen</em>, "open file", or <em>aufbauen</em>, "open internet connection", in German.</p> <li><p>Keyboard accelerators may need to be changed but without introducing conflicts, e.g. "&Quit" in English becomes "Avslutt" in Norwegian which doesn't contain a "Q". We cannot use a letter that is already in use -- unless we change several accelerators.</p> diff --git a/doc/html/linguist-manual-2.html b/doc/html/linguist-manual-2.html index a08b3b17..5ee79c54 100644 --- a/doc/html/linguist-manual-2.html +++ b/doc/html/linguist-manual-2.html @@ -61,12 +61,12 @@ body { background: #ffffff; color: black; } <!-- index lupdate --><p>Usage: <tt>lupdate myproject.pro</tt></p> <!-- index TQt Designer --><p>This is a simple command line tool. <a href="linguist-manual-2.html#2">lupdate</a> reads a TQt <tt>.pro</tt> project file, finds the translatable strings in the specified source, header and <em>TQt Designer</em> interface files, and produces or updates the <tt>.ts</tt> translation files listed in the project file. The translation files are given to the translator who uses <em>TQt Linguist</em> to read the files and insert the translations.</p> <p>Companies that have their own translators in-house may find it useful to run <a href="linguist-manual-2.html#2">lupdate</a> regularly, perhaps monthly, as the application develops. This will lead to a fairly low volume of translation work spread evenly over the life of the project and will allow the translators to support a number of projects simultaneously.</p> -<p>Companies that hire in translators as retquired may prefer to run <a href="linguist-manual-2.html#2">lupdate</a> only a few times in the application's life cycle, the first time might be just before the first test phase. This will provide the translator with a substantial single block of work and any bugs that the translator detects may easily be included with those found during the initial test phase. The second and any subsequent <a href="linguist-manual-2.html#2">lupdate</a> runs would probably take place during the final beta phase.</p> -<!-- index .ts Files --><!-- index Translation Source Files --><!-- index XML --><p>The <tt>.ts</tt> file format is a simple human-readable XML format that can be used with version control systems if retquired.</p> +<p>Companies that hire in translators as required may prefer to run <a href="linguist-manual-2.html#2">lupdate</a> only a few times in the application's life cycle, the first time might be just before the first test phase. This will provide the translator with a substantial single block of work and any bugs that the translator detects may easily be included with those found during the initial test phase. The second and any subsequent <a href="linguist-manual-2.html#2">lupdate</a> runs would probably take place during the final beta phase.</p> +<!-- index .ts Files --><!-- index Translation Source Files --><!-- index XML --><p>The <tt>.ts</tt> file format is a simple human-readable XML format that can be used with version control systems if required.</p> <h3><a name="3"></a>lrelease</h3> <!-- index lrelease --><p>Usage: <tt>lrelease myproject.pro</tt></p> <!-- index .qm Files --><!-- index TQt Message Files --><p>This is another simple command line tool. It reads a TQt <tt>.pro</tt> project file and produces the <tt>.qm</tt> files used by the application, one for each <tt>.ts</tt> translation source file listed in the project file. The <tt>.qm</tt> file format is a compact binary format that provides extremely fast lookups for translations.</p> -<p>This tool is run whenever a release of the application is to be made, from initial test version through to final release version. If the <tt>.qm</tt> files are not created, e.g. because an alpha release is retquired before any translation has been undertaken, the application will run perfectly well using the text the programmers placed in the source files. Once the <tt>.qm</tt> files are available the application will detect them and use them automatically.</p> +<p>This tool is run whenever a release of the application is to be made, from initial test version through to final release version. If the <tt>.qm</tt> files are not created, e.g. because an alpha release is required before any translation has been undertaken, the application will run perfectly well using the text the programmers placed in the source files. Once the <tt>.qm</tt> files are available the application will detect them and use them automatically.</p> <p>Note that <a href="linguist-manual-2.html#3">lrelease</a> will only incorporate translations that are marked as "done". If a translation is missing, or has failed validation, the original text will be used instead.</p> <h3><a name="4"></a>Missing Translations</h3> <p>Both <a href="linguist-manual-2.html#2">lupdate</a> and <a href="linguist-manual-2.html#3">lrelease</a> may be used with <tt>.ts</tt> translation source files which are incomplete. Missing translations will be replaced with the native language phrases at runtime.</p> diff --git a/doc/html/linguist-manual-3.html b/doc/html/linguist-manual-3.html index 1a9d36a5..73cee991 100644 --- a/doc/html/linguist-manual-3.html +++ b/doc/html/linguist-manual-3.html @@ -38,7 +38,7 @@ body { background: #ffffff; color: black; } <!-- index Linguist --><!-- index TQt Linguist --><!-- index Contexts!for Translation --><p><em>TQt Linguist</em> is a tool for adding translations to TQt applications. It introduces the concept of a translation "context" which means a group of phrases that appear together on the screen e.g. in the same menu or dialog.</p> <p>To start, run <em>TQt Linguist</em>, either from the taskbar menu, or by double clicking the desktop icon, or type <tt>linguist</tt> (followed by <b>Enter</b>) at the command line. Once <em>TQt Linguist</em> has started choose <b>File|Open</b> from the menu bar and select a <tt>.ts</tt> translation source file to work on.</p> <p><em>TQt Linguist</em>'s main window is divided into four main areas. The left hand side contains the Context list, the top right is the Source text area, the middle right is the translation area and the bottom right is the phrases and guesses area. We'll describe them in detail later.</p> -<p>Click on one of the contexts in the context list (left hand side) and then click on one of the phrases that appears in the Source text area (top right). The phrase will be copied into the translation area (middle right). Click under the word 'Translation' and type in the translation. Click <b>Ctrl+Enter</b> (Done & Next) to confirm that you have completed the translation and to move on to the next phrase that retquires translation.</p> +<p>Click on one of the contexts in the context list (left hand side) and then click on one of the phrases that appears in the Source text area (top right). The phrase will be copied into the translation area (middle right). Click under the word 'Translation' and type in the translation. Click <b>Ctrl+Enter</b> (Done & Next) to confirm that you have completed the translation and to move on to the next phrase that requires translation.</p> <p>The cycle of entering a translation then pressing <b>Ctrl+Enter</b> can be repeated until all the translations are done or until you finish the session. Linguist will attempt to fill the "phrases and guesses" area with possible translations from any open phrase books and any previous translations. Each has a keyboard shortcut, e.g. <b>Ctrl+1</b>, <b>Ctrl+2</b>, etc., which you can use to copy the guess into the Translation area. (Mouse users can double click a phrase or guess to move it into the Translation area.) At the end of the session choose <b>File|Save</b> from the menu bar and then <b>File|Exit</b> to quit.</p> <h3><a name="2"></a>TQt Linguist's Main Window</h3> <h4><a name="2-1"></a>Context List</h4> @@ -80,7 +80,7 @@ body { background: #ffffff; color: black; } <p>To add a new phrase click the <b>New Phrase</b> button (or press Alt+N) and type in a new source phrase. Press Tab and type in the translation. Optionally press Tab and enter a definition -- this is useful to distinguish different translations of the same source phrase. This process may be repeated as often as necessary.</p> <p>You can delete a phrase by selecting it in the phrases list and clicking Remove Phrase.</p> <p>Click the <em>Save</em> button (press Alt+S) and then click the <em>Close</em> button (press Esc) once you've finished adding (and removing) phrases.</p> -<p>When a phrase or set of phrases appears in the phrase book double clicking the retquired target phrase will copy it to the translation pane at the text cursor position. If you want to <em>replace</em> the text in the translation pane with the target phrase, click the translation pane, choose <b>Edit|Select All</b> (press <b>Alt+A</b>) and then double click the target phrase.</p> +<p>When a phrase or set of phrases appears in the phrase book double clicking the required target phrase will copy it to the translation pane at the text cursor position. If you want to <em>replace</em> the text in the translation pane with the target phrase, click the translation pane, choose <b>Edit|Select All</b> (press <b>Alt+A</b>) and then double click the target phrase.</p> <h3><a name="5"></a>Validation</h3> <!-- index Validation of Translations --><!-- index Accelerators!Validation --><!-- index Punctuation!Validation --><!-- index Phrases!Validation --><p><em>TQt Linguist</em> provides three kinds of validation on translated phrases.</p> <ol type=1><li><p><em>Accelerator validation</em> detects translated phrases that do not have an ampersand when the source phrase does and vice versa.</p> diff --git a/doc/html/linguist-manual-4.html b/doc/html/linguist-manual-4.html index b31088a1..bffd3062 100644 --- a/doc/html/linguist-manual-4.html +++ b/doc/html/linguist-manual-4.html @@ -32,11 +32,11 @@ body { background: #ffffff; color: black; } <td align="right" valign="center"><img src="logo32.png" align="right" width="64" height="32" border="0"></td></tr></table><p align="right">[<a href="linguist-manual-3.html">Prev: Translators</a>] [<a href="linguist-manual.html">Home</a>]</p> <h2 align="center">Programmers</h2> <p>Support for multiple languages is extremely simple in TQt applications, and adds little overhead to the programmer's workload.</p> -<p>TQt minimizes the performance cost of using translations by translating the phrases for each window as they are created. In most applications the main window is created just once. Dialogs are often created once and then shown and hidden as retquired. Once the initial translation has taken place there is no further runtime overhead for the translated windows. Only those windows that are created, destroyed and subsequently created will have a translation performance cost.</p> -<p>Creating applications that can switch language at runtime is possible with TQt, but retquires a certain amount of programmer intervention and will of course incur some runtime performance cost.</p> +<p>TQt minimizes the performance cost of using translations by translating the phrases for each window as they are created. In most applications the main window is created just once. Dialogs are often created once and then shown and hidden as required. Once the initial translation has taken place there is no further runtime overhead for the translated windows. Only those windows that are created, destroyed and subsequently created will have a translation performance cost.</p> +<p>Creating applications that can switch language at runtime is possible with TQt, but requires a certain amount of programmer intervention and will of course incur some runtime performance cost.</p> <h3><a name="1"></a>Making the Application Translation Aware</h3> <p>Programmers should make their application look for and load the appropriate translation file and mark user-visible text and Ctrl keyboard accelerators as targets for translation.</p> -<p>Each piece of text that retquires translating retquires context to help the translator identify where in the program the text occurs. In the case of multiple identical texts that retquire different translations, the translator also retquires some information to disambiguate the source texts. Marking text for translation will automatically cause the class name to be used as basic context information. In some cases the programmer may be retquired to add additional information to help the translator.</p> +<p>Each piece of text that requires translating requires context to help the translator identify where in the program the text occurs. In the case of multiple identical texts that require different translations, the translator also requires some information to disambiguate the source texts. Marking text for translation will automatically cause the class name to be used as basic context information. In some cases the programmer may be required to add additional information to help the translator.</p> <h4><a name="1-1"></a>Creating Translation Files</h4> <!-- index .ts Files --><!-- index Translation Source Files --><p>Translation files consist of all the user-visible text and Ctrl key accelerators in an application and translations of that text. Translation files are created as follows:</p> <!-- index lupdate --><!-- index lrelease --><ol type=1><li><p>Run <a href="linguist-manual-2.html#2">lupdate</a> initially to generate the first set of <tt>.ts</tt> translation source files with all the user-visible text but no translations.</p> @@ -447,7 +447,7 @@ TRANSLATIONS = tt3_pt.ts but = new <a href="qradiobutton.html">TQRadioButton</a>( <a href="qobject.html#tr">tr</a>("Disabled"), colors ); but-><a href="qbutton.html#toggle">toggle</a>(); </pre> - <p>Notice the two occurrences of <tt>tr("Enabled")</tt> and of <tt>tr("Disabled")</tt> in PrintPanel. Since both "Enabled"s and "Disabled"s appear in the same context <em>TQt Linguist</em> will only display one occurrence of each and will use the same translations for the duplicates that it doesn't display. Whilst this is a useful timesaver, in some languages, such as Portuguese, the second occurrence retquires a separate translation. We will see how <em>TQt Linguist</em> can be made to display all the occurrences for separate translation shortly.</p> + <p>Notice the two occurrences of <tt>tr("Enabled")</tt> and of <tt>tr("Disabled")</tt> in PrintPanel. Since both "Enabled"s and "Disabled"s appear in the same context <em>TQt Linguist</em> will only display one occurrence of each and will use the same translations for the duplicates that it doesn't display. Whilst this is a useful timesaver, in some languages, such as Portuguese, the second occurrence requires a separate translation. We will see how <em>TQt Linguist</em> can be made to display all the occurrences for separate translation shortly.</p> <!-- index MainWindow!in Translation Tutorial --><p>The header file for <tt>MainWindow</tt>, <tt>mainwindow.h</tt>, contains no surprises. In the implementation, <tt>mainwindow.cpp</tt>, we have some user-visible source texts that must be marked for translation.</p> <pre> <a href="qwidget.html#setCaption">setCaption</a>( <a href="qobject.html#tr">tr</a>("Troll Print 1.0") ); </pre> diff --git a/doc/html/mac-differences.html b/doc/html/mac-differences.html index 967462ed..c9a6eced 100644 --- a/doc/html/mac-differences.html +++ b/doc/html/mac-differences.html @@ -139,7 +139,7 @@ settings, same with any other default paths such as a lookup of dynamic libraries inside /usr/lib and similar default locations. <p> We still strongly recommend to build static applications where the library code is incorporated into the Mac OS X binary. However, in case you ship -applications that retquire plugin support,then you need to use dynamic +applications that require plugin support,then you need to use dynamic libraries as part of your application. <p> <h3> Combining Libraries </h3> @@ -213,7 +213,7 @@ do this: <p> <h3> Translating the Application Menu and native dialogs </h3> <a name="7-2"></a><p> You need to do a little extra to get the Application Menu and native dialogs -localized. This is a retquirement of Mac OS X and not of TQt. +localized. This is a requirement of Mac OS X and not of TQt. <p> First, you must add a localized resource folder inside the Bundle see: <p> http://developer.apple.com/documentation/CoreFoundation/Conceptual/CFBundles/index.html <p> And look for the heading: Adding Localized Resources diff --git a/doc/html/moc.html b/doc/html/moc.html index 322c570e..ad5bdd95 100644 --- a/doc/html/moc.html +++ b/doc/html/moc.html @@ -40,14 +40,14 @@ handles TQt's <a href="metaobjects.html">C++ extensions.</a> declarations that contain the <a href="metaobjects.html#Q_OBJECT">Q_OBJECT</a> macro, it produces another C++ source file which contains the <a href="metaobjects.html#meta-object">meta object</a> code for the classes that use the Q_OBJECT macro. Among other things, meta object code is -retquired for the signal/slot mechanism, runtime type information and +required for the signal/slot mechanism, runtime type information and the dynamic property system. <p> The C++ source file generated by the moc must be compiled and linked with the implementation of the class (or it can be #included into the class's source file). <p> If you use <a href="qmake-manual.html">qmake</a> to create your Makefiles, build rules will be included that call the moc when -retquired, so you will not need to use the moc directly. For more +required, so you will not need to use the moc directly. For more background information on moc, see <a href="templates.html">Why doesn't TQt use templates for signals and slots?</a>. <p> <h2> Usage @@ -265,7 +265,7 @@ templates cannot have signals or slots. Here is an example: <p> Less importantly, the following constructs are illegal. All of them have alternatives which we think are usually better, so removing these limitations is not a high priority for us. -<p> <h3> Multiple inheritance retquires <a href="qobject.html">TQObject</a> to be first +<p> <h3> Multiple inheritance requires <a href="qobject.html">TQObject</a> to be first </h3> <a name="5-1"></a><p> If you are using multiple inheritance, moc assumes that the <em>first</em> inherited class is a subclass of TQObject. Also, be sure that <em>only</em> diff --git a/doc/html/motif-walkthrough-10.html b/doc/html/motif-walkthrough-10.html index 5baecdf8..35ab043c 100644 --- a/doc/html/motif-walkthrough-10.html +++ b/doc/html/motif-walkthrough-10.html @@ -68,7 +68,7 @@ uses <em>delete</em> or <a href="qcstring.html#qstrdup">qstrdup</a>() when stori <p> Almost all of the functions in our application are affected by this change. In most cases, we end up removing more code than we are adding. To keep the size of this walkthrough reasonable, we've only -shown a small portion of the retquired changes, since the changes are +shown a small portion of the required changes, since the changes are very similar to those shown above. <p> <h2> Writing Platform-Independent Code </h2> diff --git a/doc/html/motif-walkthrough-3.html b/doc/html/motif-walkthrough-3.html index 2c0cdba3..8427c5cf 100644 --- a/doc/html/motif-walkthrough-3.html +++ b/doc/html/motif-walkthrough-3.html @@ -100,7 +100,7 @@ now use <a href="qfiledialog.html">TQFileDialog</a>. <a name="2"></a><p> The <em>Page Delete</em> dialog is created and used in <tt>actions.c</tt>. We need to migrate this file to C++. We rename it to <tt>actions.cpp</tt>, modify the project file and regenerate the <tt>Makefile</tt>. -<p> The changes retquired to make <tt>actions.cpp</tt> compile are minimal. We +<p> The changes required to make <tt>actions.cpp</tt> compile are minimal. We need to wrap more C header files and global variables in an <tt>extern "C"</tt> block. <p> @@ -131,7 +131,7 @@ completely. <p> The <em>IO Error</em> dialog is created and used in <tt>io.c</tt>. We need to migrate this file to C++. We rename it to <tt>io.cpp</tt>, modify the project file and regenerate the <tt>Makefile</tt>. -<p> The changes retquired to make <tt>io.cpp</tt> compile are minimal. We need +<p> The changes required to make <tt>io.cpp</tt> compile are minimal. We need to wrap more C header files and global variables in an <tt>extern "C"</tt> block. <p> diff --git a/doc/html/motif-walkthrough.html b/doc/html/motif-walkthrough.html index 6ec13d12..b0add895 100644 --- a/doc/html/motif-walkthrough.html +++ b/doc/html/motif-walkthrough.html @@ -38,7 +38,7 @@ body { background: #ffffff; color: black; } to the TQt toolkit using the <em>TQt Motif Extension</em>. <p> It is rarely practical for a large project with hundreds of thousands or even millions of lines of code to be migrated all at once; such an -endeavor would retquire too many development resources and would incur +endeavor would require too many development resources and would incur significant risks. Every line of code would have to be rewritten, every user interface redesigned, and quality assurance tests and procedures all rewritten. The <em>TQt Motif Extension</em> provides a @@ -79,7 +79,7 @@ references to the source code, which is included in the <tt>extensions/motif/exa <p> <h2> Preretquisites </h2> <a name="2"></a><p> Before we can start using the <em>TQt Motif Extension</em>, we must satisfy -these retquirements: +these requirements: <p> <ol type=1> <li> We are using the X11R6.x and Motif 2.x libraries. <li> The project is compilable by a C++ compiler. @@ -88,7 +88,7 @@ these retquirements: </ol> <p> <h3> X11R6.x and Motif 2.x Libraries </h3> -<a name="2-1"></a><p> The mechanisms used by the <em>TQt Motif Extension</em> retquire development +<a name="2-1"></a><p> The mechanisms used by the <em>TQt Motif Extension</em> require development headers and libraries from the X11R6 release and the Motif 2.0 release. Newer versions of these can also be used. <p> <h3> C++ Compiler diff --git a/doc/html/network.html b/doc/html/network.html index 833a5693..5d395af9 100644 --- a/doc/html/network.html +++ b/doc/html/network.html @@ -315,7 +315,7 @@ some special signals and at the end you must <em>always</em> emit a <tt>finished change the state of the <a href="qnetworkoperation.html">TQNetworkOperation</a> during processing. You can also get and set <a href="qnetworkoperation.html">TQNetworkOperation</a> arguments as the operation progresses. -<p> It may occur that the network protocol you implement only retquires a +<p> It may occur that the network protocol you implement only requires a subset of these operations. In such cases, simply reimplement the operations which are supported by the protocol. Additionally you must specify which operations you support. This is achieved by diff --git a/doc/html/object.html b/doc/html/object.html index ceb8cffb..f89a61c9 100644 --- a/doc/html/object.html +++ b/doc/html/object.html @@ -36,7 +36,7 @@ body { background: #ffffff; color: black; } <p> The standard C++ Object Model provides very efficient runtime support for the object paradigm. But the C++ Object Model's static nature is inflexibile in certain problem domains. Graphical User Interface -programming is a domain that retquires both runtime efficiency and a +programming is a domain that requires both runtime efficiency and a high level of flexibility. TQt provides this, by combining the speed of C++ with the flexibility of the TQt Object Model. <p> TQt adds these features to C++: @@ -60,7 +60,7 @@ pointers which become "dangling pointers" when their objects are destroyed. <p> Many of these TQt features are implemented with standard C++ techniques, based on inheritance from <a href="qobject.html">TQObject</a>. Others, like the object communication mechanism and the dynamic property system, -retquire the <a href="metaobjects.html">Meta Object System</a> provided +require the <a href="metaobjects.html">Meta Object System</a> provided by TQt's own <a href="moc.html">Meta Object Compiler (moc)</a>. <p> The Meta Object System is a C++ extension that makes the language better suited to true component GUI programming. Although templates can diff --git a/doc/html/opengl-x11-overlays.html b/doc/html/opengl-x11-overlays.html index 38158289..df139e84 100644 --- a/doc/html/opengl-x11-overlays.html +++ b/doc/html/opengl-x11-overlays.html @@ -46,7 +46,7 @@ following is a discussion on how to use non-TQGL widgets in overlay planes. <p> In the typical case, X11 overlays can easily be used together with the current version of TQt and the TQt OpenGL Extension. The following -retquirements apply: +requirements apply: <p> <ol type=1> <li> Your X server and graphics card/hardware must support overlays. For many X servers, overlay support can be turned on with diff --git a/doc/html/opengl.html b/doc/html/opengl.html index d1e73ba0..5cc85536 100644 --- a/doc/html/opengl.html +++ b/doc/html/opengl.html @@ -59,13 +59,13 @@ it will include the TQt OpenGL module in the TQt library. (If your OpenGL headers or libraries are placed in a non-standard directory, you may need to change the QMAKE_INCDIR_OPENGL and/or QMAKE_LIBDIR_OPENGL in the config file for your system). Some -configurations retquire threading to be enabled for OpenGL, so if +configurations require threading to be enabled for OpenGL, so if OpenGL is not detected, try <tt>configure -thread</tt>. <p> When you install TQt for Windows, the TQt OpenGL module is always included. <p> The TQt OpenGL module is not licensed for use with the TQt Professional Edition. Consider upgrading to the TQt Enterprise Edition if you -retquire OpenGL support. +require OpenGL support. <p> Note about using Mesa on X11: Mesa versions earlier than 3.1 would use the name "MesaGL" and "MesaGLU" for the libraries, instead of "GL" and "GLU". If you want to use a pre-3.1 version of Mesa, you must change diff --git a/doc/html/picture-example.html b/doc/html/picture-example.html index b851d4cb..6734d4a1 100644 --- a/doc/html/picture-example.html +++ b/doc/html/picture-example.html @@ -141,7 +141,7 @@ void PictureDisplay::<a href="qwidget.html#paintEvent">paintEvent</a>( <a href=" int main( int argc, char **argv ) { - <a href="qapplication.html">TQApplication</a> a( argc, argv ); // TQApplication retquired! + <a href="qapplication.html">TQApplication</a> a( argc, argv ); // TQApplication required! const char *fileName = "car.pic"; // default picture file name diff --git a/doc/html/plugins-howto.html b/doc/html/plugins-howto.html index 97ecd683..6ab263e8 100644 --- a/doc/html/plugins-howto.html +++ b/doc/html/plugins-howto.html @@ -71,7 +71,7 @@ with calls to <a href="qapplication.html#addLibraryPath">TQApplication::addLibra set your own path or paths you can use <a href="qapplication.html#setLibraryPaths">TQApplication::setLibraryPaths</a>(). <p> Suppose that you have a new style class called 'MyStyle' that you want -to make available as a plugin. The retquired code is straightforward: +to make available as a plugin. The required code is straightforward: <pre> class MyStylePlugin : public <a href="qstyleplugin.html">TQStylePlugin</a> { @@ -101,21 +101,21 @@ empty. There are only two virtual functions that must be implemented. The first is keys() which returns a string list of the classes implemented in the plugin. (We've just implemented one class in the example above.) The second is a function that returns an object of the -retquired class (or 0 if the plugin is asked to create an object of a +required class (or 0 if the plugin is asked to create an object of a class that it doesn't implement). For <a href="qstyleplugin.html">TQStylePlugin</a>, this second function is called create(). <p> It is possible to implement any number of plugin subclasses in a single plugin, providing they are all derived from the same base class, e.g. TQStylePlugin. <p> For database drivers, image formats, custom widgets and text codecs, -no explicit object creation is retquired. TQt will find and create them -as retquired. Styles are an exception, since you might want to set a +no explicit object creation is required. TQt will find and create them +as required. Styles are an exception, since you might want to set a style explicitly in code. To apply a style, use code like this: <pre> TQApplication::<a href="qapplication.html#setStyle">setStyle</a>( TQStyleFactory::<a href="qstylefactory.html#create">create</a>( "MyStyle" ) ); </pre> -<p> Some plugin classes retquire additional functions to be implemented. +<p> Some plugin classes require additional functions to be implemented. See the <a href="designer-manual.html">TQt Designer manual's</a>, 'Creating Custom Widgets' section in the 'Creating Custom Widgets' chapter, for a complete example of a <a href="qwidgetplugin.html">TQWidgetPlugin</a>, which implements @@ -126,7 +126,7 @@ TQWidgetPlugins. must be reimplemented for each type of plugin. <p> TQt applications automatically know which plugins are available, because plugins are stored in the standard plugin subdirectories. -Because of this applications don't retquire any code to find and load +Because of this applications don't require any code to find and load plugins, since TQt handles them automatically. <p> The default directory for plugins is <tt>QTDIR/plugins</tt><sup>*</sup>, with each type of plugin in a subdirectory for that type, e.g. <tt>styles</tt>. If you want your applications to use plugins and you don't @@ -210,7 +210,7 @@ determine if the plugin is binary compatible. available in two different configurations. However, the developer writing plugins would need to know which features are in use, both in their plugin and internally by the utility -classes in TQt. The TQt library would retquire complex feature +classes in TQt. The TQt library would require complex feature and dependency queries and verification when loading plugins. Retquiring this would place an unnecessary burden on the developer, and increase the overhead of loading a plugin. To reduce both diff --git a/doc/html/porting.html b/doc/html/porting.html index 2bbe632a..c812b21c 100644 --- a/doc/html/porting.html +++ b/doc/html/porting.html @@ -458,7 +458,7 @@ parameter list. The <tt>echo</tt> parameter is the third parameter and defaults to TQLineEdit::Normal. <p> If you used calls to <a href="qinputdialog.html#getText">TQInputDialog::getText</a>(...) that provided more -than the first two retquired parameters you will must add a value +than the first two required parameters you will must add a value for the <tt>echo</tt> parameter. <p> <h2> <a href="qlayout.html">TQLayout</a> and Other Abstract Layout Classes </h2> @@ -497,7 +497,7 @@ now work on paragraphs. published the internal data structure. <p> In most cases, applications that used TQMultiLineEdit will continue to work without problems. Applications that worked in terms of lines may -retquire some porting. +require some porting. <p> The source code for the old 2.x version of TQMultiLineEdit can be found in <tt>$QTDIR/src/attic/qtmultilineedit.h/cpp</tt>. Note that the class has been renamed to TQtMultiLineEdit to avoid name clashes. If you really diff --git a/doc/html/porting2.html b/doc/html/porting2.html index 9f44766e..723a4e0a 100644 --- a/doc/html/porting2.html +++ b/doc/html/porting2.html @@ -64,7 +64,7 @@ compiler errors (rather than mysterious results), or produce run-time messages. The result is that TQt 2.x includes many additional features, discards obsolete functionality that is easily converted to use the new features, and that porting an application from TQt 1.x to TQt 2.x is -a simple task well worth the amount of effort retquired. +a simple task well worth the amount of effort required. <p> To port code using TQt 1.x to use TQt 2.x: <p> <ul> <li> Briefly read the porting notes below to get an idea of what to expect. @@ -224,7 +224,7 @@ you use that you will incur a performance penalty since all TQt functions that took const char* now take const TQString&. <p> <p> To take full advantage of the new <a href="i18n.html#internationalization">Internationalization</a> -functionality in TQt 2.x, the following steps are retquired: +functionality in TQt 2.x, the following steps are required: <p> <ul> <li> Start converting all uses of "const char*" in parameters to "const TQString&" - this can often be done mechanically, eg. @@ -784,7 +784,7 @@ use it outside a member function, you'll need to prefix with TQt::. <p> <h3><a name="TQPicture">TQPicture</a></h3> <p> <p>The binary storage format of <a href="qpicture.html">TQPicture</a> is changed, but the TQt 2.x TQPicture class can both read and write TQt 1.x format TQPictures. No -special handling is retquired for reading; TQPicture will automatically +special handling is required for reading; TQPicture will automatically detect the version number. In order to write a TQt 1.x format TQPicture, set the formatVersion parameter to 1 in the TQPicture constructor. <p> <p>For writing TQt 1.x format TQPictures, the compatibility issues of <a diff --git a/doc/html/propertydocs b/doc/html/propertydocs index 6d8d3e7f..a3404ce6 100644 --- a/doc/html/propertydocs +++ b/doc/html/propertydocs @@ -1115,7 +1115,7 @@ proper behavior and even then QDockWindow does not limit stretchablilty. <name>QDockWindow::newLine</name> <doc href="qdockwindow.html#newLine-prop"> <p>This property holds whether the dock window prefers to start a new line in the dock area. -<p>The default is FALSE, i.e. the dock window doesn't retquire a new +<p>The default is FALSE, i.e. the dock window doesn't require a new line in the dock area. <p>Set this property's value with <a href="qdockwindow.html#setNewLine">setNewLine</a>() and get this property's value with <a href="qdockwindow.html#newLine">newLine</a>(). @@ -2145,17 +2145,17 @@ arguments. <p> The mask format understands these mask characters: <center><table cellpadding="4" cellspacing="2" border="0"> <tr bgcolor="#a2c511"> <th valign="top">Character <th valign="top">Meaning -<tr bgcolor="#f0f0f0"> <td valign="top"><tt>A</tt> <td valign="top">ASCII alphabetic character retquired. A-Z, a-z. -<tr bgcolor="#d0d0d0"> <td valign="top"><tt>a</tt> <td valign="top">ASCII alphabetic character permitted but not retquired. -<tr bgcolor="#f0f0f0"> <td valign="top"><tt>N</tt> <td valign="top">ASCII alphanumeric character retquired. A-Z, a-z, 0-9. -<tr bgcolor="#d0d0d0"> <td valign="top"><tt>n</tt> <td valign="top">ASCII alphanumeric character permitted but not retquired. -<tr bgcolor="#f0f0f0"> <td valign="top"><tt>X</tt> <td valign="top">Any character retquired. -<tr bgcolor="#d0d0d0"> <td valign="top"><a href="qwidget.html#x-prop">x</a> <td valign="top">Any character permitted but not retquired. -<tr bgcolor="#f0f0f0"> <td valign="top"><tt>9</tt> <td valign="top">ASCII digit retquired. 0-9. -<tr bgcolor="#d0d0d0"> <td valign="top"><tt>0</tt> <td valign="top">ASCII digit permitted but not retquired. -<tr bgcolor="#f0f0f0"> <td valign="top"><tt>D</tt> <td valign="top">ASCII digit retquired. 1-9. -<tr bgcolor="#d0d0d0"> <td valign="top"><tt>d</tt> <td valign="top">ASCII digit permitted but not retquired (1-9). -<tr bgcolor="#f0f0f0"> <td valign="top"><tt>#</tt> <td valign="top">ASCII digit or plus/minus sign permitted but not retquired. +<tr bgcolor="#f0f0f0"> <td valign="top"><tt>A</tt> <td valign="top">ASCII alphabetic character required. A-Z, a-z. +<tr bgcolor="#d0d0d0"> <td valign="top"><tt>a</tt> <td valign="top">ASCII alphabetic character permitted but not required. +<tr bgcolor="#f0f0f0"> <td valign="top"><tt>N</tt> <td valign="top">ASCII alphanumeric character required. A-Z, a-z, 0-9. +<tr bgcolor="#d0d0d0"> <td valign="top"><tt>n</tt> <td valign="top">ASCII alphanumeric character permitted but not required. +<tr bgcolor="#f0f0f0"> <td valign="top"><tt>X</tt> <td valign="top">Any character required. +<tr bgcolor="#d0d0d0"> <td valign="top"><a href="qwidget.html#x-prop">x</a> <td valign="top">Any character permitted but not required. +<tr bgcolor="#f0f0f0"> <td valign="top"><tt>9</tt> <td valign="top">ASCII digit required. 0-9. +<tr bgcolor="#d0d0d0"> <td valign="top"><tt>0</tt> <td valign="top">ASCII digit permitted but not required. +<tr bgcolor="#f0f0f0"> <td valign="top"><tt>D</tt> <td valign="top">ASCII digit required. 1-9. +<tr bgcolor="#d0d0d0"> <td valign="top"><tt>d</tt> <td valign="top">ASCII digit permitted but not required (1-9). +<tr bgcolor="#f0f0f0"> <td valign="top"><tt>#</tt> <td valign="top">ASCII digit or plus/minus sign permitted but not required. <tr bgcolor="#d0d0d0"> <td valign="top"><tt>&gt;</tt> <td valign="top">All following alphabetic characters are uppercased. <tr bgcolor="#f0f0f0"> <td valign="top"><tt>&lt;</tt> <td valign="top">All following alphabetic characters are lowercased. <tr bgcolor="#d0d0d0"> <td valign="top"><tt>!</tt> <td valign="top">Switch off case conversion. @@ -3561,7 +3561,7 @@ database client used: <li> connect_timeout <li> options <li> tty -<li> retquiressl +<li> requiressl <li> service </ul> <tr bgcolor="#a2c511"> <th valign="top">DB2 <th valign="top">OCI <th valign="top">TDS @@ -3587,7 +3587,7 @@ database client used: } ... // PostgreSQL connection - db-&gt;setConnectOptions( "retquiressl=1" ); // enable PostgreSQL SSL connections + db-&gt;setConnectOptions( "requiressl=1" ); // enable PostgreSQL SSL connections if ( !db-&gt;open() ) { db-&gt;setConnectOptions(); // clear options ... @@ -3630,7 +3630,7 @@ entry in the ODBC manager: ... </pre> -("FIL" is the retquired spelling in Microsoft's API.) +("FIL" is the required spelling in Microsoft's API.) <p> There is no default value. <p>Set this property's value with <a href="qsqldatabase.html#setDatabaseName">setDatabaseName</a>() and get this property's value with <a href="qsqldatabase.html#databaseName">databaseName</a>(). @@ -4374,7 +4374,7 @@ that the auto mask calculation works, you should add: <p> at the end of your event handlers. This is true for all member functions that change the appearance of the widget in a way that -retquires a recalculation of the mask. +requires a recalculation of the mask. <p> While being a technically appealing concept, masks have a big drawback: when using complex masks that cannot be expressed easily with relatively simple regions, they can be very slow on some diff --git a/doc/html/qaccel-h.html b/doc/html/qaccel-h.html index 5b630c51..da828ee1 100644 --- a/doc/html/qaccel-h.html +++ b/doc/html/qaccel-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qaccessible-h.html b/doc/html/qaccessible-h.html index 0ab9461b..4c404054 100644 --- a/doc/html/qaccessible-h.html +++ b/doc/html/qaccessible-h.html @@ -52,7 +52,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qaction-h.html b/doc/html/qaction-h.html index ae63dcc6..06b32fe1 100644 --- a/doc/html/qaction-h.html +++ b/doc/html/qaction-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qapplication-h.html b/doc/html/qapplication-h.html index 7b26e42f..23cee48e 100644 --- a/doc/html/qapplication-h.html +++ b/doc/html/qapplication-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qapplication.html b/doc/html/qapplication.html index 353c3ee3..9dc8edb3 100644 --- a/doc/html/qapplication.html +++ b/doc/html/qapplication.html @@ -744,7 +744,7 @@ rejected, the shutdown is canceled. <h3 class=fn>int <a name="cursorFlashTime"></a>TQApplication::cursorFlashTime ()<tt> [static]</tt> </h3> Returns the text cursor's flash (blink) time in milliseconds. The -flash time is the time retquired to display, invert and restore the +flash time is the time required to display, invert and restore the caret display. <p> The default value on X11 is 1000 milliseconds. On Windows, the control panel value is used. @@ -1303,7 +1303,7 @@ colors. On X11, this option is the same as NormalColor. On Windows, TQt creates a Windows palette, and allocates colors to it on demand. <li> TQApplication::ManyColor. Use this option if your application is very color hungry -(e.g. it retquires thousands of colors). +(e.g. it requires thousands of colors). Under X11 the effect is: <ul> <li> For 256-color displays which have at best a 256 color true color @@ -1347,7 +1347,7 @@ green, and blue components always have one of the following values: <h3 class=fn>void <a name="setCursorFlashTime"></a>TQApplication::setCursorFlashTime ( int msecs )<tt> [static]</tt> </h3> Sets the text cursor's flash (blink) time to <em>msecs</em> -milliseconds. The flash time is the time retquired to display, +milliseconds. The flash time is the time required to display, invert and restore the caret display. Usually the text cursor is displayed for <em>msecs/2</em> milliseconds, then hidden for <em>msecs/2</em> milliseconds, but this may vary. @@ -1522,7 +1522,7 @@ any previously set class specific palettes. <h3 class=fn>void <a name="setReverseLayout"></a>TQApplication::setReverseLayout ( bool b )<tt> [static]</tt> </h3> If <em>b</em> is TRUE, all dialogs and widgets will be laid out in a -mirrored fashion, as retquired by right to left languages such as +mirrored fashion, as required by right to left languages such as Arabic and Hebrew. If <em>b</em> is FALSE, dialogs and widgets are laid out left to right. <p> Changing this flag in runtime does not cause a relayout of already diff --git a/doc/html/qasciicache-h.html b/doc/html/qasciicache-h.html index 369128a3..70cfb959 100644 --- a/doc/html/qasciicache-h.html +++ b/doc/html/qasciicache-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qasciidict-h.html b/doc/html/qasciidict-h.html index 30b5d5c0..040a4a03 100644 --- a/doc/html/qasciidict-h.html +++ b/doc/html/qasciidict-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qassistantclient-h.html b/doc/html/qassistantclient-h.html index e1cae1b7..2803b022 100644 --- a/doc/html/qassistantclient-h.html +++ b/doc/html/qassistantclient-h.html @@ -48,7 +48,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qassistantclient.html b/doc/html/qassistantclient.html index 6e664a44..37a500b5 100644 --- a/doc/html/qassistantclient.html +++ b/doc/html/qassistantclient.html @@ -70,7 +70,7 @@ then call <a href="#showPage">showPage</a>() as often as necessary to show your pages. When you call showPage(), TQt Assistant will be launched if it isn't already running. <p> The TQAssistantClient instance can open (<a href="#openAssistant">openAssistant</a>()) or close -(<a href="#closeAssistant">closeAssistant</a>()) TQt Assistant whenever retquired. If TQt Assistant +(<a href="#closeAssistant">closeAssistant</a>()) TQt Assistant whenever required. If TQt Assistant is open, <a href="#isOpen">isOpen</a>() returns TRUE. <p> One TQAssistantClient instance interacts with one TQt Assistant instance, so every time you call openAssistant(), showPage() or diff --git a/doc/html/qasyncimageio-h.html b/doc/html/qasyncimageio-h.html index 99c0c8f9..245810f5 100644 --- a/doc/html/qasyncimageio-h.html +++ b/doc/html/qasyncimageio-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qasyncio-h.html b/doc/html/qasyncio-h.html index 3894724f..93bca25c 100644 --- a/doc/html/qasyncio-h.html +++ b/doc/html/qasyncio-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qaxbase.html b/doc/html/qaxbase.html index 473d5cad..41c40da2 100644 --- a/doc/html/qaxbase.html +++ b/doc/html/qaxbase.html @@ -312,7 +312,7 @@ See the <a href="qaxbase.html#control-prop">"control"</a> property for details. <h3 class=fn>void <a name="disableClassInfo"></a>TQAxBase::disableClassInfo () </h3> Disables the class info generation for this ActiveX container. If -you don't retquire any class information about the ActiveX control +you don't require any class information about the ActiveX control use this function to speed up the <a href="metaobjects.html#meta-object">meta object</a> generation. <p> Note that this function must be called immediately after construction of the object (without passing an object identifier), diff --git a/doc/html/qaxbindable.html b/doc/html/qaxbindable.html index 2d495cb3..d0834e19 100644 --- a/doc/html/qaxbindable.html +++ b/doc/html/qaxbindable.html @@ -65,7 +65,7 @@ The TQAxBindable class provides an interface between a <p> The functions provided by this class allow an ActiveX control to communicate property changes to a client application. Inherit your control class from both TQWidget (directly or indirectly) and -this class to get access to this class's functions. The <a href="moc.html">meta object compiler</a> retquires you to inherit from +this class to get access to this class's functions. The <a href="moc.html">meta object compiler</a> requires you to inherit from TQWidget <em>first</em>. <p> <pre> class MyActiveX : public <a href="qwidget.html">TQWidget</a>, public TQAxBindable diff --git a/doc/html/qaxcontainer.html b/doc/html/qaxcontainer.html index 381bf31b..65d0b86c 100644 --- a/doc/html/qaxcontainer.html +++ b/doc/html/qaxcontainer.html @@ -153,7 +153,7 @@ Studio's Debug output). </h4> <a name="5-1-1"></a><p> The control requested in <a href="qaxbase.html#setControl">TQAxBase::setControl</a>() is not installed on this system, or is not accessible for the current user. -<p> The control might retquire administrator rights, or a license key. +<p> The control might require administrator rights, or a license key. If the control is licensed, reimplement initialize() and use the COM APIs to call the IClassFactory2 interface functions. <p> <h4> TQAxBase::internalInvoke: No such method diff --git a/doc/html/qaxserver-example-hierarchy.html b/doc/html/qaxserver-example-hierarchy.html index 3179e127..1bede5f0 100644 --- a/doc/html/qaxserver-example-hierarchy.html +++ b/doc/html/qaxserver-example-hierarchy.html @@ -190,7 +190,7 @@ interface of <tt>TQParentWidget</tt> objects. return TQUuid(); } -</pre>COM however retquires the IDs for the interfaces of the sub types as +</pre>COM however requires the IDs for the interfaces of the sub types as well to be able to marshal calls correctly. <p> <pre> <a href="qstring.html">TQString</a> exposeToSuperClass( const <a href="qstring.html">TQString</a> &key ) const { @@ -208,7 +208,7 @@ macro. <p> To build the example you must first build the <a href="qaxserver.html">TQAxServer</a> library. Then run qmake and your make tool in <tt>examples/multiple</tt>. <p> <hr> -<p> The <a href="qaxserver-demo-hierarchy.html">demonstration</a> retquires your +<p> The <a href="qaxserver-demo-hierarchy.html">demonstration</a> requires your WebBrowser to support ActiveX controls, and scripting to be enabled. <p> diff --git a/doc/html/qaxserver-example-menus.html b/doc/html/qaxserver-example-menus.html index c111baf3..b2b4a1ca 100644 --- a/doc/html/qaxserver-example-menus.html +++ b/doc/html/qaxserver-example-menus.html @@ -39,7 +39,7 @@ a <a href="qmainwindow.html">TQMainWindow</a> to implement an in-place active co <p> To build the example you must first build the <a href="qaxserver.html">TQAxServer</a> library. Then run qmake and your make tool in <tt>examples/menus</tt>. <p> <hr> -<p> The <a href="qaxserver-demo-menus.html">demonstration</a> retquires your +<p> The <a href="qaxserver-demo-menus.html">demonstration</a> requires your WebBrowser to support ActiveX controls, and scripting to be enabled. <p> diff --git a/doc/html/qaxserver-example-multiple.html b/doc/html/qaxserver-example-multiple.html index 457342dd..0754c627 100644 --- a/doc/html/qaxserver-example-multiple.html +++ b/doc/html/qaxserver-example-multiple.html @@ -150,7 +150,7 @@ macro. <p> To build the example you must first build the <a href="qaxserver.html">TQAxServer</a> library. Then run qmake and your make tool in <tt>examples/multiple</tt>. <p> <hr> -<p> The <a href="qaxserver-demo-multiple.html">demonstration</a> retquires your +<p> The <a href="qaxserver-demo-multiple.html">demonstration</a> requires your WebBrowser to support ActiveX controls, and scripting to be enabled. <p> diff --git a/doc/html/qaxserver-example-opengl.html b/doc/html/qaxserver-example-opengl.html index 52f73083..82c69458 100644 --- a/doc/html/qaxserver-example-opengl.html +++ b/doc/html/qaxserver-example-opengl.html @@ -163,7 +163,7 @@ with information about supported and enabled safety options, and returns <p> To build the example you must first build the <a href="qaxserver.html">TQAxServer</a> library. Then run qmake and your make tool in <tt>examples/wrapper</tt>. <p> <hr> -<p> The <a href="qaxserver-demo-opengl.html">demonstration</a> retquires your +<p> The <a href="qaxserver-demo-opengl.html">demonstration</a> requires your WebBrowser to support ActiveX controls, and scripting to be enabled. <p> In contrast to the other TQAxServer examples Internet Explorer will not open a dialog box to ask the user whether or not the scripting of the GLBox diff --git a/doc/html/qaxserver-example-simple.html b/doc/html/qaxserver-example-simple.html index 4cc86423..7a4caf05 100644 --- a/doc/html/qaxserver-example-simple.html +++ b/doc/html/qaxserver-example-simple.html @@ -130,7 +130,7 @@ and <a href="qaxbindable.html#propertyChanged">TQAxBindable::propertyChanged</a> <p> To build the example you must first build the <a href="qaxserver.html">TQAxServer</a> library. Then run qmake and your make tool in <tt>examples/simple</tt>. <p> <hr> -<p> The <a href="qaxserver-demo-simple.html">demonstration</a> retquires your +<p> The <a href="qaxserver-demo-simple.html">demonstration</a> requires your WebBrowser to support ActiveX controls, and scripting to be enabled. <p> The simple ActiveX control is embedded using the <tt><object></tt> tag. diff --git a/doc/html/qaxserver-example-tetrax.html b/doc/html/qaxserver-example-tetrax.html index bbe994a0..4f8418d0 100644 --- a/doc/html/qaxserver-example-tetrax.html +++ b/doc/html/qaxserver-example-tetrax.html @@ -47,7 +47,7 @@ tetrax.cpp file. The default implementation of the <a href="qaxfactory.html">TQAxFactory</a> is used through the TQAXFACTORY_DEFAULT macro, and exports the TQTetrax object specifying -the five unique IDs retquired by COM to instantiate and communicate with +the five unique IDs required by COM to instantiate and communicate with the server. <pre> #include "qtetrax.h" #include "qdragapp.h" @@ -86,7 +86,7 @@ the program has been started by the user, not by COM). <p> To build the example you must first build the <a href="qaxserver.html">TQAxServer</a> library. Then run qmake and your make tool in <tt>examples/tetrix</tt>. <p> <hr> -<p> The <a href="qaxserver-demo-tetrax.html">demonstration</a> retquires your +<p> The <a href="qaxserver-demo-tetrax.html">demonstration</a> requires your Web browser to support ActiveX controls, and scripting to be enabled. <p> diff --git a/doc/html/qaxserver-example-wrapper.html b/doc/html/qaxserver-example-wrapper.html index dad6313b..f74c8043 100644 --- a/doc/html/qaxserver-example-wrapper.html +++ b/doc/html/qaxserver-example-wrapper.html @@ -144,7 +144,7 @@ IDs of the COM classes and interfaces for each control. <p> To build the example you must first build the <a href="qaxserver.html">TQAxServer</a> library. Then run qmake and your make tool in <tt>examples/wrapper</tt>. <p> <hr> -<p> The <a href="qaxserver-demo-wrapper.html">demonstration</a> retquires your +<p> The <a href="qaxserver-demo-wrapper.html">demonstration</a> requires your WebBrowser to support ActiveX controls, and scripting to be enabled. <p> diff --git a/doc/html/qaxserver.html b/doc/html/qaxserver.html index 766a1e04..ad20e4c4 100644 --- a/doc/html/qaxserver.html +++ b/doc/html/qaxserver.html @@ -141,7 +141,7 @@ body { background: #ffffff; color: black; } <p> <h2> Introduction </h2> <a name="1"></a><p> The TQAxServer module provides a static library implementing the -functions retquired to turn a standard TQt binary into an ActiveX +functions required to turn a standard TQt binary into an ActiveX control server. <p> This module is part of the <a href="activeqt.html">ActiveTQt framework</a>. (To incorporate ActiveX controls in a TQt @@ -195,7 +195,7 @@ You can modify these files as long as it includes any file as the type library entry, ie. you can add version information or use a different toolbox icon. <p> The <tt>activeqt</tt> configuration will cause the <tt>qmake</tt> tool to add the -retquired build steps to the build system: +required build steps to the build system: <ul> <li> link the binary against <tt>qaxserver.lib</tt> <li> generate an interface definition and link the type library into @@ -226,7 +226,7 @@ continue to run. <p> An in-process server is usually smaller and has faster startup time. The communication between client and server is done directly through virtual function calls and does not introduce the overhead -retquired for remote procedure calls. But if the server crashes the +required for remote procedure calls. But if the server crashes the client application is likely to crash as well. <p> Both server types can use TQt either as a shared library, or statically linked into the server binary. @@ -259,7 +259,7 @@ Microsoft Visual C++ 6.0 compiler. <a name="4-1-1-1"></a><p> When the error occurs in code that uses the <a href="qaxfactory.html#TQAXFACTORY_DEFAULT">TQAXFACTORY_DEFAULT</a> macro, the widget class had no constructor that can be used by the default factory. Either add a standard widget constructor or -implement a custom factory that doesn't retquire one. +implement a custom factory that doesn't require one. <p> When the error occurs in code that uses the <a href="qaxfactory.html#TQAXFACTORY_EXPORT">TQAXFACTORY_EXPORT</a> macro, the <a href="qaxfactory.html">TQAxFactory</a> subclass had no appropriate constructor. Provide a public class constructor like @@ -304,18 +304,18 @@ of the binary to make it into an ActiveX server. <li> Attach the type library as a binary resource to the server <li> Register the server </ul> -<p> For this to work the server has to meet some retquirements: +<p> For this to work the server has to meet some requirements: <p> <ul> <li> All controls exposed can be created with nothing but a <a href="qapplication.html">TQApplication</a> instance being present <li> The initial linking of the server includes a temporary type library resource -<li> All dependencies retquired to run the server are in the system path +<li> All dependencies required to run the server are in the system path (or in the path used by the calling environment; note that Visual Studio has it's own set of environment variables listed in the Tools|Options|Directories dialog). </ul> -<p> If those retquirements are not met one ore more of the following +<p> If those requirements are not met one ore more of the following errors are likely to occure: <p> <h5> The server executable crashes </h5> @@ -341,7 +341,7 @@ the interface definition, and to register the server. If a dynamic link library the server links against is not in the path this might fail (e.g. Visual Studio calls the server using the enivronment settings specified in the "Directories" option). Make -sure that all DLLs retquired by your server are located in a +sure that all DLLs required by your server are located in a directory that is listed in the path as printed in the error message box. <p> <h5> The Server does not respond @@ -386,7 +386,7 @@ or any existing TQWidget subclass: <a href="metaobjects.html#Q_OBJECT">Q_OBJECT</a> </pre> -<p> The <a href="metaobjects.html#Q_OBJECT">Q_OBJECT</a> macro is retquired to provide the <a href="metaobjects.html#meta-object">meta object</a> information +<p> The <a href="metaobjects.html#Q_OBJECT">Q_OBJECT</a> macro is required to provide the <a href="metaobjects.html#meta-object">meta object</a> information about the widget to the ActiveTQt framework. Use the <tt>Q_PROPERTY</tt> macro to declare properties for the ActiveX control: <p> <pre> @@ -640,7 +640,7 @@ server must export an implementation of a <a href="qaxfactory.html">TQAxFactory< default factory when the server provides only a single ActiveX control, and implement a subclass of TQAxFactory to provide multiple ActiveX controls. The default factory is available -through a macro that takes the identifiers COM retquires to locate +through a macro that takes the identifiers COM requires to locate the ActiveX control on the target system: <p> <pre> TQAXFACTORY_DEFAULT ( MyActiveX, @@ -734,7 +734,7 @@ make the server available to the browser used to view your page, and you need to specify the location of the server package in your page. <p> To specify the location of a server, use the CODEBASE attribute in the OBJECT tag of your web-site. The value can point to the server -file itself, to an <tt>INF</tt> file listing other files the server retquires +file itself, to an <tt>INF</tt> file listing other files the server requires (e.g. the TQt DLL), or a compressed <tt>CAB</tt> archive. <p> INF and CAB files are documented in almost every book available about ActiveX and COM programming as well as in the MSDN library and various @@ -873,8 +873,8 @@ Ie. the default property of a push button would be "text". Ie. the default signal of a push button would be "clicked". <tr bgcolor="#f0f0f0"> <td valign="top">LicenseKey -<td valign="top">Object creation retquires the specified license key. The key can be -empty to retquire a licensed machine. By default classes are not +<td valign="top">Object creation requires the specified license key. The key can be +empty to require a licensed machine. By default classes are not licensed. Also see the following section. <tr bgcolor="#d0d0d0"> <td valign="top">StockEvents @@ -951,14 +951,14 @@ macro. }; </pre> -The key is retquired to be able to create an instance of <tt>MyLicensedControl</tt> +The key is required to be able to create an instance of <tt>MyLicensedControl</tt> on a machine that is not licensed itself. The licensed developer can now redistributes the server binary with his application, which creates the control using the value of "LicenseKey", while users of the application cannot create the control without the license key. <p> If a single license key for the control is not sufficient (ie. you want differnet developers to receive different license keys) you can specify an -empty key to indicate that the control retquires a license, and reimplement +empty key to indicate that the control requires a license, and reimplement <a href="qaxfactory.html#validateLicenseKey">TQAxFactory::validateLicenseKey</a>() to verify that a license exists on the system (ie. through a license file). <p> <h3> More Interfaces @@ -1056,10 +1056,10 @@ Microsoft OLE needs to marshal user defined types by reference (ByRef), and cannot marshal them by value (ByVal). This is why const-references and object parameters are not supported for <a href="qrect.html">TQRect</a>, <a href="qsize.html">TQSize</a> and <a href="qpoint.html">TQPoint</a>. Also note that -servers with this datatype retquire Windows 98 or DCOM 1.2 to be installed. +servers with this datatype require Windows 98 or DCOM 1.2 to be installed. <a href="#footnote-call3">Back...</a> <li><a name="footnote4"></a> -This is not retquired, but gives the client more control over +This is not required, but gives the client more control over the ActiveX control. <a href="#footnote-call4">Back...</a></ol> </hr> diff --git a/doc/html/qaxwidget.html b/doc/html/qaxwidget.html index 006e57f9..9870c0b4 100644 --- a/doc/html/qaxwidget.html +++ b/doc/html/qaxwidget.html @@ -235,7 +235,7 @@ VK_CONTROL or VK_MENU </table></center> <p> This table is the result of experimenting with popular ActiveX controls, ie. Internet Explorer and Microsoft Office applications, but for some -controls it might retquire modification. +controls it might require modification. <!-- eof --> <hr><p> diff --git a/doc/html/qbig5codec-h.html b/doc/html/qbig5codec-h.html index f815aadb..6e05ce67 100644 --- a/doc/html/qbig5codec-h.html +++ b/doc/html/qbig5codec-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qbitarray-h.html b/doc/html/qbitarray-h.html index 754bf12d..e0b4397b 100644 --- a/doc/html/qbitarray-h.html +++ b/doc/html/qbitarray-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qbitarray.html b/doc/html/qbitarray.html index 7584aa87..8ea0a68b 100644 --- a/doc/html/qbitarray.html +++ b/doc/html/qbitarray.html @@ -84,7 +84,7 @@ arrays or bits. <p> Bits can be manipulated by the <a href="#setBit">setBit</a>() and <a href="#clearBit">clearBit</a>() functions, but it is also possible to use the indexing [] operator to test and set individual bits. The [] operator is a little slower than -setBit() and clearBit() because some tricks are retquired to +setBit() and clearBit() because some tricks are required to implement single-bit assignments. <p> Example: <pre> diff --git a/doc/html/qbitmap-h.html b/doc/html/qbitmap-h.html index cd46a33f..c4b991eb 100644 --- a/doc/html/qbitmap-h.html +++ b/doc/html/qbitmap-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qbitval.html b/doc/html/qbitval.html index 759a7427..641bdd2d 100644 --- a/doc/html/qbitval.html +++ b/doc/html/qbitval.html @@ -49,7 +49,7 @@ body { background: #ffffff; color: black; } The TQBitVal class is an internal class, used with <a href="qbitarray.html">TQBitArray</a>. <p> -<p> The TQBitVal is retquired by the indexing [] operator on bit arrays. +<p> The TQBitVal is required by the indexing [] operator on bit arrays. It is not for use in any other context. <p>See also <a href="collection.html">Collection Classes</a>. diff --git a/doc/html/qbrush-h.html b/doc/html/qbrush-h.html index 50938b22..ca33253c 100644 --- a/doc/html/qbrush-h.html +++ b/doc/html/qbrush-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qbuffer-h.html b/doc/html/qbuffer-h.html index b7ec7c80..5fafba80 100644 --- a/doc/html/qbuffer-h.html +++ b/doc/html/qbuffer-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qbutton-h.html b/doc/html/qbutton-h.html index bad80e7e..6476f2e1 100644 --- a/doc/html/qbutton-h.html +++ b/doc/html/qbutton-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qbuttongroup-h.html b/doc/html/qbuttongroup-h.html index 9061a805..da29b22c 100644 --- a/doc/html/qbuttongroup-h.html +++ b/doc/html/qbuttongroup-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qcache-h.html b/doc/html/qcache-h.html index 3eb240fe..96a63fe9 100644 --- a/doc/html/qcache-h.html +++ b/doc/html/qcache-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qcanvas-h.html b/doc/html/qcanvas-h.html index 1b1f4ffa..c6fdf861 100644 --- a/doc/html/qcanvas-h.html +++ b/doc/html/qcanvas-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qcanvas.html b/doc/html/qcanvas.html index 5c68676f..fbfdbd12 100644 --- a/doc/html/qcanvas.html +++ b/doc/html/qcanvas.html @@ -266,7 +266,7 @@ item is an item that is in motion; see setVelocity().) 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 retquired, such as +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", @@ -408,10 +408,10 @@ many objects on the canvas. <p> The canvas is divided into chunks which are rectangular areas <em>chunksze</em> wide by <em>chunksze</em> high. Use a chunk size which is about the average size of the canvas items. If you choose a chunk size which is too small it will increase the amount of calculation -retquired when drawing since each change will affect many chunks. +required when drawing since each change will affect many chunks. If you choose a chunk size which is too large the amount of -drawing retquired will increase because for each change, a lot of -drawing will be retquired since there will be many (unchanged) +drawing required will increase because for each change, a lot of +drawing will be required since there will be many (unchanged) canvas items which are in the same chunk as the changed canvas items. <p> Internally, a canvas uses a low-resolution "chunk matrix" to keep diff --git a/doc/html/qcanvaspolygonalitem.html b/doc/html/qcanvaspolygonalitem.html index 213ffd47..a24b3024 100644 --- a/doc/html/qcanvaspolygonalitem.html +++ b/doc/html/qcanvaspolygonalitem.html @@ -79,7 +79,7 @@ handling, etc., which is much faster for non-rectangular items. <p> Derived classes should try to define as small an area as possible to maximize efficiency, but the polygon must <em>definitely</em> be contained completely within the polygonal area. Calculating the -exact retquirements is usually difficult, but if you allow a small +exact requirements is usually difficult, but if you allow a small overestimate it can be easy and tquick, while still getting almost all of TQCanvasPolygonalItem's speed. <p> Note that all subclasses <em>must</em> call <a href="qcanvasitem.html#hide">hide</a>() in their destructor diff --git a/doc/html/qcanvasspline.html b/doc/html/qcanvasspline.html index 40ec0666..3fafc390 100644 --- a/doc/html/qcanvasspline.html +++ b/doc/html/qcanvasspline.html @@ -101,11 +101,11 @@ Set the spline control points to <em>ctrl</em>. <p> If <em>close</em> is TRUE, then the first point in <em>ctrl</em> will be re-used as the last point, and the number of control points must be a multiple of 3. If <em>close</em> is FALSE, one additional control -point is retquired, and the number of control points must be one of +point is required, and the number of control points must be one of (4, 7, 10, 13, ...). <p> If the number of control points doesn't meet the above conditions, the number of points will be truncated to the largest number of -points that do meet the retquirement. +points that do meet the requirement. <p>Example: <a href="canvas-example.html#x2926">canvas/canvas.cpp</a>. <!-- eof --> diff --git a/doc/html/qcdestyle-h.html b/doc/html/qcdestyle-h.html index 5ad1dedb..0148ce80 100644 --- a/doc/html/qcdestyle-h.html +++ b/doc/html/qcdestyle-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qcheckbox-h.html b/doc/html/qcheckbox-h.html index 1044e650..109f3ee0 100644 --- a/doc/html/qcheckbox-h.html +++ b/doc/html/qcheckbox-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qclipboard-h.html b/doc/html/qclipboard-h.html index 6345160c..94ea7737 100644 --- a/doc/html/qclipboard-h.html +++ b/doc/html/qclipboard-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qcolor-h.html b/doc/html/qcolor-h.html index cb40dd6c..6759c8f9 100644 --- a/doc/html/qcolor-h.html +++ b/doc/html/qcolor-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qcolor.html b/doc/html/qcolor.html index 421cbde1..c296808a 100644 --- a/doc/html/qcolor.html +++ b/doc/html/qcolor.html @@ -262,7 +262,7 @@ don't need to call this function. <h3 class=fn>void <a name="cleanup"></a>TQColor::cleanup ()<tt> [static]</tt> </h3> -Internal clean up retquired for TQColor. +Internal clean up required for TQColor. This function is called from the <a href="qapplication.html">TQApplication</a> destructor. <p> <p>See also <a href="#initialize">initialize</a>(). @@ -390,7 +390,7 @@ Use <a href="#getHsv">getHsv</a>() instead. <p>Example: <a href="themes-example.html#x272">themes/metal.cpp</a>. <h3 class=fn>void <a name="initialize"></a>TQColor::initialize ()<tt> [static]</tt> </h3> -Internal initialization retquired for TQColor. +Internal initialization required for TQColor. This function is called from the <a href="qapplication.html">TQApplication</a> constructor. <p> <p>See also <a href="#cleanup">cleanup</a>(). diff --git a/doc/html/qcolordialog-h.html b/doc/html/qcolordialog-h.html index 89a80390..05366627 100644 --- a/doc/html/qcolordialog-h.html +++ b/doc/html/qcolordialog-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qcombobox-h.html b/doc/html/qcombobox-h.html index fcd4dd37..73f25bea 100644 --- a/doc/html/qcombobox-h.html +++ b/doc/html/qcombobox-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qcommonstyle-h.html b/doc/html/qcommonstyle-h.html index 34638c1c..1b1a0a6e 100644 --- a/doc/html/qcommonstyle-h.html +++ b/doc/html/qcommonstyle-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qcopchannel.html b/doc/html/qcopchannel.html index 44b9b660..4de884fb 100644 --- a/doc/html/qcopchannel.html +++ b/doc/html/qcopchannel.html @@ -122,7 +122,7 @@ This example assumes that the <em>msg</em> is a DCOP-style function signature and the <em>data</em> contains the function's arguments. (See <a href="#send">send</a>().) <p> Using the DCOP convention is a recommendation, but not a -retquirement. Whatever convention you use the sender and receiver +requirement. Whatever convention you use the sender and receiver <em>must</em> agree on the argument types. <p> <p>See also <a href="#send">send</a>(). @@ -154,7 +154,7 @@ functionname(types) where types is a list of zero or more comma-separated type names, with no whitespace, no consts and no pointer or reference marks, i.e. no "*" or "&". <p> Using the DCOP convention is a recommendation, but not a -retquirement. Whatever convention you use the sender and receiver +requirement. Whatever convention you use the sender and receiver <em>must</em> agree on the argument types. <p> <p>See also <a href="#receive">receive</a>(). diff --git a/doc/html/qcopchannel_qws-h.html b/doc/html/qcopchannel_qws-h.html index 00c0b316..e68bd7d9 100644 --- a/doc/html/qcopchannel_qws-h.html +++ b/doc/html/qcopchannel_qws-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qcstring-h.html b/doc/html/qcstring-h.html index 15756a83..0d0682d3 100644 --- a/doc/html/qcstring-h.html +++ b/doc/html/qcstring-h.html @@ -55,7 +55,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qcursor-h.html b/doc/html/qcursor-h.html index bbd490de..3adf6a19 100644 --- a/doc/html/qcursor-h.html +++ b/doc/html/qcursor-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qdatabrowser-h.html b/doc/html/qdatabrowser-h.html index 1d7ebede..cf110818 100644 --- a/doc/html/qdatabrowser-h.html +++ b/doc/html/qdatabrowser-h.html @@ -53,7 +53,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qdatastream-h.html b/doc/html/qdatastream-h.html index c2175e6a..c37ab7b1 100644 --- a/doc/html/qdatastream-h.html +++ b/doc/html/qdatastream-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qdatastream.html b/doc/html/qdatastream.html index 316e9351..7f710323 100644 --- a/doc/html/qdatastream.html +++ b/doc/html/qdatastream.html @@ -201,7 +201,7 @@ number to give yourself room for future expansion. For example: default setting is big endian (MSB first). Changing it to little endian breaks the portability (unless the reader also changes to little endian). We recommend keeping this setting unless you have -special retquirements. +special requirements. <p> <a name="raw"></a> <h3> Reading and writing raw binary data </h3> @@ -486,7 +486,7 @@ reference to the stream. Sets the serialization byte order to <em>bo</em>. <p> The <em>bo</em> parameter can be <a href="#ByteOrder-enum">TQDataStream::BigEndian</a> or <a href="#ByteOrder-enum">TQDataStream::LittleEndian</a>. <p> The default setting is big endian. We recommend leaving this -setting unless you have special retquirements. +setting unless you have special requirements. <p> <p>See also <a href="#byteOrder">byteOrder</a>(). <h3 class=fn>void <a name="setDevice"></a>TQDataStream::setDevice ( <a href="qiodevice.html">TQIODevice</a> * d ) diff --git a/doc/html/qdatatable-h.html b/doc/html/qdatatable-h.html index d47ae226..be5eb8b7 100644 --- a/doc/html/qdatatable-h.html +++ b/doc/html/qdatatable-h.html @@ -53,7 +53,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qdataview-h.html b/doc/html/qdataview-h.html index b4dea455..a4b604e1 100644 --- a/doc/html/qdataview-h.html +++ b/doc/html/qdataview-h.html @@ -53,7 +53,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qdatetime-h.html b/doc/html/qdatetime-h.html index 011f246e..44c382f5 100644 --- a/doc/html/qdatetime-h.html +++ b/doc/html/qdatetime-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qdatetimeedit-h.html b/doc/html/qdatetimeedit-h.html index 55eb0860..dc4d6efd 100644 --- a/doc/html/qdatetimeedit-h.html +++ b/doc/html/qdatetimeedit-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qdeepcopy-h.html b/doc/html/qdeepcopy-h.html index 7a31b6b1..a0248c39 100644 --- a/doc/html/qdeepcopy-h.html +++ b/doc/html/qdeepcopy-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qdesktopwidget-h.html b/doc/html/qdesktopwidget-h.html index a1ea27ef..72ae4975 100644 --- a/doc/html/qdesktopwidget-h.html +++ b/doc/html/qdesktopwidget-h.html @@ -52,7 +52,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qdial-h.html b/doc/html/qdial-h.html index 14693fb1..25a4374b 100644 --- a/doc/html/qdial-h.html +++ b/doc/html/qdial-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qdialog-h.html b/doc/html/qdialog-h.html index 1c4925d4..662001c0 100644 --- a/doc/html/qdialog-h.html +++ b/doc/html/qdialog-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qdialog.html b/doc/html/qdialog.html index 01945715..79f1c0dc 100644 --- a/doc/html/qdialog.html +++ b/doc/html/qdialog.html @@ -158,7 +158,7 @@ controlled with <a href="#setExtension">setExtension</a>(), <a href="#setOrienta <h3> Return value (modal dialogs) </h3> <a name="1-5"></a><p> Modal dialogs are often used in situations where a return value is -retquired, e.g. to indicate whether the user pressed "OK" or +required, e.g. to indicate whether the user pressed "OK" or "Cancel". A dialog can be closed by calling the <a href="#accept">accept</a>() or the <a href="#reject">reject</a>() slots, and <a href="#exec">exec</a>() will return <a href="#DialogCode-enum">Accepted</a> or <a href="#DialogCode-enum">Rejected</a> as appropriate. The exec() call returns the result of the dialog. diff --git a/doc/html/qdict-h.html b/doc/html/qdict-h.html index 3975ed2f..863f7f7f 100644 --- a/doc/html/qdict-h.html +++ b/doc/html/qdict-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qdir-h.html b/doc/html/qdir-h.html index 953cccf3..1213471a 100644 --- a/doc/html/qdir-h.html +++ b/doc/html/qdir-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qdirectpainter_qws-h.html b/doc/html/qdirectpainter_qws-h.html index dde44f48..31ff6628 100644 --- a/doc/html/qdirectpainter_qws-h.html +++ b/doc/html/qdirectpainter_qws-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qdns-h.html b/doc/html/qdns-h.html index 8f57d2bd..99c24e2f 100644 --- a/doc/html/qdns-h.html +++ b/doc/html/qdns-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qdockarea-h.html b/doc/html/qdockarea-h.html index 1beab2a5..ca976754 100644 --- a/doc/html/qdockarea-h.html +++ b/doc/html/qdockarea-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qdockwindow-h.html b/doc/html/qdockwindow-h.html index 31e3a6a1..f8ba5a47 100644 --- a/doc/html/qdockwindow-h.html +++ b/doc/html/qdockwindow-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qdockwindow.html b/doc/html/qdockwindow.html index a22281b0..59de4f32 100644 --- a/doc/html/qdockwindow.html +++ b/doc/html/qdockwindow.html @@ -443,7 +443,7 @@ proper behavior and even then TQDockWindow does not limit stretchablilty. <p>Set this property's value with <a href="#setMovingEnabled">setMovingEnabled</a>() and get this property's value with <a href="#isMovingEnabled">isMovingEnabled</a>(). <h3 class=fn>bool <a name="newLine-prop"></a>newLine</h3> <p>This property holds whether the dock window prefers to start a new line in the dock area. -<p>The default is FALSE, i.e. the dock window doesn't retquire a new +<p>The default is FALSE, i.e. the dock window doesn't require a new line in the dock area. <p>Set this property's value with <a href="#setNewLine">setNewLine</a>() and get this property's value with <a href="#newLine">newLine</a>(). diff --git a/doc/html/qdom-h.html b/doc/html/qdom-h.html index bdd2cb8e..4f4d0619 100644 --- a/doc/html/qdom-h.html +++ b/doc/html/qdom-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qdomdocument.html b/doc/html/qdomdocument.html index 6427a8c1..e236b109 100644 --- a/doc/html/qdomdocument.html +++ b/doc/html/qdomdocument.html @@ -392,7 +392,7 @@ will also change the other. If you want to make a <a href="shclass.html#deep-cop <h3 class=fn>bool <a name="setContent"></a>TQDomDocument::setContent ( const <a href="qbytearray.html">TQByteArray</a> & buffer, bool namespaceProcessing, <a href="qstring.html">TQString</a> * errorMsg = 0, int * errorLine = 0, int * errorColumn = 0 ) </h3> This function parses the XML document from the byte array <em>buffer</em> and sets it as the content of the document. It tries to -detect the encoding of the document as retquired by the XML +detect the encoding of the document as required by the XML specification. <p> If <em>namespaceProcessing</em> is TRUE, the parser recognizes namespaces in the XML file and sets the prefix name, local name diff --git a/doc/html/qdomnodelist.html b/doc/html/qdomnodelist.html index a3050b42..38c3104b 100644 --- a/doc/html/qdomnodelist.html +++ b/doc/html/qdomnodelist.html @@ -57,7 +57,7 @@ The TQDomNodeList class is a list of <a href="qdomnode.html">TQDomNode</a> objec <p> <p> Lists can be obtained by <a href="qdomdocument.html#elementsByTagName">TQDomDocument::elementsByTagName</a>() and -<a href="qdomnode.html#childNodes">TQDomNode::childNodes</a>(). The Document Object Model (DOM) retquires +<a href="qdomnode.html#childNodes">TQDomNode::childNodes</a>(). The Document Object Model (DOM) requires these lists to be "live": whenever you change the underlying document, the contents of the list will get updated. <p> You can get a particular node from the list with <a href="#item">item</a>(). The diff --git a/doc/html/qdragobject-h.html b/doc/html/qdragobject-h.html index 295ef4c3..7a868a27 100644 --- a/doc/html/qdragobject-h.html +++ b/doc/html/qdragobject-h.html @@ -52,7 +52,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qdrawutil-h.html b/doc/html/qdrawutil-h.html index 73d8d96d..a9a3f955 100644 --- a/doc/html/qdrawutil-h.html +++ b/doc/html/qdrawutil-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qdropsite-h.html b/doc/html/qdropsite-h.html index 43689c34..2c3e5112 100644 --- a/doc/html/qdropsite-h.html +++ b/doc/html/qdropsite-h.html @@ -52,7 +52,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qeditorfactory-h.html b/doc/html/qeditorfactory-h.html index 347e2eed..71d6469b 100644 --- a/doc/html/qeditorfactory-h.html +++ b/doc/html/qeditorfactory-h.html @@ -53,7 +53,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qerrormessage-h.html b/doc/html/qerrormessage-h.html index cc6d4f02..d466f018 100644 --- a/doc/html/qerrormessage-h.html +++ b/doc/html/qerrormessage-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qeucjpcodec-h.html b/doc/html/qeucjpcodec-h.html index 4f55c57e..3fb00617 100644 --- a/doc/html/qeucjpcodec-h.html +++ b/doc/html/qeucjpcodec-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qeuckrcodec-h.html b/doc/html/qeuckrcodec-h.html index fade5071..95e0011b 100644 --- a/doc/html/qeuckrcodec-h.html +++ b/doc/html/qeuckrcodec-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qevent-h.html b/doc/html/qevent-h.html index b700cf3d..2f0e57c7 100644 --- a/doc/html/qevent-h.html +++ b/doc/html/qevent-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qeventloop-h.html b/doc/html/qeventloop-h.html index b9383976..f0c15f05 100644 --- a/doc/html/qeventloop-h.html +++ b/doc/html/qeventloop-h.html @@ -52,7 +52,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qfile-h.html b/doc/html/qfile-h.html index 12a8b0de..b871d35a 100644 --- a/doc/html/qfile-h.html +++ b/doc/html/qfile-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qfiledialog-h.html b/doc/html/qfiledialog-h.html index 52fcf5b5..f44db2e8 100644 --- a/doc/html/qfiledialog-h.html +++ b/doc/html/qfiledialog-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qfiledialog.html b/doc/html/qfiledialog.html index c9bb992c..2f624f2a 100644 --- a/doc/html/qfiledialog.html +++ b/doc/html/qfiledialog.html @@ -379,7 +379,7 @@ to the bottom of the file dialog. </h3> Returns the current directory shown in the file dialog. <p> The ownership of the <a href="qdir.html">TQDir</a> pointer is transferred to the caller, so -it must be deleted by the caller when no longer retquired. +it must be deleted by the caller when no longer required. <p> <p>See also <a href="#setDir">setDir</a>(). <h3 class=fn>void <a name="dirEntered"></a>TQFileDialog::dirEntered ( const <a href="qstring.html">TQString</a> & )<tt> [signal]</tt> diff --git a/doc/html/qfileinfo-h.html b/doc/html/qfileinfo-h.html index 43f65f73..2077d6da 100644 --- a/doc/html/qfileinfo-h.html +++ b/doc/html/qfileinfo-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qfocusdata-h.html b/doc/html/qfocusdata-h.html index 4296e082..c900dc19 100644 --- a/doc/html/qfocusdata-h.html +++ b/doc/html/qfocusdata-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qfont-h.html b/doc/html/qfont-h.html index af4c5a1e..00d34475 100644 --- a/doc/html/qfont-h.html +++ b/doc/html/qfont-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qfont.html b/doc/html/qfont.html index c410d5c9..3f60643f 100644 --- a/doc/html/qfont.html +++ b/doc/html/qfont.html @@ -642,7 +642,7 @@ Saves the glyphs in the font that have previously been accessed as a TQPF file. If <em>all</em> is TRUE (the default), then before saving, all glyphs are marked as used. <p> If the font is large and you are sure that only a subset of -characters will ever be retquired on the target device, passing +characters will ever be required on the target device, passing FALSE for the <em>all</em> parameter can save a significant amount of disk space. <p> Note that this function is only applicable on TQt/Embedded. diff --git a/doc/html/qfontdatabase-h.html b/doc/html/qfontdatabase-h.html index a0e67731..cc2bbd06 100644 --- a/doc/html/qfontdatabase-h.html +++ b/doc/html/qfontdatabase-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qfontdialog-h.html b/doc/html/qfontdialog-h.html index bdc2c340..cc934c43 100644 --- a/doc/html/qfontdialog-h.html +++ b/doc/html/qfontdialog-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qfontinfo-h.html b/doc/html/qfontinfo-h.html index 4489ea9e..e16a52df 100644 --- a/doc/html/qfontinfo-h.html +++ b/doc/html/qfontinfo-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qfontmanager_qws-h.html b/doc/html/qfontmanager_qws-h.html index 0b102e67..05ee1cb0 100644 --- a/doc/html/qfontmanager_qws-h.html +++ b/doc/html/qfontmanager_qws-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qfontmetrics-h.html b/doc/html/qfontmetrics-h.html index 78ee858d..b173fbae 100644 --- a/doc/html/qfontmetrics-h.html +++ b/doc/html/qfontmetrics-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qframe-h.html b/doc/html/qframe-h.html index 3edc3110..01c1161a 100644 --- a/doc/html/qframe-h.html +++ b/doc/html/qframe-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qftp-h.html b/doc/html/qftp-h.html index b1aa13fa..39d08fe0 100644 --- a/doc/html/qftp-h.html +++ b/doc/html/qftp-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qgb18030codec-h.html b/doc/html/qgb18030codec-h.html index 635e2458..c46d0f0a 100644 --- a/doc/html/qgb18030codec-h.html +++ b/doc/html/qgb18030codec-h.html @@ -52,7 +52,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qgfx_qws-h.html b/doc/html/qgfx_qws-h.html index 4551ca62..68bcb4b3 100644 --- a/doc/html/qgfx_qws-h.html +++ b/doc/html/qgfx_qws-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qgfxdriverfactory_qws-h.html b/doc/html/qgfxdriverfactory_qws-h.html index 66f2e1a7..b54dcec2 100644 --- a/doc/html/qgfxdriverfactory_qws-h.html +++ b/doc/html/qgfxdriverfactory_qws-h.html @@ -52,7 +52,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qgfxdriverplugin_qws-h.html b/doc/html/qgfxdriverplugin_qws-h.html index 9c3db4f4..46078e67 100644 --- a/doc/html/qgfxdriverplugin_qws-h.html +++ b/doc/html/qgfxdriverplugin_qws-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qgl-h.html b/doc/html/qgl-h.html index 2459aab6..86ba13ce 100644 --- a/doc/html/qgl-h.html +++ b/doc/html/qgl-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qglcolormap-h.html b/doc/html/qglcolormap-h.html index dde9d0af..81fa6299 100644 --- a/doc/html/qglcolormap-h.html +++ b/doc/html/qglcolormap-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qglcontext.html b/doc/html/qglcontext.html index 8f0ab6bf..215ef3d6 100644 --- a/doc/html/qglcontext.html +++ b/doc/html/qglcontext.html @@ -137,7 +137,7 @@ visual that matches the format using the given <em>device</em> handle, reducing the demands if the original request cannot be met. <p> The algorithm for reducing the demands of the format is quite simple-minded, so override this method in your subclass if your -application has specific retquirements on visual selection. +application has specific requirements on visual selection. <p> <p>See also <a href="#chooseContext">chooseContext</a>(). <h3 class=fn>int <a name="choosePixelFormat"></a>TQGLContext::choosePixelFormat ( void * dummyPfd, HDC pdc )<tt> [virtual protected]</tt> @@ -157,7 +157,7 @@ visual that matches the format, reducing the demands if the original request cannot be met. <p> The algorithm for reducing the demands of the format is quite simple-minded, so override this method in your subclass if your -application has spcific retquirements on visual selection. +application has spcific requirements on visual selection. <p> <p>See also <a href="#chooseContext">chooseContext</a>(). <h3 class=fn>bool <a name="create"></a>TQGLContext::create ( const <a href="qglcontext.html">TQGLContext</a> * shareContext = 0 )<tt> [virtual]</tt> diff --git a/doc/html/qglformat.html b/doc/html/qglformat.html index 76ebe9c3..4eb3057e 100644 --- a/doc/html/qglformat.html +++ b/doc/html/qglformat.html @@ -131,7 +131,7 @@ requested features the system was able to provide: if ( !w->format().stereo() ) { // ok, goggles off if ( !w->format().hasOverlay() ) { - <a href="qapplication.html#qFatal">qFatal</a>( "Cool hardware retquired" ); + <a href="qapplication.html#qFatal">qFatal</a>( "Cool hardware required" ); } } </pre> diff --git a/doc/html/qglobal-h.html b/doc/html/qglobal-h.html index 1d5932b8..285a4d9b 100644 --- a/doc/html/qglobal-h.html +++ b/doc/html/qglobal-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -601,7 +601,7 @@ body { background: #ffffff; color: black; } # define Q_WS_MAC9 #elif defined(Q_OS_MSDOS) # define Q_WS_WIN16 -# error "TQt retquires Win32 and does not work with Windows 3.x" +# error "TQt requires Win32 and does not work with Windows 3.x" #elif defined(_WIN32_X11_) # define Q_WS_X11 #elif defined(Q_OS_WIN32) @@ -1116,7 +1116,7 @@ Q_EXPORT const char *qInstallPathSysconf(); /* compilers which follow outdated template instantiation rules - retquire a class to have a comparison operator to exist when + require a class to have a comparison operator to exist when a TQValueList of this type is instantiated. It's not actually used in the list, though. Hence the dummy implementation. Just in case other code relies on it we better trigger a warning diff --git a/doc/html/qglwidget.html b/doc/html/qglwidget.html index a9fa0e7e..694f7182 100644 --- a/doc/html/qglwidget.html +++ b/doc/html/qglwidget.html @@ -356,7 +356,7 @@ function. This virtual function is called once before the first call to <a href="#paintGL">paintGL</a>() or <a href="#resizeGL">resizeGL</a>(), and then once whenever the widget has been assigned a new <a href="qglcontext.html">TQGLContext</a>. Reimplement it in a subclass. -<p> This function should set up any retquired OpenGL context rendering +<p> This function should set up any required OpenGL context rendering flags, defining display lists, etc. <p> There is no need to call <a href="#makeCurrent">makeCurrent</a>() because this has already been done when this function is called. @@ -368,7 +368,7 @@ except that it operates on the widget's overlay context instead of the widget's main context. This means that <a href="#initializeOverlayGL">initializeOverlayGL</a>() is called once before the first call to <a href="#paintOverlayGL">paintOverlayGL</a>() or <a href="#resizeOverlayGL">resizeOverlayGL</a>(). Reimplement it in a subclass. -<p> This function should set up any retquired OpenGL context rendering +<p> This function should set up any required OpenGL context rendering flags, defining display lists, etc. for the overlay context. <p> There is no need to call <a href="#makeOverlayCurrent">makeOverlayCurrent</a>() because this has already been done when this function is called. diff --git a/doc/html/qgrid-h.html b/doc/html/qgrid-h.html index 3f9bf0d7..31316c95 100644 --- a/doc/html/qgrid-h.html +++ b/doc/html/qgrid-h.html @@ -50,7 +50,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qgridview-h.html b/doc/html/qgridview-h.html index 0d699493..68921e88 100644 --- a/doc/html/qgridview-h.html +++ b/doc/html/qgridview-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qgroupbox-h.html b/doc/html/qgroupbox-h.html index a943c0e6..1584eb2e 100644 --- a/doc/html/qgroupbox-h.html +++ b/doc/html/qgroupbox-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qguardedptr-h.html b/doc/html/qguardedptr-h.html index 311a16e3..d3588910 100644 --- a/doc/html/qguardedptr-h.html +++ b/doc/html/qguardedptr-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qguardedptr.html b/doc/html/qguardedptr.html index b62e9586..4b5ebed3 100644 --- a/doc/html/qguardedptr.html +++ b/doc/html/qguardedptr.html @@ -93,7 +93,7 @@ them using either the <tt>*x</tt> or the <tt>x->member</tt> notation. <p> A guarded pointer will automatically cast to an X*, so you can freely mix guarded and unguarded pointers. This means that if you have a TQGuardedPtr<TQWidget>, you can pass it to a function that -retquires a <a href="qwidget.html">TQWidget</a>*. For this reason, it is of little value to +requires a <a href="qwidget.html">TQWidget</a>*. For this reason, it is of little value to declare functions to take a TQGuardedPtr as a parameter; just use normal pointers. Use a TQGuardedPtr when you are storing a pointer over time. @@ -139,7 +139,7 @@ there is no referenced object; otherwise returns FALSE. <p> Cast operator; implements pointer semantics. Because of this function you can pass a TQGuardedPtr<X> to a function where an X* -is retquired. +is required. <h3 class=fn>bool <a name="operator!-eq"></a>TQGuardedPtr::operator!= ( const <a href="qguardedptr.html">TQGuardedPtr</a><T> & p ) const </h3> diff --git a/doc/html/qhbox-h.html b/doc/html/qhbox-h.html index 0fde00b4..f83b4ddb 100644 --- a/doc/html/qhbox-h.html +++ b/doc/html/qhbox-h.html @@ -50,7 +50,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qhbuttongroup-h.html b/doc/html/qhbuttongroup-h.html index 863c7cb0..e79ed3de 100644 --- a/doc/html/qhbuttongroup-h.html +++ b/doc/html/qhbuttongroup-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qheader-h.html b/doc/html/qheader-h.html index f6cb9137..3fecd36e 100644 --- a/doc/html/qheader-h.html +++ b/doc/html/qheader-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qhgroupbox-h.html b/doc/html/qhgroupbox-h.html index e05cf2a0..01db686a 100644 --- a/doc/html/qhgroupbox-h.html +++ b/doc/html/qhgroupbox-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qhostaddress-h.html b/doc/html/qhostaddress-h.html index 97788675..ffbed3a3 100644 --- a/doc/html/qhostaddress-h.html +++ b/doc/html/qhostaddress-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qhttp-h.html b/doc/html/qhttp-h.html index e25d9527..3bb8b34a 100644 --- a/doc/html/qhttp-h.html +++ b/doc/html/qhttp-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qhttp.html b/doc/html/qhttp.html index 9d830fc9..3d20edba 100644 --- a/doc/html/qhttp.html +++ b/doc/html/qhttp.html @@ -309,7 +309,7 @@ connection and want to close it. <p> For the requests issued with <a href="#get">get</a>(), <a href="#post">post</a>() and <a href="#head">head</a>(), TQHttp sets the connection to be keep-alive. You can also do this using the header you pass to the <a href="#request">request</a>() function. TQHttp only closes the -connection to the HTTP server if the response header retquires it +connection to the HTTP server if the response header requires it to do so. <p> The function does not block and returns immediately. The request is scheduled, and its execution is performed asynchronously. The diff --git a/doc/html/qiconset-h.html b/doc/html/qiconset-h.html index 6fb45c52..c28ed7ac 100644 --- a/doc/html/qiconset-h.html +++ b/doc/html/qiconset-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qiconset.html b/doc/html/qiconset.html index 2389f062..63a11a44 100644 --- a/doc/html/qiconset.html +++ b/doc/html/qiconset.html @@ -77,7 +77,7 @@ from the set of icons it is given. Such pixmaps are used by <a href="qtoolbutton.html">TQToolButton</a>, <a href="qheader.html">TQHeader</a>, <a href="qpopupmenu.html">TQPopupMenu</a>, etc. to show an icon representing a particular action. <p> The simplest use of TQIconSet is to create one from a <a href="qpixmap.html">TQPixmap</a> and then -use it, allowing TQt to work out all the retquired icon styles and +use it, allowing TQt to work out all the required icon styles and sizes. For example: <p> <pre> <a href="qtoolbutton.html">TQToolButton</a> *but = new <a href="qtoolbutton.html">TQToolButton</a>( <a href="#TQIconSet">TQIconSet</a>( TQPixmap("open.xpm") ), ... ); @@ -174,7 +174,7 @@ pixel size. This is a useful default. <li><tt>TQIconSet::Large</tt> - The pixmap is the larger of two. </ul><p> If a Small pixmap is not set by <a href="#setPixmap">TQIconSet::setPixmap</a>(), the Large pixmap will be automatically scaled down to the size of a small pixmap -to generate the Small pixmap when retquired. Similarly, a Small pixmap +to generate the Small pixmap when required. Similarly, a Small pixmap will be automatically scaled up to generate a Large pixmap. The preferred sizes for large/small generated icons can be set using <a href="#setIconSize">setIconSize</a>(). diff --git a/doc/html/qiconview-h.html b/doc/html/qiconview-h.html index 5dc5eb20..bf10e5dc 100644 --- a/doc/html/qiconview-h.html +++ b/doc/html/qiconview-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qimage-h.html b/doc/html/qimage-h.html index 0892e74d..adb34b33 100644 --- a/doc/html/qimage-h.html +++ b/doc/html/qimage-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qimage.html b/doc/html/qimage.html index a050b5b3..1624d7a3 100644 --- a/doc/html/qimage.html +++ b/doc/html/qimage.html @@ -242,7 +242,7 @@ operations that are independent of endianness. <p> The functions <a href="#scale">scale</a>() and <a href="#smoothScale">smoothScale</a>() use different modes for scaling the image. The purpose of these modes is to retain the -ratio of the image if this is retquired. +ratio of the image if this is required. <p> <center><img src="scaling.png"></center> <ul> <li><tt>TQImage::ScaleFree</tt> - The image is scaled freely: the resulting image diff --git a/doc/html/qimagedecoder.html b/doc/html/qimagedecoder.html index b52c490d..25dff373 100644 --- a/doc/html/qimagedecoder.html +++ b/doc/html/qimagedecoder.html @@ -70,13 +70,13 @@ currently-existing TQImageFormatType factory objects. need to implement support for additional image formats. <p> <p> TQt supports GIF reading if it is configured that way during -installation (see qgif.h). If it is, we are retquired to state that +installation (see qgif.h). If it is, 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." <p> <b>Warning:</b> 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 retquire you to +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. <p> GIF support may be removed completely in a future version of TQt. diff --git a/doc/html/qimageformatplugin-h.html b/doc/html/qimageformatplugin-h.html index 9b4ce8bb..c0b8e08d 100644 --- a/doc/html/qimageformatplugin-h.html +++ b/doc/html/qimageformatplugin-h.html @@ -52,7 +52,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qimageio.html b/doc/html/qimageio.html index 52e2ad68..adae5443 100644 --- a/doc/html/qimageio.html +++ b/doc/html/qimageio.html @@ -95,7 +95,7 @@ raw format. PPM and PGM files with more than 256 levels of intensity are scaled down when reading. <p> <b>Warning:</b> If you are in a country which recognizes software patents and in which Unisys holds a patent on LZW compression and/or -decompression and you want to use GIF, Unisys may retquire you to +decompression and you want to use GIF, Unisys may require you to license the technology. Such countries include Canada, Japan, the USA, France, Germany, Italy and the UK. <p> GIF support may be removed completely in a future version of TQt. @@ -309,7 +309,7 @@ Sets the image to <em>image</em>. <h3 class=fn>void <a name="setParameters"></a>TQImageIO::setParameters ( const char * parameters ) </h3> Sets the image's parameter string to <em>parameters</em>. This is for -image handlers that retquire special parameters. +image handlers that require special parameters. <p> 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). diff --git a/doc/html/qinputdialog-h.html b/doc/html/qinputdialog-h.html index 03829cfc..91cddced 100644 --- a/doc/html/qinputdialog-h.html +++ b/doc/html/qinputdialog-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qintcache-h.html b/doc/html/qintcache-h.html index 8f041560..82ad55b3 100644 --- a/doc/html/qintcache-h.html +++ b/doc/html/qintcache-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qintdict-h.html b/doc/html/qintdict-h.html index ef63a2b2..744a1412 100644 --- a/doc/html/qintdict-h.html +++ b/doc/html/qintdict-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qiodevice-h.html b/doc/html/qiodevice-h.html index dbeb2a43..249fa9fe 100644 --- a/doc/html/qiodevice-h.html +++ b/doc/html/qiodevice-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qjiscodec-h.html b/doc/html/qjiscodec-h.html index 1a5ec0c7..2265e91c 100644 --- a/doc/html/qjiscodec-h.html +++ b/doc/html/qjiscodec-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qkbddriverfactory_qws-h.html b/doc/html/qkbddriverfactory_qws-h.html index 9ad15141..d5e05088 100644 --- a/doc/html/qkbddriverfactory_qws-h.html +++ b/doc/html/qkbddriverfactory_qws-h.html @@ -52,7 +52,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qkbddriverplugin_qws-h.html b/doc/html/qkbddriverplugin_qws-h.html index 326192a6..1956d140 100644 --- a/doc/html/qkbddriverplugin_qws-h.html +++ b/doc/html/qkbddriverplugin_qws-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qkeyboard_qws-h.html b/doc/html/qkeyboard_qws-h.html index bd3a38e9..19a11c97 100644 --- a/doc/html/qkeyboard_qws-h.html +++ b/doc/html/qkeyboard_qws-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qkeysequence-h.html b/doc/html/qkeysequence-h.html index e2df6fc5..51a38a82 100644 --- a/doc/html/qkeysequence-h.html +++ b/doc/html/qkeysequence-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qlabel-h.html b/doc/html/qlabel-h.html index 9ec87949..cec59f69 100644 --- a/doc/html/qlabel-h.html +++ b/doc/html/qlabel-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qlayout-h.html b/doc/html/qlayout-h.html index 94a65108..b00bc82c 100644 --- a/doc/html/qlayout-h.html +++ b/doc/html/qlayout-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qlcdnumber-h.html b/doc/html/qlcdnumber-h.html index d04b6dbb..c003ff87 100644 --- a/doc/html/qlcdnumber-h.html +++ b/doc/html/qlcdnumber-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qlibrary-h.html b/doc/html/qlibrary-h.html index c85c12c3..1dace16f 100644 --- a/doc/html/qlibrary-h.html +++ b/doc/html/qlibrary-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qlibrary.html b/doc/html/qlibrary.html index be75bd85..526e250f 100644 --- a/doc/html/qlibrary.html +++ b/doc/html/qlibrary.html @@ -194,7 +194,7 @@ not be resolved or the library could not be loaded. </pre> <p> The symbol must be exported as a C-function from the library. This -retquires the <tt>extern "C"</tt> notation if the library is compiled +requires the <tt>extern "C"</tt> notation if the library is compiled with a C++ compiler. On Windows you also have to explicitly export the function from the DLL using the <tt>__declspec(dllexport)</tt> compiler directive. diff --git a/doc/html/qlineedit-h.html b/doc/html/qlineedit-h.html index fe6743c9..88d4d6ac 100644 --- a/doc/html/qlineedit-h.html +++ b/doc/html/qlineedit-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qlineedit.html b/doc/html/qlineedit.html index cb7840ed..3542564f 100644 --- a/doc/html/qlineedit.html +++ b/doc/html/qlineedit.html @@ -659,17 +659,17 @@ arguments. <p> The mask format understands these mask characters: <center><table cellpadding="4" cellspacing="2" border="0"> <tr bgcolor="#a2c511"> <th valign="top">Character <th valign="top">Meaning -<tr bgcolor="#f0f0f0"> <td valign="top"><tt>A</tt> <td valign="top">ASCII alphabetic character retquired. A-Z, a-z. -<tr bgcolor="#d0d0d0"> <td valign="top"><tt>a</tt> <td valign="top">ASCII alphabetic character permitted but not retquired. -<tr bgcolor="#f0f0f0"> <td valign="top"><tt>N</tt> <td valign="top">ASCII alphanumeric character retquired. A-Z, a-z, 0-9. -<tr bgcolor="#d0d0d0"> <td valign="top"><tt>n</tt> <td valign="top">ASCII alphanumeric character permitted but not retquired. -<tr bgcolor="#f0f0f0"> <td valign="top"><tt>X</tt> <td valign="top">Any character retquired. -<tr bgcolor="#d0d0d0"> <td valign="top"><a href="qwidget.html#x-prop">x</a> <td valign="top">Any character permitted but not retquired. -<tr bgcolor="#f0f0f0"> <td valign="top"><tt>9</tt> <td valign="top">ASCII digit retquired. 0-9. -<tr bgcolor="#d0d0d0"> <td valign="top"><tt>0</tt> <td valign="top">ASCII digit permitted but not retquired. -<tr bgcolor="#f0f0f0"> <td valign="top"><tt>D</tt> <td valign="top">ASCII digit retquired. 1-9. -<tr bgcolor="#d0d0d0"> <td valign="top"><tt>d</tt> <td valign="top">ASCII digit permitted but not retquired (1-9). -<tr bgcolor="#f0f0f0"> <td valign="top"><tt>#</tt> <td valign="top">ASCII digit or plus/minus sign permitted but not retquired. +<tr bgcolor="#f0f0f0"> <td valign="top"><tt>A</tt> <td valign="top">ASCII alphabetic character required. A-Z, a-z. +<tr bgcolor="#d0d0d0"> <td valign="top"><tt>a</tt> <td valign="top">ASCII alphabetic character permitted but not required. +<tr bgcolor="#f0f0f0"> <td valign="top"><tt>N</tt> <td valign="top">ASCII alphanumeric character required. A-Z, a-z, 0-9. +<tr bgcolor="#d0d0d0"> <td valign="top"><tt>n</tt> <td valign="top">ASCII alphanumeric character permitted but not required. +<tr bgcolor="#f0f0f0"> <td valign="top"><tt>X</tt> <td valign="top">Any character required. +<tr bgcolor="#d0d0d0"> <td valign="top"><a href="qwidget.html#x-prop">x</a> <td valign="top">Any character permitted but not required. +<tr bgcolor="#f0f0f0"> <td valign="top"><tt>9</tt> <td valign="top">ASCII digit required. 0-9. +<tr bgcolor="#d0d0d0"> <td valign="top"><tt>0</tt> <td valign="top">ASCII digit permitted but not required. +<tr bgcolor="#f0f0f0"> <td valign="top"><tt>D</tt> <td valign="top">ASCII digit required. 1-9. +<tr bgcolor="#d0d0d0"> <td valign="top"><tt>d</tt> <td valign="top">ASCII digit permitted but not required (1-9). +<tr bgcolor="#f0f0f0"> <td valign="top"><tt>#</tt> <td valign="top">ASCII digit or plus/minus sign permitted but not required. <tr bgcolor="#d0d0d0"> <td valign="top"><tt>></tt> <td valign="top">All following alphabetic characters are uppercased. <tr bgcolor="#f0f0f0"> <td valign="top"><tt><</tt> <td valign="top">All following alphabetic characters are lowercased. <tr bgcolor="#d0d0d0"> <td valign="top"><tt>!</tt> <td valign="top">Switch off case conversion. diff --git a/doc/html/qlistbox-h.html b/doc/html/qlistbox-h.html index 744d273f..1e1d6eaf 100644 --- a/doc/html/qlistbox-h.html +++ b/doc/html/qlistbox-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qlistbox.html b/doc/html/qlistbox.html index 7b4ff52f..7c7650f0 100644 --- a/doc/html/qlistbox.html +++ b/doc/html/qlistbox.html @@ -204,7 +204,7 @@ functions both to set the selection state of an item, i.e. <a href="#setSelected">setSelected</a>(), and to set which item displays keyboard focus, i.e. <a href="#setCurrentItem">setCurrentItem</a>(). <p> The list box normally arranges its items in a single column and -adds a vertical scroll bar if retquired. It is possible to have a +adds a vertical scroll bar if required. It is possible to have a different fixed number of columns (<a href="#setColumnMode">setColumnMode</a>()), or as many columns as will fit in the list box's assigned screen space (setColumnMode(FitToWidth)), or to have a fixed number of rows @@ -275,8 +275,8 @@ and columns. <li><tt>TQListBox::FitToWidth</tt> - There are as many columns as will fit on-screen. <li><tt>TQListBox::FitToHeight</tt> - There are as many rows as will fit on-screen. -<li><tt>TQListBox::Variable</tt> - There are as many rows as are retquired by the -column mode. (Or as many columns as retquired by the row mode.) +<li><tt>TQListBox::Variable</tt> - There are as many rows as are required by the +column mode. (Or as many columns as required by the row mode.) </ul><p> Example: When you call <a href="#setRowMode">setRowMode</a>( FitToHeight ), <a href="#columnMode">columnMode</a>() automatically becomes <a href="#LayoutMode-enum">Variable</a> to accommodate the row mode you've set. diff --git a/doc/html/qlistview-h.html b/doc/html/qlistview-h.html index c5d0b544..b760cc67 100644 --- a/doc/html/qlistview-h.html +++ b/doc/html/qlistview-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qlistview.html b/doc/html/qlistview.html index 35e7d359..b95403ab 100644 --- a/doc/html/qlistview.html +++ b/doc/html/qlistview.html @@ -601,7 +601,7 @@ create a <a href="qdragobject.html">TQDragObject</a> depending on the selected i </h3> Calls <a href="qlistviewitem.html#paintCell">TQListViewItem::paintCell</a>() and <a href="qlistviewitem.html#paintBranches">TQListViewItem::paintBranches</a>() as necessary for all list view -items that retquire repainting in the <em>cw</em> pixels wide and <em>ch</em> +items that require repainting in the <em>cw</em> pixels wide and <em>ch</em> pixels high bounding rectangle starting at position <em>cx</em>, <em>cy</em> with offset <em>ox</em>, <em>oy</em>. Uses the painter <em>p</em>. @@ -617,7 +617,7 @@ viewport (not onto an item). </h3> Ensures that item <em>i</em> is visible, scrolling the list view vertically if necessary and opening (expanding) any parent items -if this is retquired to show the item. +if this is required to show the item. <p> <p>See also <a href="#itemRect">itemRect</a>() and <a href="qscrollview.html#ensureVisible">TQScrollView::ensureVisible</a>(). <h3 class=fn>bool <a name="eventFilter"></a>TQListView::eventFilter ( <a href="qobject.html">TQObject</a> * o, <a href="qevent.html">TQEvent</a> * e )<tt> [virtual]</tt> diff --git a/doc/html/qlistviewitem.html b/doc/html/qlistviewitem.html index ff41f292..ca3eec1a 100644 --- a/doc/html/qlistviewitem.html +++ b/doc/html/qlistviewitem.html @@ -779,7 +779,7 @@ height. <h3 class=fn>int <a name="width"></a>TQListViewItem::width ( const <a href="qfontmetrics.html">TQFontMetrics</a> & fm, const <a href="qlistview.html">TQListView</a> * lv, int c ) const<tt> [virtual]</tt> </h3> -Returns the number of pixels of width retquired to draw column <em>c</em> +Returns the number of pixels of width required to draw column <em>c</em> of list view <em>lv</em>, using the metrics <em>fm</em> without cropping. The list view containing this item may use this information depending on the TQListView::WidthMode settings for the column. diff --git a/doc/html/qlocale-h.html b/doc/html/qlocale-h.html index 2ab807e2..5c468161 100644 --- a/doc/html/qlocale-h.html +++ b/doc/html/qlocale-h.html @@ -52,7 +52,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qlocalfs-h.html b/doc/html/qlocalfs-h.html index 49680ab0..577a5916 100644 --- a/doc/html/qlocalfs-h.html +++ b/doc/html/qlocalfs-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qmacstyle_mac-h.html b/doc/html/qmacstyle_mac-h.html index 02f33eda..9623fba5 100644 --- a/doc/html/qmacstyle_mac-h.html +++ b/doc/html/qmacstyle_mac-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qmainwindow-h.html b/doc/html/qmainwindow-h.html index f2c72d01..4f9e5299 100644 --- a/doc/html/qmainwindow-h.html +++ b/doc/html/qmainwindow-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qmainwindow.html b/doc/html/qmainwindow.html index e298dcfb..3d43bb55 100644 --- a/doc/html/qmainwindow.html +++ b/doc/html/qmainwindow.html @@ -282,7 +282,7 @@ right clicking a dock area and clicking the name of the relevant dock window on the pop up dock window menu. This menu lists the names of every dock window; visible dock windows have a tick beside their names. The dock window menu is created automatically -as retquired by <a href="#createDockWindowMenu">createDockWindowMenu</a>(). Since it may not always be +as required by <a href="#createDockWindowMenu">createDockWindowMenu</a>(). Since it may not always be appropriate for a dock window to appear on this menu the <a href="#setAppropriate">setAppropriate</a>() function is used to inform the main window whether or not the dock window menu should include a particular diff --git a/doc/html/qmake-manual-1.html b/doc/html/qmake-manual-1.html index ce413523..be0ec6bf 100644 --- a/doc/html/qmake-manual-1.html +++ b/doc/html/qmake-manual-1.html @@ -33,8 +33,8 @@ body { background: #ffffff; color: black; } <h2 align="center">Introduction to qmake</h2> <h3><a name="1"></a>Introduction to qmake</h3> <p><em>qmake</em> is a tool created by Trolltech to write makefiles for different compilers and platforms.</p> -<p>Writing makefiles by hand can be difficult and error prone, especially if several makefiles are retquired for different compiler and platform combinations. With <em>qmake</em>, developers create a simple single 'project' file and run <em>qmake</em> to generate the appropriate makefiles. <em>qmake</em> takes care of all the compiler and platform dependencies, freeing developers to focus on their code. Trolltech uses <em>qmake</em> as the primary build tool for the TQt library, and for the tools supplied with TQt.</p> -<p><em>qmake</em> also takes care of TQt's special retquirements, automatically including build rules for <a href="moc.html">moc</a> and <em>uic</em>.</p> +<p>Writing makefiles by hand can be difficult and error prone, especially if several makefiles are required for different compiler and platform combinations. With <em>qmake</em>, developers create a simple single 'project' file and run <em>qmake</em> to generate the appropriate makefiles. <em>qmake</em> takes care of all the compiler and platform dependencies, freeing developers to focus on their code. Trolltech uses <em>qmake</em> as the primary build tool for the TQt library, and for the tools supplied with TQt.</p> +<p><em>qmake</em> also takes care of TQt's special requirements, automatically including build rules for <a href="moc.html">moc</a> and <em>uic</em>.</p> <!-- eof --> <p align="right">[<a href="qmake-manual.html">Home</a>] [<a href="qmake-manual-2.html">Next: Installing qmake</a>]</p> <p><address><hr><div align=center> diff --git a/doc/html/qmake-manual-3.html b/doc/html/qmake-manual-3.html index fcbc8221..4247a526 100644 --- a/doc/html/qmake-manual-3.html +++ b/doc/html/qmake-manual-3.html @@ -44,7 +44,7 @@ body { background: #ffffff; color: black; } <pre> SOURCES = hello.cpp </pre> -<p>This line specifies the source files that implement the application. In this case there is just one file, <em>hello.cpp</em>. Most applications retquire multiple files; this situation is dealt with by listing all the files on the same line space separated, like this:</p> +<p>This line specifies the source files that implement the application. In this case there is just one file, <em>hello.cpp</em>. Most applications require multiple files; this situation is dealt with by listing all the files on the same line space separated, like this:</p> <pre> SOURCES = hello.cpp main.cpp </pre> diff --git a/doc/html/qmake-manual-4.html b/doc/html/qmake-manual-4.html index 8f656715..990d6050 100644 --- a/doc/html/qmake-manual-4.html +++ b/doc/html/qmake-manual-4.html @@ -135,7 +135,7 @@ body { background: #ffffff; color: black; } </pre> <p>Use <em>qmake</em> as before to generate a makefile. If you rename <em>main.cpp</em> temporarily, you will see the message and <em>qmake</em> will stop processing.</p> <h3><a name="6"></a>Checking for more than one condition</h3> -<p>Suppose you use Windows and you want to be able to see the qDebug() statements when you run your application on the command line. Unless you build your application with the console setting, you won't see the output. We can easily put <em>console</em> on the CONFIG line so that on Windows the makefile will have this setting. But let's say that we only want to add the CONFIG line if we are running on Windows <em>and</em> when <em>debug</em> is already on the CONFIG line. This retquires using two nested scopes; just create one scope, then create the other inside that one. Put the settings to be processed inside the last scope, like this:</p> +<p>Suppose you use Windows and you want to be able to see the qDebug() statements when you run your application on the command line. Unless you build your application with the console setting, you won't see the output. We can easily put <em>console</em> on the CONFIG line so that on Windows the makefile will have this setting. But let's say that we only want to add the CONFIG line if we are running on Windows <em>and</em> when <em>debug</em> is already on the CONFIG line. This requires using two nested scopes; just create one scope, then create the other inside that one. Put the settings to be processed inside the last scope, like this:</p> <pre> win32 { debug { diff --git a/doc/html/qmake-manual-5.html b/doc/html/qmake-manual-5.html index e1912340..ed3b9cfb 100644 --- a/doc/html/qmake-manual-5.html +++ b/doc/html/qmake-manual-5.html @@ -33,7 +33,7 @@ body { background: #ffffff; color: black; } <h2 align="center">qmake Concepts</h2> <h3><a name="1"></a>Introducing qmake</h3> <p><em>qmake</em> is an easy-to-use tool from Trolltech that creates makefiles for development projects across different platforms. <em>qmake</em> simplifies the generation of makefiles so that only a few lines of information are needed to create a makefile. <em>qmake</em> can be used for any software project whether it is written in TQt or not, although it also contains additional features to support TQt development.</p> -<p><em>qmake</em> generates a makefile based on the information in a project file. Project files are created by the developer. Project files are usually simple, but can be quite sophisticated if retquired. <em>qmake</em> can also generate projects for Microsoft Visual studio without having to change the project file.</p> +<p><em>qmake</em> generates a makefile based on the information in a project file. Project files are created by the developer. Project files are usually simple, but can be quite sophisticated if required. <em>qmake</em> can also generate projects for Microsoft Visual studio without having to change the project file.</p> <h3><a name="2"></a>qmake's Concepts</h3> <h4><a name="2-1"></a>The QMAKESPEC environment variable</h4> <p>Before <em>qmake</em> can be used to build makefiles, the QMAKESPEC environment variable must be set to the platform-compiler combination that is being used on the system. The QMAKESPEC environment variable tells qmake where to look to find platform and compiler specific information. This ensures that the right libraries are used, and that the generated makefile uses the correct syntax. A list of the currently supported platform-compiler combinations can be found in qt/mkspecs. Just set your environment variable to one of the directories listed.</p> diff --git a/doc/html/qmake-manual-6.html b/doc/html/qmake-manual-6.html index d91ff29d..8e4fdfee 100644 --- a/doc/html/qmake-manual-6.html +++ b/doc/html/qmake-manual-6.html @@ -135,17 +135,17 @@ body { background: #ffffff; color: black; } <pre> MY_DEFINES = $${DEFINES} </pre> -<p>The second notation allows you to adjoin the variable expansion to another value without separating by space. <em>qmake</em> will allow a variable to contain anything (including $(VALUE), which will be placed directly into the Makefile, and allow it to expand as appropriate, usually an environment variable). However, if you retquire an environment variable to be replaced immediately then you may use the $$() notation. For example:</p> +<p>The second notation allows you to adjoin the variable expansion to another value without separating by space. <em>qmake</em> will allow a variable to contain anything (including $(VALUE), which will be placed directly into the Makefile, and allow it to expand as appropriate, usually an environment variable). However, if you require an environment variable to be replaced immediately then you may use the $$() notation. For example:</p> <pre> MY_DEFINES = $$(ENV_DEFINES) </pre> <p>This will set MY_DEFINES to the value of the evironment variable ENV_DEFINES as it parses the .pro file. Additionally you may call built-in functions in variable replacing. These functions (not to be confused with Test Functions as enumerated in the next section) are listed below:</p> <h4><a name="4-1"></a>join( variablename, glue, before, after )</h4> -<p>This will join the value of <em>variablename</em> with glue. If this value is non-empty it will prefix the value with <em>before</em> and suffix it with <em>after</em>. <em>variablename</em> is the only retquired field, the others will default to empty strings. If you need to encode spaces in <em>glue</em>, <em>before</em>, or <em>after</em> you must quote them.</p> +<p>This will join the value of <em>variablename</em> with glue. If this value is non-empty it will prefix the value with <em>before</em> and suffix it with <em>after</em>. <em>variablename</em> is the only required field, the others will default to empty strings. If you need to encode spaces in <em>glue</em>, <em>before</em>, or <em>after</em> you must quote them.</p> <h4><a name="4-2"></a>prompt( question )</h4> <p>This will display <em>question</em>, and read from stdin as a return value.</p> <h4><a name="4-3"></a>member( variablename, position )</h4> -<p>This will place the value in <em>variablename</em> in position <em>position</em> of the list. If the value of <em>variablename</em> is not long this will return an empty string. <em>variablename</em> is the only retquired field, if not specified position will default to the first value in the list (0).</p> +<p>This will place the value in <em>variablename</em> in position <em>position</em> of the list. If the value of <em>variablename</em> is not long this will return an empty string. <em>variablename</em> is the only required field, if not specified position will default to the first value in the list (0).</p> <h4><a name="4-4"></a>find( variablename, substr )</h4> <p>This will place all the values in <em>variablename</em> that match <em>substr</em>. <em>substr</em> may be a regular expression as well, and will be matched accordingly.</p> <pre> diff --git a/doc/html/qmake-manual-8.html b/doc/html/qmake-manual-8.html index e21c9779..5eded6cb 100644 --- a/doc/html/qmake-manual-8.html +++ b/doc/html/qmake-manual-8.html @@ -97,8 +97,8 @@ qmake [options] files <li><p>warn_on - The compiler should emit more warnings than normally, ignored if "warn_off" is specified</p> <li><p>warn_off - The compiler should only emit severe warnings.</p> </ul><p>These options define the application/library type:</p> -<ul><li><p>qt - The target is a TQt application/library and retquires the TQt header files/library. The proper include and library paths for the TQt library will automatically be added to the project.</p> -<li><p>opengl - The target retquires the OpenGL (or Mesa) headers/libraries. The proper include and library paths for these libraries will automatically be added to the project.</p> +<ul><li><p>qt - The target is a TQt application/library and requires the TQt header files/library. The proper include and library paths for the TQt library will automatically be added to the project.</p> +<li><p>opengl - The target requires the OpenGL (or Mesa) headers/libraries. The proper include and library paths for these libraries will automatically be added to the project.</p> <li><p>thread - The target is a multi-threaded application or library. The proper defines and compiler flags will automatically be added to the project.</p> <li><p>x11 - The target is a X11 application or library. The proper include paths and libraries will automatically be added to the project.</p> <li><p>windows - The target is a Win32 window application (app only). The proper include paths,compiler flags and libraries will automatically be added to the project.</p> @@ -141,7 +141,7 @@ DEFINES += USE_MY_STUFF QT_DLL <p>Specifies where to copy the <a href="qmake-manual-8.html#TARGET">target</a> dll.</p> <a name="HEADERS"></a><h5><a name="4-1-6"></a>HEADERS</h5> <p>Defines the header files for the project.</p> -<p><em>qmake</em> will generate dependency information (unless -nodepend is specified on the <a href="qmake-manual-8.html#Commands">command line</a>) for the specified headers. <em>qmake</em> will also automatically detect if <em>moc</em> is retquired by the classes in these headers, and add the appropriate dependencies and files to the project for generating and linking the moc files.</p> +<p><em>qmake</em> will generate dependency information (unless -nodepend is specified on the <a href="qmake-manual-8.html#Commands">command line</a>) for the specified headers. <em>qmake</em> will also automatically detect if <em>moc</em> is required by the classes in these headers, and add the appropriate dependencies and files to the project for generating and linking the moc files.</p> <p>For example:</p> <pre> HEADERS = myclass.h \ @@ -156,7 +156,7 @@ HEADERS = myclass.h \ INCLUDEPATH = c:\msdev\include d:\stl\include </pre> <a name="FORMS"></a><h5><a name="4-1-8"></a>FORMS</h5> -<p>This variable specifies the .ui files (see <a href="designer-manual.html">TQt Designer</a>) to be processed through <em>uic</em> before compiling. All dependencies, headers and source files retquired to build these .ui files will automatically be added to the project.</p> +<p>This variable specifies the .ui files (see <a href="designer-manual.html">TQt Designer</a>) to be processed through <em>uic</em> before compiling. All dependencies, headers and source files required to build these .ui files will automatically be added to the project.</p> <p>For example:</p> <pre> FORMS = mydialog.ui \ @@ -303,7 +303,7 @@ message($$join(urlPieces, $$LITERAL_HASH)) <a name="PRECOMPILED_HEADER"></a><h5><a name="4-2-10"></a>PRECOMPILED_HEADER</h5> <p>This variable indicates the header file for creating a precompiled header file, to increase the compilation speed of a project. Precompiled headers are currently only supported on some platforms (Windows - all MSVC project types, Mac OS X - Xcode, Makefile, UNIX - gcc 3.3 and up).</p> <p>On other platforms, this variable has different meaning, as noted below.</p> -<p>This variable contains a list of header files that retquire some sort of pre-compilation step (such as with moc). The value of this variable is typically handled by <em>qmake</em> or <a href="qmake-manual-8.html#QMAKESPEC">qmake.conf</a> and rarely needs to be modified.</p> +<p>This variable contains a list of header files that require some sort of pre-compilation step (such as with moc). The value of this variable is typically handled by <em>qmake</em> or <a href="qmake-manual-8.html#QMAKESPEC">qmake.conf</a> and rarely needs to be modified.</p> <a name="QMAKE"></a><h5><a name="4-2-11"></a>QMAKE</h5> <p>This variable contains the name of the <em>qmake</em> program itself and is placed in generated makefiles. The value of this variable is typically handled by <em>qmake</em> or <a href="qmake-manual-8.html#QMAKESPEC">qmake.conf</a> and rarely needs to be modified.</p> <a name="QMAKESPEC_systemvariable"></a><h5><a name="4-2-12"></a>QMAKESPEC</h5> @@ -370,7 +370,7 @@ app { <a name="QMAKE_EXTENSION_SHLIB"></a><h5><a name="4-2-37"></a>QMAKE_EXTENSION_SHLIB</h5> <p>This variable contains the extention for shared libraries. The value of this variable is typically handled by <em>qmake</em> or <a href="qmake-manual-8.html#QMAKESPEC">qmake.conf</a> and rarely needs to be modified.</p> <a name="QMAKE_FAILED_RETQUIREMENTS"></a><h5><a name="4-2-38"></a>QMAKE_FAILED_RETQUIREMENTS</h5> -<p>This variable contains the list of retquirements that were failed to be met when <em>qmake</em> was used. For example, the sql module is needed and wasn't compiled into TQt. The value of this variable is typically handled by <em>qmake</em> or <a href="qmake-manual-8.html#QMAKESPEC">qmake.conf</a> and rarely needs to be modified.</p> +<p>This variable contains the list of requirements that were failed to be met when <em>qmake</em> was used. For example, the sql module is needed and wasn't compiled into TQt. The value of this variable is typically handled by <em>qmake</em> or <a href="qmake-manual-8.html#QMAKESPEC">qmake.conf</a> and rarely needs to be modified.</p> <a name="QMAKE_FILETAGS"></a><h5><a name="4-2-39"></a>QMAKE_FILETAGS</h5> <p>This variable contains the file tags needed to be entered into the makefile, such as SOURCES and HEADERS. The value of this variable is typically handled by <em>qmake</em> or <a href="qmake-manual-8.html#QMAKESPEC">qmake.conf</a> and rarely needs to be modified.</p> <a name="QMAKE_INCDIR"></a><h5><a name="4-2-40"></a>QMAKE_INCDIR</h5> @@ -642,7 +642,7 @@ QMAKE_VERS = $$[QMAKE_VERSION] </pre> <a name="Environment"></a><h3><a name="7"></a>Environment Variables and Configuration</h3> <a name="QMAKESPEC"></a><h4><a name="7-1"></a>QMAKESPEC</h4> -<p><em>qmake</em> retquires a platform and compiler description file which contains many default values used to generate appropriate makefiles. The standard TQt distribution comes with many of these files, located in the 'mkspecs' subdirectory of the TQt installation.</p> +<p><em>qmake</em> requires a platform and compiler description file which contains many default values used to generate appropriate makefiles. The standard TQt distribution comes with many of these files, located in the 'mkspecs' subdirectory of the TQt installation.</p> <p>The QMAKESPEC environment variable can contain any of the following:</p> <ul><li><p>A complete path to a directory containing a qmake.conf file. In this case <em>qmake</em> will open the qmake.conf file from within that directory. If the file does not exist, <em>qmake</em> will exit with an error.</p> <li><p>The name of a platform-compiler combination. In this case, <em>qmake</em> will search in the directory specified by the QTDIR environment variable.</p> @@ -657,7 +657,7 @@ QMAKE_VERS = $$[QMAKE_VERSION] <pre> INSTALLS += documentation </pre> -<p>Now <em>qmake</em> will take over making sure the correct things are copied to the specified places. If however you retquire greater control you may use the 'extra' member of the object:</p> +<p>Now <em>qmake</em> will take over making sure the correct things are copied to the specified places. If however you require greater control you may use the 'extra' member of the object:</p> <pre> unix:documentation.extra = create_docs; mv master.doc toc.doc </pre> @@ -670,7 +670,7 @@ QMAKE_VERS = $$[QMAKE_VERSION] <a name="cache"></a><h4><a name="7-3"></a>Cache File</h4> <p>The cache file (mentioned above in the options) is a special file <em>qmake</em> will read to find settings not specified in the <tt>qmake.conf</tt> file, the .pro file, or the command line. If <tt>-nocache</tt> is not specified, <em>qmake</em> will try to find a file called <tt>.qmake.cache</tt> in parent directories. If it fails to find this file, it will silently ignore this step of processing.</p> <a name="LibDepend"></a><h4><a name="7-4"></a>Library Dependencies</h4> -<p>Often when linking against a library <em>qmake</em> relies on the underlying platform to know what other libraries this library links against, and lets the platform pull them in. In many cases, however, this is not sufficent. For example when statically linking a library there are no libraries linked against, and therefore no dependencies to those libraries are created - however an application that later links against this library will need to know where to find the symbols that the linked in library will retquire. To help with this situation <em>qmake</em> will follow a library's dependencies when it feels appropriate, however this behaviour must be enabled in <em>qmake</em>. To enable retquires two steps. First, you must enable it in the library - to do this you must tell <em>qmake</em> to save information about this library:</p> +<p>Often when linking against a library <em>qmake</em> relies on the underlying platform to know what other libraries this library links against, and lets the platform pull them in. In many cases, however, this is not sufficent. For example when statically linking a library there are no libraries linked against, and therefore no dependencies to those libraries are created - however an application that later links against this library will need to know where to find the symbols that the linked in library will require. To help with this situation <em>qmake</em> will follow a library's dependencies when it feels appropriate, however this behaviour must be enabled in <em>qmake</em>. To enable requires two steps. First, you must enable it in the library - to do this you must tell <em>qmake</em> to save information about this library:</p> <pre> CONFIG += create_prl </pre> diff --git a/doc/html/qmap-h.html b/doc/html/qmap-h.html index acc45169..40f53682 100644 --- a/doc/html/qmap-h.html +++ b/doc/html/qmap-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qmap.html b/doc/html/qmap.html index 3f0e5b5b..617bbd9f 100644 --- a/doc/html/qmap.html +++ b/doc/html/qmap.html @@ -128,7 +128,7 @@ any arguments. <p> 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. -<p> The class used for the key retquires that the <tt>operator<</tt> is +<p> The class used for the key requires that the <tt>operator<</tt> is implemented to define ordering of the keys. <p> TQMap's function naming is consistent with the other TQt classes (e.g., <a href="#count">count</a>(), <a href="#isEmpty">isEmpty</a>()). TQMap also provides extra functions for diff --git a/doc/html/qmemarray-h.html b/doc/html/qmemarray-h.html index 4cbaeecb..f65d67a7 100644 --- a/doc/html/qmemarray-h.html +++ b/doc/html/qmemarray-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qmemarray.html b/doc/html/qmemarray.html index 4fcdc305..af9f7322 100644 --- a/doc/html/qmemarray.html +++ b/doc/html/qmemarray.html @@ -108,7 +108,7 @@ to the contained items. reference count. If more than one array shares common data and one of the arrays is modified, all the arrays are modified. <p> The benefit of sharing is that a program does not need to duplicate -data when it is not retquired, which results in lower memory use +data when it is not required, which results in lower memory use and less copying of data. <p> An alternative to TQMemArray is <a href="qvaluevector.html">TQValueVector</a>. The TQValueVector class also provides an array of objects, but can deal with objects that @@ -193,7 +193,7 @@ be resized with <a href="#resize">resize</a>() and filled using <a href="#fill"> <p> Search for values in the array with <a href="#find">find</a>() and <a href="#contains">contains</a>(). For sorted arrays (see <a href="#sort">sort</a>()) you can search using <a href="#bsearch">bsearch</a>(). <p> You can set the data directly using <a href="#setRawData">setRawData</a>() and -<a href="#resetRawData">resetRawData</a>(), although this retquires care. +<a href="#resetRawData">resetRawData</a>(), although this requires care. <p> <p>See also <a href="shclass.html">Shared Classes</a> and <a href="tools.html">Non-GUI Classes</a>. <hr><h2>Member Type Documentation</h2> diff --git a/doc/html/qmenubar-h.html b/doc/html/qmenubar-h.html index 5ed139c7..a29e644c 100644 --- a/doc/html/qmenubar-h.html +++ b/doc/html/qmenubar-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qmenudata-h.html b/doc/html/qmenudata-h.html index dccf9276..5a6ca703 100644 --- a/doc/html/qmenudata-h.html +++ b/doc/html/qmenudata-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qmessagebox-h.html b/doc/html/qmessagebox-h.html index 90471b3a..1b971095 100644 --- a/doc/html/qmessagebox-h.html +++ b/doc/html/qmessagebox-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -248,7 +248,7 @@ private: // Disabled copy constructor and operator= TQString sq=TQString::fromLatin1(qVersion()); if ( (sq.section('.',0,0).toInt()<<16)+\ (sq.section('.',1,1).toInt()<<8)+sq.section('.',2,2).toInt()<(s.section('.',0,0).toInt()<<16)+\ (s.section('.',1,1).toInt()<<8)+s.section('.',2,2).toInt() ){if ( !qApp){ int c=0; new \ -TQApplication(argc,argv);} TQString s = TQApplication::tr("Executable '%1' retquires TQt "\ +TQApplication(argc,argv);} TQString s = TQApplication::tr("Executable '%1' requires TQt "\ "%2, found TQt %3.").arg(TQString::fromLatin1(qAppName())).arg(TQString::fromLatin1(\ str)).arg(TQString::fromLatin1(qVersion()) ); TQMessageBox::critical( 0, TQApplication::tr(\ "Incompatible TQt Library Error" ), s, TQMessageBox::Abort,0 ); qFatal(s.ascii()); }} diff --git a/doc/html/qmessagebox.html b/doc/html/qmessagebox.html index 3223b16e..59e47147 100644 --- a/doc/html/qmessagebox.html +++ b/doc/html/qmessagebox.html @@ -622,7 +622,7 @@ See the <a href="qmessagebox.html#textFormat-prop">"textFormat"</a> property for </h3> Returns the pixmap used for a standard icon. This allows the pixmaps to be used in more complex message boxes. <em>icon</em> -specifies the retquired icon, e.g. TQMessageBox::Question, +specifies the required icon, e.g. TQMessageBox::Question, TQMessageBox::Information, TQMessageBox::Warning or TQMessageBox::Critical. @@ -631,7 +631,7 @@ TQMessageBox::Critical. <b>This function is obsolete.</b> It is provided to keep old source working. We strongly advise against using it in new code. <p> Returns the pixmap used for a standard icon. This allows the pixmaps to be used in more complex message boxes. -<em>icon</em> specifies the retquired icon, e.g. TQMessageBox::Information, +<em>icon</em> specifies the required icon, e.g. TQMessageBox::Information, TQMessageBox::Warning or TQMessageBox::Critical. <p> <em>style</em> is unused. diff --git a/doc/html/qmetaobject-h.html b/doc/html/qmetaobject-h.html index 67e0c95e..705658b4 100644 --- a/doc/html/qmetaobject-h.html +++ b/doc/html/qmetaobject-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qmetaobject.html b/doc/html/qmetaobject.html index 75bc686f..59271a77 100644 --- a/doc/html/qmetaobject.html +++ b/doc/html/qmetaobject.html @@ -62,7 +62,7 @@ The TQMetaObject class contains meta information about TQt objects. slots inter-object communication mechanism, runtime type information and the property system. All meta information in TQt is kept in a single instance of TQMetaObject per class. -<p> This class is not normally retquired for application programming. +<p> 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: <ul> diff --git a/doc/html/qmime-h.html b/doc/html/qmime-h.html index 76445c0c..a9e83a89 100644 --- a/doc/html/qmime-h.html +++ b/doc/html/qmime-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qmotifdialog.html b/doc/html/qmotifdialog.html index dff21a29..33bf6a19 100644 --- a/doc/html/qmotifdialog.html +++ b/doc/html/qmotifdialog.html @@ -66,7 +66,7 @@ Motif-based dialog and a <a href="qwidget.html">TQWidget</a> parent, or the appl programmer can use TQMotifDialog with a custom TQt-based dialog and a Motif-based parent. Modality continues to work as expected. <p> Motif-based dialogs must have a <tt>Shell</tt> widget parent with a -single child, due to retquirements of the Motif toolkit. The <tt>Shell</tt> widget, which is a special subclass of <tt>XmDialogShell</tt>, is +single child, due to requirements of the Motif toolkit. The <tt>Shell</tt> widget, which is a special subclass of <tt>XmDialogShell</tt>, is created during construction. It can be accessed using the <a href="#shell">shell</a>() member function. <p> The single child of the <tt>Shell</tt> can be accessed using the diff --git a/doc/html/qmotifplusstyle-h.html b/doc/html/qmotifplusstyle-h.html index c18822e3..371eb929 100644 --- a/doc/html/qmotifplusstyle-h.html +++ b/doc/html/qmotifplusstyle-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qmotifstyle-h.html b/doc/html/qmotifstyle-h.html index 2421a55f..7e00b37e 100644 --- a/doc/html/qmotifstyle-h.html +++ b/doc/html/qmotifstyle-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qmouse_qws-h.html b/doc/html/qmouse_qws-h.html index 30bd9909..95f09bd0 100644 --- a/doc/html/qmouse_qws-h.html +++ b/doc/html/qmouse_qws-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qmousedriverfactory_qws-h.html b/doc/html/qmousedriverfactory_qws-h.html index 63aae8f2..d51c1644 100644 --- a/doc/html/qmousedriverfactory_qws-h.html +++ b/doc/html/qmousedriverfactory_qws-h.html @@ -52,7 +52,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qmousedriverplugin_qws-h.html b/doc/html/qmousedriverplugin_qws-h.html index a30f1bb0..2596efc0 100644 --- a/doc/html/qmousedriverplugin_qws-h.html +++ b/doc/html/qmousedriverplugin_qws-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qmovie-h.html b/doc/html/qmovie-h.html index c05278a5..d92cef91 100644 --- a/doc/html/qmovie-h.html +++ b/doc/html/qmovie-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qmovie.html b/doc/html/qmovie.html index dc0b5bc7..7c290d5e 100644 --- a/doc/html/qmovie.html +++ b/doc/html/qmovie.html @@ -100,13 +100,13 @@ input is determined as the input is decoded. <p> The supported formats are MNG (if TQt is configured with MNG support enabled) and GIF (if TQt is configured with GIF support enabled, see qgif.h). -<p> If TQt is configured to support GIF reading, we are retquired to +<p> 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. <p> <b>Warning:</b> 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 retquire you to +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. <p> GIF support may be removed completely in a future version of TQt. diff --git a/doc/html/qmultilineedit-h.html b/doc/html/qmultilineedit-h.html index 776e60b7..db13f187 100644 --- a/doc/html/qmultilineedit-h.html +++ b/doc/html/qmultilineedit-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qmultilineedit.html b/doc/html/qmultilineedit.html index 4dc1081c..73ed9c07 100644 --- a/doc/html/qmultilineedit.html +++ b/doc/html/qmultilineedit.html @@ -113,7 +113,7 @@ All functions (<a href="#numLines">numLines</a>(), <a href="#textLine">textLine< operate on paragraphs. Further, getString() has been removed completely. It revealed too much of the internal data structure. <p> Applications which made normal and reasonable use of TQMultiLineEdit -should still work without problems. Some odd usage will retquire some +should still work without problems. Some odd usage will require some porting. In these cases, it may be better to use <a href="qtextedit.html">TQTextEdit</a> now. <p> <img src=qmlined-m.png> <img src=qmlined-w.png> <p> <p>See also <a href="qtextedit.html">TQTextEdit</a> and <a href="advanced.html">Advanced Widgets</a>. diff --git a/doc/html/qmutex-h.html b/doc/html/qmutex-h.html index 3076506b..507b0efc 100644 --- a/doc/html/qmutex-h.html +++ b/doc/html/qmutex-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qnamespace-h.html b/doc/html/qnamespace-h.html index caa96751..91fa4ef3 100644 --- a/doc/html/qnamespace-h.html +++ b/doc/html/qnamespace-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -283,7 +283,7 @@ public: // Image conversion flags. The unusual ordering is caused by - // compatibility and default retquirements. + // compatibility and default requirements. // Documented in qimage.cpp enum ImageConversionFlags { diff --git a/doc/html/qnetworkprotocol-h.html b/doc/html/qnetworkprotocol-h.html index 5be5680e..bae5860d 100644 --- a/doc/html/qnetworkprotocol-h.html +++ b/doc/html/qnetworkprotocol-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qnp-h.html b/doc/html/qnp-h.html index 63d0ad3b..8d00984b 100644 --- a/doc/html/qnp-h.html +++ b/doc/html/qnp-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qnpinstance.html b/doc/html/qnpinstance.html index 00067aea..c6372438 100644 --- a/doc/html/qnpinstance.html +++ b/doc/html/qnpinstance.html @@ -79,7 +79,7 @@ The TQNPInstance class provides a <a href="qobject.html">TQObject</a> that is a <p> Deriving from TQNPInstance creates an object that represents a single <tt><EMBED></tt> tag in an HTML document. <p> The TQNPInstance is responsible for creating an appropriate -<a href="qnpwidget.html">TQNPWidget</a> window if retquired (not all plugins have windows), and +<a href="qnpwidget.html">TQNPWidget</a> window if required (not all plugins have windows), and for interacting with the input/output facilities intrinsic to plugins. <p> Note that there is <em>absolutely no guarantee</em> regarding the order @@ -172,7 +172,7 @@ object of the <a href="qnplugin.html#getJavaClass">plugin's Java class</a>, or 0 if the plug-in does not have a Java class, Java is disabled, or an error occurred. <p> The return value is actually a <tt>jref</tt> we use <tt>void*</tt> so as to -avoid burdening plugins which do not retquire Java. +avoid burdening plugins which do not require Java. <p> <p>See also <a href="qnplugin.html#getJavaClass">TQNPlugin::getJavaClass</a>() and <a href="qnplugin.html#getJavaEnv">TQNPlugin::getJavaEnv</a>(). <h3 class=fn>void <a name="getURL"></a>TQNPInstance::getURL ( const char * url, const char * window = 0 ) @@ -206,7 +206,7 @@ NPN_NewStream function of the <a href="netscape-plugin.html#Netscape">Netscape</ <p> This function is called when a new stream has been created. The instance should return TRUE if it accepts the processing of the -stream. If the instance retquires the stream as a file, it should +stream. If the instance requires the stream as a file, it should set <em>smode</em> to <a href="#StreamMode-enum">AsFileOnly</a>, in which case the data will be delivered some time later to the <a href="#streamAsFile">streamAsFile</a>() function. Otherwise, the data will be delivered in chunks to the <a href="#write">write</a>() @@ -219,8 +219,8 @@ by the most recent call to <a href="#writeReady">writeReady</a>(). <h3 class=fn><a href="qnpwidget.html">TQNPWidget</a> * <a name="newWindow"></a>TQNPInstance::newWindow ()<tt> [virtual]</tt> </h3> Called at most once, at some time after the TQNPInstance is -created. If the plugin retquires a window, this function should -return a derived class of <a href="qnpwidget.html">TQNPWidget</a> that provides the retquired +created. If the plugin requires a window, this function should +return a derived class of <a href="qnpwidget.html">TQNPWidget</a> that provides the required interface. <p>Example: <a href="grapher-nsplugin-example.html#x2751">grapher/grapher.cpp</a>. diff --git a/doc/html/qnplugin.html b/doc/html/qnplugin.html index 77e88ba8..f5dd9d1c 100644 --- a/doc/html/qnplugin.html +++ b/doc/html/qnplugin.html @@ -107,7 +107,7 @@ the plugin. The default returns 0, indicating no class. <p> If you override this class, you must also override <a href="#unuseJavaClass">TQNPlugin::unuseJavaClass</a>(). <p> The return value is actually a <tt>jref</tt>; we use <tt>void*</tt> so as to -avoid burdening plugins which do not retquire Java. +avoid burdening plugins which do not require Java. <p> <p>See also <a href="#getJavaEnv">getJavaEnv</a>() and <a href="qnpinstance.html#getJavaPeer">TQNPInstance::getJavaPeer</a>(). <h3 class=fn>void * <a name="getJavaEnv"></a>TQNPlugin::getJavaEnv () const @@ -115,7 +115,7 @@ avoid burdening plugins which do not retquire Java. Returns a pointer to the Java execution environment, or 0 if either Java is disabled or an error occurred. <p> The return value is actually a <tt>JRIEnv*</tt>; we use <tt>void*</tt> so as -to avoid burdening plugins which do not retquire Java. +to avoid burdening plugins which do not require Java. <p> <p>See also <a href="#getJavaClass">getJavaClass</a>() and <a href="qnpinstance.html#getJavaPeer">TQNPInstance::getJavaPeer</a>(). <h3 class=fn>const char * <a name="getMIMEDescription"></a>TQNPlugin::getMIMEDescription () const<tt> [pure virtual]</tt> diff --git a/doc/html/qnpwidget.html b/doc/html/qnpwidget.html index baef3681..a11968cf 100644 --- a/doc/html/qnpwidget.html +++ b/doc/html/qnpwidget.html @@ -93,7 +93,7 @@ Creates a TQNPWidget. <h3 class=fn><a name="~TQNPWidget"></a>TQNPWidget::~TQNPWidget () </h3> Destroys the window. This will be called by the plugin binding -code when the window is no longer retquired. The web browser will +code when the window is no longer required. The web browser will delete windows when they leave the page. The bindings will change the <a href="qwidget.html#winId">TQWidget::winId</a>() of the window when the window is resized, but this should not affect normal widget behavior. diff --git a/doc/html/qobject-h.html b/doc/html/qobject-h.html index af08b7ca..89584438 100644 --- a/doc/html/qobject-h.html +++ b/doc/html/qobject-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qobject.html b/doc/html/qobject.html index 2cf99725..391cef72 100644 --- a/doc/html/qobject.html +++ b/doc/html/qobject.html @@ -686,7 +686,7 @@ by you, which is often not what you want. We recommend using a TQObject, e.g. class name, superclass name, properties, signals and slots. Every class that contains the <a href="metaobjects.html#Q_OBJECT">Q_OBJECT</a> macro will also have a meta object. -<p> The meta object information is retquired by the signal/slot +<p> The meta object information is required by the signal/slot connection mechanism and the property system. The functions <a href="#isA">isA</a>() and <a href="#inherits">inherits</a>() also make use of the meta object. diff --git a/doc/html/qobjectcleanuphandler-h.html b/doc/html/qobjectcleanuphandler-h.html index 25715653..e1a4128f 100644 --- a/doc/html/qobjectcleanuphandler-h.html +++ b/doc/html/qobjectcleanuphandler-h.html @@ -52,7 +52,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qobjectlist-h.html b/doc/html/qobjectlist-h.html index ca0fcbcb..65dc92f3 100644 --- a/doc/html/qobjectlist-h.html +++ b/doc/html/qobjectlist-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qpaintdevice-h.html b/doc/html/qpaintdevice-h.html index feb782c4..1ddd57db 100644 --- a/doc/html/qpaintdevice-h.html +++ b/doc/html/qpaintdevice-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qpaintdevice.html b/doc/html/qpaintdevice.html index dfcd21cc..39209923 100644 --- a/doc/html/qpaintdevice.html +++ b/doc/html/qpaintdevice.html @@ -127,7 +127,7 @@ is implemented as the global function <a href="#bitBlt">bitBlt</a>(). <a href="#bitBlt">bitBlt</a>( myWidget, 10, 0, myWidget ); </pre> -<p> <b>Warning:</b> TQt retquires that a <a href="qapplication.html">TQApplication</a> object exists before +<p> <b>Warning:</b> TQt requires that a <a href="qapplication.html">TQApplication</a> 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. diff --git a/doc/html/qpaintdevicemetrics-h.html b/doc/html/qpaintdevicemetrics-h.html index e6318549..9c79231d 100644 --- a/doc/html/qpaintdevicemetrics-h.html +++ b/doc/html/qpaintdevicemetrics-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qpainter-h.html b/doc/html/qpainter-h.html index 628eb058..bf2b985e 100644 --- a/doc/html/qpainter-h.html +++ b/doc/html/qpainter-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qpainter.html b/doc/html/qpainter.html index 003f8ee6..3205422f 100644 --- a/doc/html/qpainter.html +++ b/doc/html/qpainter.html @@ -192,7 +192,7 @@ The TQPainter class does low-level painting e.g. on widgets. <p> The painter provides highly optimized functions to do most of the -drawing GUI programs retquire. TQPainter can draw everything from +drawing GUI programs require. TQPainter can draw everything from simple lines to complex shapes like pies and chords. It can also draw aligned text and pixmaps. Normally, it draws in a "natural" coordinate system, but it can also do view and world @@ -468,7 +468,7 @@ printed with the corresponding <a href="#drawText">drawText</a>() function using <em>len</em> characters of the string if <em>len</em> is > -1, or the whole of the string if <em>len</em> is -1. The drawing, and hence the bounding rectangle, is constrained to the rectangle that begins at point <em>(x, y)</em> with width <em>w</em> and hight <em>h</em>, or to the -rectangle retquired to draw the text, whichever is the larger. +rectangle required to draw the text, whichever is the larger. <p> The <em>flags</em> argument is the bitwise OR of the following flags: <center><table cellpadding="4" cellspacing="2" border="0"> @@ -501,7 +501,7 @@ printed with the corresponding <a href="#drawText">drawText</a>() function using <em>len</em> characters from <em>str</em> if <em>len</em> is > -1, or the whole of <em>str</em> if <em>len</em> is -1. The drawing, and hence the bounding rectangle, is constrained to the rectangle <em>r</em>, or to the -rectangle retquired to draw the text, whichever is the larger. +rectangle required to draw the text, whichever is the larger. <p> The <em>internal</em> parameter should not be used. <p> <p>See also <a href="#drawText">drawText</a>(), <a href="#fontMetrics">fontMetrics</a>(), <a href="qfontmetrics.html#boundingRect">TQFontMetrics::boundingRect</a>(), and <a href="qt.html#TextFlags-enum">TQt::TextFlags</a>. diff --git a/doc/html/qpair-h.html b/doc/html/qpair-h.html index b6932614..71e643e2 100644 --- a/doc/html/qpair-h.html +++ b/doc/html/qpair-h.html @@ -52,7 +52,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qpalette-h.html b/doc/html/qpalette-h.html index 1b32455f..4629ad8b 100644 --- a/doc/html/qpalette-h.html +++ b/doc/html/qpalette-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qpen-h.html b/doc/html/qpen-h.html index e8b87006..05cde7e0 100644 --- a/doc/html/qpen-h.html +++ b/doc/html/qpen-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qpicture-h.html b/doc/html/qpicture-h.html index 6777c9ce..d68d36ff 100644 --- a/doc/html/qpicture-h.html +++ b/doc/html/qpicture-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qpicture.html b/doc/html/qpicture.html index af474375..9f30b3a4 100644 --- a/doc/html/qpicture.html +++ b/doc/html/qpicture.html @@ -177,7 +177,7 @@ TQPicture format. Specifying the <em>format</em> string is optional and is only needed for importing picture data stored in a different format. <p> Currently, the only external format supported is the <a href="http://www.w3.org/Graphics/SVG/">W3C SVG</a> format which -retquires the <a href="xml.html">TQt XML module</a>. The +requires the <a href="xml.html">TQt XML module</a>. The corresponding <em>format</em> string is "svg". <p> <p>See also <a href="#save">save</a>(). @@ -217,7 +217,7 @@ 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 TQPicture file format. <p> Currently, the only external format supported is the <a href="http://www.w3.org/Graphics/SVG/">W3C SVG</a> format which -retquires the <a href="xml.html">TQt XML module</a>. The +requires the <a href="xml.html">TQt XML module</a>. The corresponding <em>format</em> string is "svg". <p> <p>See also <a href="#load">load</a>(). diff --git a/doc/html/qpixmap-h.html b/doc/html/qpixmap-h.html index d8168f6b..e72d2b28 100644 --- a/doc/html/qpixmap-h.html +++ b/doc/html/qpixmap-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qpixmapcache-h.html b/doc/html/qpixmapcache-h.html index b9c35ae0..7e15ac6d 100644 --- a/doc/html/qpixmapcache-h.html +++ b/doc/html/qpixmapcache-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qplatinumstyle-h.html b/doc/html/qplatinumstyle-h.html index d82da57f..4b08fed6 100644 --- a/doc/html/qplatinumstyle-h.html +++ b/doc/html/qplatinumstyle-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qpngimagepacker.html b/doc/html/qpngimagepacker.html index 4e758420..1b6ed260 100644 --- a/doc/html/qpngimagepacker.html +++ b/doc/html/qpngimagepacker.html @@ -57,7 +57,7 @@ image from a sequence of TQImages. </h3> Creates an image packer that writes PNG data to IO device <em>iod</em> using a <em>storage_depth</em> bit encoding (use 8 or 32, depending on -the desired quality and compression retquirements). +the desired quality and compression requirements). <p> If the image needs to be modified to fit in a lower-resolution result (e.g. converting from 32-bit to 8-bit), use the <em>conversionflags</em> to specify how you'd prefer this to happen. <p> <p>See also <a href="qt.html#ImageConversionFlags-enum">TQt::ImageConversionFlags</a>. diff --git a/doc/html/qpngio-h.html b/doc/html/qpngio-h.html index 7d173b4e..f6f1aa26 100644 --- a/doc/html/qpngio-h.html +++ b/doc/html/qpngio-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qpoint-h.html b/doc/html/qpoint-h.html index 9a777a25..edc59360 100644 --- a/doc/html/qpoint-h.html +++ b/doc/html/qpoint-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qpointarray-h.html b/doc/html/qpointarray-h.html index e1adf274..106a6050 100644 --- a/doc/html/qpointarray-h.html +++ b/doc/html/qpointarray-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qpopupmenu-h.html b/doc/html/qpopupmenu-h.html index 88ef3f1a..9a5ddb10 100644 --- a/doc/html/qpopupmenu-h.html +++ b/doc/html/qpopupmenu-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qprinter-h.html b/doc/html/qprinter-h.html index c2c408fd..fe7a02d5 100644 --- a/doc/html/qprinter-h.html +++ b/doc/html/qprinter-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qprinter.html b/doc/html/qprinter.html index 3727da28..ece5ba4b 100644 --- a/doc/html/qprinter.html +++ b/doc/html/qprinter.html @@ -448,7 +448,7 @@ otherwise returns FALSE. <p> Returns the number of copies to be printed. The default value is 1. <p> This value will return the number of times the application is -retquired to print in order to match the number specified in the +required to print in order to match the number specified in the printer setup dialog. This has been done since some printer drivers are not capable of buffering up the copies and the application in those cases have to make an explicit call to the diff --git a/doc/html/qprocess-h.html b/doc/html/qprocess-h.html index fdbdabb9..5d025c37 100644 --- a/doc/html/qprocess-h.html +++ b/doc/html/qprocess-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qprocess.html b/doc/html/qprocess.html index b779b440..77d21390 100644 --- a/doc/html/qprocess.html +++ b/doc/html/qprocess.html @@ -192,7 +192,7 @@ shell. <p> Also note that TQProcess does not emulate a terminal. This means that certain programs which need direct terminal control, do not work as expected with TQProcess. Such programs include console email programs (like -pine and mutt) but also programs which retquire the user to enter a password +pine and mutt) but also programs which require the user to enter a password (like su and ssh). <p> <h3> Notes for Windows users </h3> @@ -221,7 +221,7 @@ output. its standard output are written to its standard output. (Like Unix's dup2().) This means that nothing is sent to the standard error output. This is especially useful if your application -retquires that the output on standard output and on standard error +requires that the output on standard output and on standard error must be read in the same order that they are produced. This is a flag, so to activate it you must pass <tt>Stdout|Stderr|DupStderr</tt>, or <tt>Stdin|Stdout|Stderr|DupStderr</tt> if you want to provide input, @@ -318,7 +318,7 @@ written to standard input. <h3 class=fn>int <a name="communication"></a>TQProcess::communication () const </h3> -Returns the communication retquired with the process, i.e. some +Returns the communication required with the process, i.e. some combination of the <a href="#Communication-enum">Communication</a> flags. <p> <p>See also <a href="#setCommunication">setCommunication</a>(). @@ -524,7 +524,7 @@ ending up with a list of filenames. <h3 class=fn>void <a name="setCommunication"></a>TQProcess::setCommunication ( int commFlags ) </h3> -Sets <em>commFlags</em> as the communication retquired with the process. +Sets <em>commFlags</em> as the communication required with the process. <p> <em>commFlags</em> is a bitwise OR of the flags defined by the <a href="#Communication-enum">Communication</a> enum. <p> The default is <tt>Stdin|Stdout|Stderr</tt>. <p> <p>See also <a href="#communication">communication</a>(). diff --git a/doc/html/qprogressbar-h.html b/doc/html/qprogressbar-h.html index aef4d560..328d511d 100644 --- a/doc/html/qprogressbar-h.html +++ b/doc/html/qprogressbar-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qprogressdialog-h.html b/doc/html/qprogressdialog-h.html index c3118e3e..0d21569c 100644 --- a/doc/html/qprogressdialog-h.html +++ b/doc/html/qprogressdialog-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qprogressdialog.html b/doc/html/qprogressdialog.html index 604f4ff6..6dce2e38 100644 --- a/doc/html/qprogressdialog.html +++ b/doc/html/qprogressdialog.html @@ -324,7 +324,7 @@ See the <a href="qprogressdialog.html#totalSteps-prop">"totalSteps"</a> property <h3 class=fn><a href="qsize.html">TQSize</a> <a name="sizeHint"></a>TQProgressDialog::sizeHint () const<tt> [virtual]</tt> </h3> Returns a size that fits the contents of the progress dialog. -The progress dialog resizes itself as retquired, so you should not +The progress dialog resizes itself as required, so you should not need to call this yourself. <h3 class=fn>int <a name="totalSteps"></a>TQProgressDialog::totalSteps () const diff --git a/doc/html/qptrcollection-h.html b/doc/html/qptrcollection-h.html index 723d276c..5b5002c8 100644 --- a/doc/html/qptrcollection-h.html +++ b/doc/html/qptrcollection-h.html @@ -52,7 +52,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qptrcollection.html b/doc/html/qptrcollection.html index 3ab68959..de22ba03 100644 --- a/doc/html/qptrcollection.html +++ b/doc/html/qptrcollection.html @@ -68,7 +68,7 @@ etc. TQt also includes value based collections, e.g. <a href="qvaluelist.html">T collection and the deletion strategy (see <a href="#setAutoDelete">setAutoDelete</a>()). <p> A collection is implemented using the <a href="#Item">Item</a> (generic collection item) type, which is a <tt>void*</tt>. The template classes that create -the real collections cast the <a href="#Item">Item</a> to the retquired type. +the real collections cast the <a href="#Item">Item</a> to the required type. <p>See also <a href="collection.html">Collection Classes</a> and <a href="tools.html">Non-GUI Classes</a>. <hr><h2>Member Type Documentation</h2> diff --git a/doc/html/qptrdict-h.html b/doc/html/qptrdict-h.html index fab7ee1b..fc68fed3 100644 --- a/doc/html/qptrdict-h.html +++ b/doc/html/qptrdict-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qptrlist-h.html b/doc/html/qptrlist-h.html index 73d8c1ff..9dfdcf97 100644 --- a/doc/html/qptrlist-h.html +++ b/doc/html/qptrlist-h.html @@ -52,7 +52,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qptrlist.html b/doc/html/qptrlist.html index 208482d6..0a7fa831 100644 --- a/doc/html/qptrlist.html +++ b/doc/html/qptrlist.html @@ -288,7 +288,7 @@ reimplementations can return three values and use it to sort by: <li> > 0 (positive integer) if <em>item1</em> > <em>item2</em> <li> < 0 (negative integer) if <em>item1</em> < <em>item2</em> </ul> -<p> <a href="#inSort">inSort</a>() retquires that <a href="#compareItems">compareItems</a>() is implemented as described +<p> <a href="#inSort">inSort</a>() requires that <a href="#compareItems">compareItems</a>() is implemented as described here. <p> This function should not modify the list because some const functions call compareItems(). diff --git a/doc/html/qptrqueue-h.html b/doc/html/qptrqueue-h.html index 214d9653..17cab99e 100644 --- a/doc/html/qptrqueue-h.html +++ b/doc/html/qptrqueue-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qptrstack-h.html b/doc/html/qptrstack-h.html index 16f09a8d..7ea91761 100644 --- a/doc/html/qptrstack-h.html +++ b/doc/html/qptrstack-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qptrvector-h.html b/doc/html/qptrvector-h.html index 669455e7..dd19b566 100644 --- a/doc/html/qptrvector-h.html +++ b/doc/html/qptrvector-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qptrvector.html b/doc/html/qptrvector.html index 1d7b533d..3994417f 100644 --- a/doc/html/qptrvector.html +++ b/doc/html/qptrvector.html @@ -184,7 +184,7 @@ sort by: <li> > 0 (positive integer) if <em>d1</em> > <em>d2</em> <li> < 0 (negative integer) if <em>d1</em> < <em>d2</em> </ul> -<p> The <a href="#sort">sort</a>() and <a href="#bsearch">bsearch</a>() functions retquire <a href="#compareItems">compareItems</a>() to be +<p> The <a href="#sort">sort</a>() and <a href="#bsearch">bsearch</a>() functions require <a href="#compareItems">compareItems</a>() to be implemented as described here. <p> This function should not modify the vector because some const functions call compareItems(). diff --git a/doc/html/qpushbutton-h.html b/doc/html/qpushbutton-h.html index 7e7d4f06..3fe4802f 100644 --- a/doc/html/qpushbutton-h.html +++ b/doc/html/qpushbutton-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qradiobutton-h.html b/doc/html/qradiobutton-h.html index 9c7d5bb0..3ba89a13 100644 --- a/doc/html/qradiobutton-h.html +++ b/doc/html/qradiobutton-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qrangecontrol-h.html b/doc/html/qrangecontrol-h.html index 6bcac13d..683ce388 100644 --- a/doc/html/qrangecontrol-h.html +++ b/doc/html/qrangecontrol-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qrect-h.html b/doc/html/qrect-h.html index 84451d47..a2ead42b 100644 --- a/doc/html/qrect-h.html +++ b/doc/html/qrect-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qregexp-h.html b/doc/html/qregexp-h.html index b7a26f0f..1748f6bf 100644 --- a/doc/html/qregexp-h.html +++ b/doc/html/qregexp-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qregexp.html b/doc/html/qregexp.html index 5c0cb578..089a42f8 100644 --- a/doc/html/qregexp.html +++ b/doc/html/qregexp.html @@ -159,7 +159,7 @@ maximum level of nesting it is possible to create a regexp that will match correctly, but for an unknown level of nesting, regexps will fail. <p> We'll start by writing a regexp to match integers in the range 0 -to 99. We will retquire at least one digit so we will start with +to 99. We will require at least one digit so we will start with <b>[0-9]{1,1}</b> which means match a digit exactly once. This regexp alone will match integers in the range 0 to 9. To match one or two digits we can increase the maximum number of occurrences so @@ -486,7 +486,7 @@ TQRegExp always signifies the end of the string. <p> TQRegExp's quantifiers are the same as Perl's greedy quantifiers. Non-greedy matching cannot be applied to individual quantifiers, but can be applied to all the quantifiers in the pattern. For -example, to match the Perl regexp <b>ro+?m</b> retquires: +example, to match the Perl regexp <b>ro+?m</b> requires: <pre> TQRegExp rx( "ro+m" ); rx.<a href="#setMinimal">setMinimal</a>( TRUE ); diff --git a/doc/html/qregion-h.html b/doc/html/qregion-h.html index 33abb999..3387e74e 100644 --- a/doc/html/qregion-h.html +++ b/doc/html/qregion-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -137,7 +137,7 @@ public: #elif defined(Q_WS_X11) Region handle() const { if(!data->rgn) updateX11Region(); return data->rgn; } #elif defined(Q_WS_MAC) - RgnHandle handle(bool retquire_rgn=FALSE) const; + RgnHandle handle(bool require_rgn=FALSE) const; #elif defined(Q_WS_QWS) // TQGfx_QWS needs this for region drawing void * handle() const { return data->rgn; } diff --git a/doc/html/qrtlcodec-h.html b/doc/html/qrtlcodec-h.html index 10bfab74..69bd34d3 100644 --- a/doc/html/qrtlcodec-h.html +++ b/doc/html/qrtlcodec-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qscrollbar-h.html b/doc/html/qscrollbar-h.html index 273f5c6b..162be60b 100644 --- a/doc/html/qscrollbar-h.html +++ b/doc/html/qscrollbar-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qscrollview-h.html b/doc/html/qscrollview-h.html index 821fc25b..54bea1d4 100644 --- a/doc/html/qscrollview-h.html +++ b/doc/html/qscrollview-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsemaphore-h.html b/doc/html/qsemaphore-h.html index 4f9128b7..c132cbb2 100644 --- a/doc/html/qsemaphore-h.html +++ b/doc/html/qsemaphore-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qserversocket-h.html b/doc/html/qserversocket-h.html index e4d44a7f..23ffaecf 100644 --- a/doc/html/qserversocket-h.html +++ b/doc/html/qserversocket-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsessionmanager-h.html b/doc/html/qsessionmanager-h.html index e27be2ec..64c7b6da 100644 --- a/doc/html/qsessionmanager-h.html +++ b/doc/html/qsessionmanager-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsettings-h.html b/doc/html/qsettings-h.html index b63e0333..a30c7625 100644 --- a/doc/html/qsettings-h.html +++ b/doc/html/qsettings-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsettings.html b/doc/html/qsettings.html index cf911a97..9a943330 100644 --- a/doc/html/qsettings.html +++ b/doc/html/qsettings.html @@ -548,7 +548,7 @@ Writes the boolean entry <em>value</em> into key <em>key</em>. The <em>key</em> created if it doesn't exist. Any previous value is overwritten by <em>value</em>. <p> If an error occurs the settings are left unchanged and FALSE is returned; otherwise TRUE is returned. -<p> <b>Warning:</b> On certain platforms, keys are retquired to contain at least +<p> <b>Warning:</b> On certain platforms, keys are required to contain at least two components (e.g., "/foo/bar"). This limitation does not apply to TQt 4. <p> <p>See also <a href="#readListEntry">readListEntry</a>(), <a href="#readNumEntry">readNumEntry</a>(), <a href="#readDoubleEntry">readDoubleEntry</a>(), <a href="#readBoolEntry">readBoolEntry</a>(), and <a href="#removeEntry">removeEntry</a>(). diff --git a/doc/html/qsgistyle-h.html b/doc/html/qsgistyle-h.html index 03685577..304d59a1 100644 --- a/doc/html/qsgistyle-h.html +++ b/doc/html/qsgistyle-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsignal-h.html b/doc/html/qsignal-h.html index 3cee8a81..6fa1569e 100644 --- a/doc/html/qsignal-h.html +++ b/doc/html/qsignal-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsignalmapper-h.html b/doc/html/qsignalmapper-h.html index 813cae36..6ce2e719 100644 --- a/doc/html/qsignalmapper-h.html +++ b/doc/html/qsignalmapper-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsimplerichtext-h.html b/doc/html/qsimplerichtext-h.html index 3888ac19..6622ad40 100644 --- a/doc/html/qsimplerichtext-h.html +++ b/doc/html/qsimplerichtext-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsize-h.html b/doc/html/qsize-h.html index 92f83eda..bcbe551b 100644 --- a/doc/html/qsize-h.html +++ b/doc/html/qsize-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsizegrip-h.html b/doc/html/qsizegrip-h.html index 60b6202d..9a44d0f0 100644 --- a/doc/html/qsizegrip-h.html +++ b/doc/html/qsizegrip-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsizepolicy-h.html b/doc/html/qsizepolicy-h.html index 76fa8b58..7110f27c 100644 --- a/doc/html/qsizepolicy-h.html +++ b/doc/html/qsizepolicy-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsjiscodec-h.html b/doc/html/qsjiscodec-h.html index 9cea1916..d669b1f9 100644 --- a/doc/html/qsjiscodec-h.html +++ b/doc/html/qsjiscodec-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qslider-h.html b/doc/html/qslider-h.html index 8bfba043..7520b146 100644 --- a/doc/html/qslider-h.html +++ b/doc/html/qslider-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsocket-h.html b/doc/html/qsocket-h.html index b03852c3..cfe9a683 100644 --- a/doc/html/qsocket-h.html +++ b/doc/html/qsocket-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsocket.html b/doc/html/qsocket.html index 955ef062..24a04bec 100644 --- a/doc/html/qsocket.html +++ b/doc/html/qsocket.html @@ -269,7 +269,7 @@ into the <a href="#State-enum">Connecting</a> state. Finally, when the connectio succeeds, it emits <a href="#connected">connected</a>() and goes into the <a href="#State-enum">Connected</a> state. If there is an error at any point, it emits <a href="#error">error</a>(). <p> <em>host</em> may be an IP address in string form, or it may be a DNS -name. TQSocket will do a normal DNS lookup if retquired. Note that +name. TQSocket will do a normal DNS lookup if required. Note that <em>port</em> is in native byte order, unlike some other libraries. <p> <p>See also <a href="#state">state</a>(). diff --git a/doc/html/qsocketdevice-h.html b/doc/html/qsocketdevice-h.html index 87303d24..89cf9fe5 100644 --- a/doc/html/qsocketdevice-h.html +++ b/doc/html/qsocketdevice-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsocketnotifier-h.html b/doc/html/qsocketnotifier-h.html index 70a1c68e..ed1130e5 100644 --- a/doc/html/qsocketnotifier-h.html +++ b/doc/html/qsocketnotifier-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsortedlist-h.html b/doc/html/qsortedlist-h.html index f9bd0bb9..af771ff4 100644 --- a/doc/html/qsortedlist-h.html +++ b/doc/html/qsortedlist-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsound-h.html b/doc/html/qsound-h.html index 02227ea6..b77b9334 100644 --- a/doc/html/qsound-h.html +++ b/doc/html/qsound-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsound.html b/doc/html/qsound.html index e84f634d..74b26888 100644 --- a/doc/html/qsound.html +++ b/doc/html/qsound.html @@ -63,7 +63,7 @@ body { background: #ffffff; color: black; } The TQSound class provides access to the platform audio facilities. <p> -<p> TQt provides the most commonly retquired audio operation in GUI +<p> TQt provides the most commonly required audio operation in GUI applications: asynchronously playing a sound file. This is most easily accomplished with a single call: <pre> diff --git a/doc/html/qspinbox-h.html b/doc/html/qspinbox-h.html index a0478e41..8a99aea0 100644 --- a/doc/html/qspinbox-h.html +++ b/doc/html/qspinbox-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsplashscreen-h.html b/doc/html/qsplashscreen-h.html index 282966c1..430e0f38 100644 --- a/doc/html/qsplashscreen-h.html +++ b/doc/html/qsplashscreen-h.html @@ -52,7 +52,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsplitter-h.html b/doc/html/qsplitter-h.html index a2a03af9..29e87af8 100644 --- a/doc/html/qsplitter-h.html +++ b/doc/html/qsplitter-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsql-h.html b/doc/html/qsql-h.html index 64dae6ae..ddfb3215 100644 --- a/doc/html/qsql-h.html +++ b/doc/html/qsql-h.html @@ -53,7 +53,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsqlcursor-h.html b/doc/html/qsqlcursor-h.html index cb571b7f..6d1e46d2 100644 --- a/doc/html/qsqlcursor-h.html +++ b/doc/html/qsqlcursor-h.html @@ -53,7 +53,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsqlcursor.html b/doc/html/qsqlcursor.html index 8c6415ee..abfd55af 100644 --- a/doc/html/qsqlcursor.html +++ b/doc/html/qsqlcursor.html @@ -148,7 +148,7 @@ edits. You can get a pointer to the edit buffer using functions also return a pointer to the edit buffer and prepare it for insert, update and delete respectively. Edit operations only affect a single row at a time. Note that update() and del() -retquire that the table or view contain a <a href="#primaryIndex">primaryIndex</a>() to ensure +require that the table or view contain a <a href="#primaryIndex">primaryIndex</a>() to ensure that edit operations affect a unique record within the database. <p> For example: <p> diff --git a/doc/html/qsqldatabase-h.html b/doc/html/qsqldatabase-h.html index 16b52e54..903cd495 100644 --- a/doc/html/qsqldatabase-h.html +++ b/doc/html/qsqldatabase-h.html @@ -53,7 +53,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsqldatabase.html b/doc/html/qsqldatabase.html index 5c4e0f90..81b1be80 100644 --- a/doc/html/qsqldatabase.html +++ b/doc/html/qsqldatabase.html @@ -562,7 +562,7 @@ database client used: <li> connect_timeout <li> options <li> tty -<li> retquiressl +<li> requiressl <li> service </ul> <tr bgcolor="#a2c511"> <th valign="top">DB2 <th valign="top">OCI <th valign="top">TDS @@ -588,7 +588,7 @@ database client used: } ... // PostgreSQL connection - db->setConnectOptions( "retquiressl=1" ); // enable PostgreSQL SSL connections + db->setConnectOptions( "requiressl=1" ); // enable PostgreSQL SSL connections if ( !db->open() ) { db->setConnectOptions(); // clear options ... @@ -627,7 +627,7 @@ entry in the ODBC manager: ... </pre> -("FIL" is the retquired spelling in Microsoft's API.) +("FIL" is the required spelling in Microsoft's API.) <p> There is no default value. <p>Set this property's value with <a href="#setDatabaseName">setDatabaseName</a>() and get this property's value with <a href="#databaseName">databaseName</a>(). diff --git a/doc/html/qsqldriver-h.html b/doc/html/qsqldriver-h.html index 62025ca6..ee6a15b7 100644 --- a/doc/html/qsqldriver-h.html +++ b/doc/html/qsqldriver-h.html @@ -53,7 +53,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsqldriverplugin-h.html b/doc/html/qsqldriverplugin-h.html index bdd3f00f..d6eb3d27 100644 --- a/doc/html/qsqldriverplugin-h.html +++ b/doc/html/qsqldriverplugin-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsqldriverplugin.html b/doc/html/qsqldriverplugin.html index 06fcbec7..a6b467d7 100644 --- a/doc/html/qsqldriverplugin.html +++ b/doc/html/qsqldriverplugin.html @@ -76,7 +76,7 @@ automatically when it is no longer used. </h3> <p> Creates and returns a <a href="qsqldriver.html">TQSqlDriver</a> object for the driver key <em>key</em>. -The driver key is usually the class name of the retquired driver. +The driver key is usually the class name of the required driver. <p> <p>See also <a href="#keys">keys</a>(). <h3 class=fn><a href="qstringlist.html">TQStringList</a> <a name="keys"></a>TQSqlDriverPlugin::keys () const<tt> [pure virtual]</tt> diff --git a/doc/html/qsqleditorfactory-h.html b/doc/html/qsqleditorfactory-h.html index d659e693..69f864b8 100644 --- a/doc/html/qsqleditorfactory-h.html +++ b/doc/html/qsqleditorfactory-h.html @@ -53,7 +53,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsqlerror-h.html b/doc/html/qsqlerror-h.html index e85fa1d9..3254db8e 100644 --- a/doc/html/qsqlerror-h.html +++ b/doc/html/qsqlerror-h.html @@ -53,7 +53,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsqlfield-h.html b/doc/html/qsqlfield-h.html index 515c880a..3a838e14 100644 --- a/doc/html/qsqlfield-h.html +++ b/doc/html/qsqlfield-h.html @@ -53,7 +53,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -150,7 +150,7 @@ class TQM_EXPORT_SQL TQSqlFieldInfo public: TQSqlFieldInfo( const TQString& name = TQString::null, TQVariant::Type typ = TQVariant::Invalid, - int retquired = -1, + int required = -1, int len = -1, int prec = -1, const TQVariant& defValue = TQVariant(), diff --git a/doc/html/qsqlfieldinfo.html b/doc/html/qsqlfieldinfo.html index 882010ac..72e3f93f 100644 --- a/doc/html/qsqlfieldinfo.html +++ b/doc/html/qsqlfieldinfo.html @@ -37,7 +37,7 @@ body { background: #ffffff; color: black; } <p><a href="qsqlfieldinfo-members.html">List of all member functions.</a> <h2>Public Members</h2> <ul> -<li class=fn><a href="#TQSqlFieldInfo"><b>TQSqlFieldInfo</b></a> ( const TQString & name = TQString::null, TQVariant::Type typ = TQVariant::Invalid, int retquired = -1, int len = -1, int prec = -1, const TQVariant & defValue = TQVariant ( ), int typeID = 0, bool generated = TRUE, bool trim = FALSE, bool calculated = FALSE )</li> +<li class=fn><a href="#TQSqlFieldInfo"><b>TQSqlFieldInfo</b></a> ( const TQString & name = TQString::null, TQVariant::Type typ = TQVariant::Invalid, int required = -1, int len = -1, int prec = -1, const TQVariant & defValue = TQVariant ( ), int typeID = 0, bool generated = TRUE, bool trim = FALSE, bool calculated = FALSE )</li> <li class=fn><a href="#TQSqlFieldInfo-2"><b>TQSqlFieldInfo</b></a> ( const TQSqlFieldInfo & other )</li> <li class=fn><a href="#TQSqlFieldInfo-3"><b>TQSqlFieldInfo</b></a> ( const TQSqlField & other, bool generated = TRUE )</li> <li class=fn>virtual <a href="#~TQSqlFieldInfo"><b>~TQSqlFieldInfo</b></a> ()</li> @@ -72,15 +72,15 @@ using <a href="#isRequired">isRequired</a>(), <a href="#type">type</a>(), <a hre <p>See also <a href="database.html">Database Classes</a>. <hr><h2>Member Function Documentation</h2> -<h3 class=fn><a name="TQSqlFieldInfo"></a>TQSqlFieldInfo::TQSqlFieldInfo ( const <a href="qstring.html">TQString</a> & name = TQString::null, <a href="qvariant.html#Type-enum">TQVariant::Type</a> typ = TQVariant::Invalid, int retquired = -1, int len = -1, int prec = -1, const <a href="qvariant.html">TQVariant</a> & defValue = TQVariant ( ), int typeID = 0, bool generated = TRUE, bool trim = FALSE, bool calculated = FALSE ) +<h3 class=fn><a name="TQSqlFieldInfo"></a>TQSqlFieldInfo::TQSqlFieldInfo ( const <a href="qstring.html">TQString</a> & name = TQString::null, <a href="qvariant.html#Type-enum">TQVariant::Type</a> typ = TQVariant::Invalid, int required = -1, int len = -1, int prec = -1, const <a href="qvariant.html">TQVariant</a> & defValue = TQVariant ( ), int typeID = 0, bool generated = TRUE, bool trim = FALSE, bool calculated = FALSE ) </h3> Constructs a TQSqlFieldInfo with the following parameters: <center><table cellpadding="4" cellspacing="2" border="0"> <tr bgcolor="#f0f0f0"> <td valign="top"><em>name</em> <td valign="top">the name of the field. <tr bgcolor="#d0d0d0"> <td valign="top"><em>typ</em> <td valign="top">the field's type in a <a href="qvariant.html">TQVariant</a>. -<tr bgcolor="#f0f0f0"> <td valign="top"><em>retquired</em> <td valign="top">greater than 0 if the field is retquired, 0 +<tr bgcolor="#f0f0f0"> <td valign="top"><em>required</em> <td valign="top">greater than 0 if the field is required, 0 if its value can be NULL and less than 0 if it cannot be -determined whether the field is retquired or not. +determined whether the field is required or not. <tr bgcolor="#d0d0d0"> <td valign="top"><em>len</em> <td valign="top">the length of the field. Note that for non-character types some databases return either the length in bytes or the number of digits. -1 signifies that the length cannot @@ -137,10 +137,10 @@ SQL statments, e.g. in <a href="qsqlcursor.html">TQSqlCursor</a>; otherwise retu <h3 class=fn>int <a name="isRequired"></a>TQSqlFieldInfo::isRequired () const </h3> -Returns a value greater than 0 if the field is retquired (NULL -values are not allowed), 0 if it isn't retquired (NULL values are +Returns a value greater than 0 if the field is required (NULL +values are not allowed), 0 if it isn't required (NULL values are allowed) or less than 0 if it cannot be determined whether the -field is retquired or not. +field is required or not. <h3 class=fn>bool <a name="isTrim"></a>TQSqlFieldInfo::isTrim () const </h3> diff --git a/doc/html/qsqlform-h.html b/doc/html/qsqlform-h.html index 8d403ef5..4011d871 100644 --- a/doc/html/qsqlform-h.html +++ b/doc/html/qsqlform-h.html @@ -53,7 +53,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsqlindex-h.html b/doc/html/qsqlindex-h.html index 2294d476..d54869c9 100644 --- a/doc/html/qsqlindex-h.html +++ b/doc/html/qsqlindex-h.html @@ -53,7 +53,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsqlpropertymap-h.html b/doc/html/qsqlpropertymap-h.html index 5c70e70e..33977c94 100644 --- a/doc/html/qsqlpropertymap-h.html +++ b/doc/html/qsqlpropertymap-h.html @@ -53,7 +53,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsqlquery-h.html b/doc/html/qsqlquery-h.html index e963f9b3..b9a52bbd 100644 --- a/doc/html/qsqlquery-h.html +++ b/doc/html/qsqlquery-h.html @@ -53,7 +53,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsqlquery.html b/doc/html/qsqlquery.html index e5400112..373f0ad1 100644 --- a/doc/html/qsqlquery.html +++ b/doc/html/qsqlquery.html @@ -138,13 +138,13 @@ by name. (The <a href="qsqlcursor.html">TQSqlCursor</a> class provides a higher- with field access by name and automatic SQL generation.) <p> TQSqlQuery 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 retquired +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 retquires that the database supports prepared +placeholders, which requires that the database supports prepared queries. <p> Oracle databases identify placeholders by using a colon-name syntax, e.g <tt>:name</tt>. ODBC simply uses <tt>?</tt> characters. TQt diff --git a/doc/html/qsqlrecord-h.html b/doc/html/qsqlrecord-h.html index 1726ef81..9fb20a03 100644 --- a/doc/html/qsqlrecord-h.html +++ b/doc/html/qsqlrecord-h.html @@ -53,7 +53,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsqlresult-h.html b/doc/html/qsqlresult-h.html index 64176b7e..e94d332e 100644 --- a/doc/html/qsqlresult-h.html +++ b/doc/html/qsqlresult-h.html @@ -53,7 +53,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsqlselectcursor-h.html b/doc/html/qsqlselectcursor-h.html index 63c26147..cfee37b3 100644 --- a/doc/html/qsqlselectcursor-h.html +++ b/doc/html/qsqlselectcursor-h.html @@ -53,7 +53,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qstatusbar-h.html b/doc/html/qstatusbar-h.html index b189a627..09173a0c 100644 --- a/doc/html/qstatusbar-h.html +++ b/doc/html/qstatusbar-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qstring-h.html b/doc/html/qstring-h.html index 34db545f..529258b2 100644 --- a/doc/html/qstring-h.html +++ b/doc/html/qstring-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qstring.html b/doc/html/qstring.html index a405751f..c6e26866 100644 --- a/doc/html/qstring.html +++ b/doc/html/qstring.html @@ -255,7 +255,7 @@ C-style '\0'-terminated ASCII string. It is legal for the <tt>const char *</ classic C strings into a TQString will not copy the terminating '\0' character. The <a href="qchar.html">TQChar</a> array of the TQString (as returned by <a href="#unicode">unicode</a>()) is generally not terminated by a '\0'. If you need to -pass a TQString to a function that retquires a C '\0'-terminated +pass a TQString to a function that requires a C '\0'-terminated string use <a href="#latin1">latin1</a>(). <p> <!-- index TQString::null --><a name="TQString-null"></a>A TQString that has not been assigned to anything is <em>null</em>, i.e. both the length and data pointer is 0. A TQString that references @@ -693,7 +693,7 @@ for experimental and illustrative purposes only. It is mainly of interest to those experimenting with Arabic and other composition-rich texts. <p> Applies possible ligatures to a TQString. Useful when -composition-rich text retquires rendering with glyph-poor fonts, +composition-rich text requires rendering with glyph-poor fonts, but it also makes compositions such as <a href="qchar.html">TQChar</a>(0x0041) ('A') and TQChar(0x0308) (Unicode accent diaresis), giving TQChar(0x00c4) (German A Umlaut). diff --git a/doc/html/qstringlist-h.html b/doc/html/qstringlist-h.html index 53a15269..ac1cdc40 100644 --- a/doc/html/qstringlist-h.html +++ b/doc/html/qstringlist-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qstringlist.html b/doc/html/qstringlist.html index 21e5cadd..18ecd96d 100644 --- a/doc/html/qstringlist.html +++ b/doc/html/qstringlist.html @@ -149,7 +149,7 @@ acts like a <a href="shclass.html#deep-copy">deep copy</a>, for example, if this one or some other list referencing the same shared data is modified, the modifying list first makes a copy, i.e. copy-on-write. -In a threaded environment you may retquire a real deep copy +In a threaded environment you may require a real deep copy . <h3 class=fn><a name="TQStringList-3"></a>TQStringList::TQStringList ( const <a href="qvaluelist.html">TQValueList</a><TQString> & l ) diff --git a/doc/html/qstrlist-h.html b/doc/html/qstrlist-h.html index 32a2e6ed..980d5e07 100644 --- a/doc/html/qstrlist-h.html +++ b/doc/html/qstrlist-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qstyle-h.html b/doc/html/qstyle-h.html index cea27dd0..d8baefa5 100644 --- a/doc/html/qstyle-h.html +++ b/doc/html/qstyle-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qstyle.html b/doc/html/qstyle.html index 3d91dd2a..fd87e9a0 100644 --- a/doc/html/qstyle.html +++ b/doc/html/qstyle.html @@ -231,7 +231,7 @@ button is down. <li><tt>TQStyle::PM_SpinBoxFrameWidth</tt> - frame width of a spin box. <li><tt>TQStyle::PM_MDIFrameWidth</tt> - frame width of an MDI window. <li><tt>TQStyle::PM_MDIMinimizedWidth</tt> - width of a minimized MSI window. -<li><tt>TQStyle::PM_MaximumDragDistance</tt> - Some feels retquire the scrollbar or +<li><tt>TQStyle::PM_MaximumDragDistance</tt> - Some feels require the scrollbar or other sliders to jump back to the original position when the mouse pointer is too far away while dragging. A value of -1 disables this behavior. @@ -669,7 +669,7 @@ ComplexControls. <p> The <em>widget</em> argument is a pointer to a <a href="qwidget.html">TQWidget</a> or one of its subclasses. The widget can be cast to the appropriate type based on the value of <em>control</em>. The <em>opt</em> argument can be used to -pass extra information retquired when drawing the ComplexControl. +pass extra information required when drawing the ComplexControl. Note that <em>opt</em> may be the default value even for ComplexControls that can make use of the extra options. See the table below for the appropriate <em>widget</em> and <em>opt</em> usage: @@ -754,7 +754,7 @@ ControlElements. <p> The <em>widget</em> argument is a pointer to a <a href="qwidget.html">TQWidget</a> or one of its subclasses. The widget can be cast to the appropriate type based on the value of <em>element</em>. The <em>opt</em> argument can be used to -pass extra information retquired when drawing the ControlElement. +pass extra information required when drawing the ControlElement. Note that <em>opt</em> may be the default value even for ControlElements that can make use of the extra options. See the table below for the appropriate <em>widget</em> and <em>opt</em> usage: @@ -1026,9 +1026,9 @@ This is an overloaded member function, provided for convenience. It behaves esse <h3 class=fn>void <a name="polish-3"></a>TQStyle::polish ( <a href="qpalette.html">TQPalette</a> & )<tt> [virtual]</tt> </h3> This is an overloaded member function, provided for convenience. It behaves essentially like the above function. -<p> The style may have certain retquirements for color palettes. In +<p> The style may have certain requirements for color palettes. In this function it has the chance to change the palette according to -these retquirements. +these requirements. <p> <p>See also <a href="qpalette.html">TQPalette</a> and <a href="qapplication.html#setPalette">TQApplication::setPalette</a>(). <h3 class=fn>void <a name="polishPopupMenu"></a>TQStyle::polishPopupMenu ( <a href="qpopupmenu.html">TQPopupMenu</a> * )<tt> [pure virtual]</tt> @@ -1044,7 +1044,7 @@ checkable by default (<a href="qpopupmenu.html#setCheckable">TQPopupMenu::setChe <p> Returns the SubControl for <em>widget</em> at the point <em>pos</em>. The <em>widget</em> argument is a pointer to a <a href="qwidget.html">TQWidget</a> or one of its subclasses. The widget can be cast to the appropriate type based on the value of <em>control</em>. The <em>opt</em> argument can be used to -pass extra information retquired when drawing the ComplexControl. +pass extra information required when drawing the ComplexControl. Note that <em>opt</em> may be the default value even for ComplexControls that can make use of the extra options. See <a href="#drawComplexControl">drawComplexControl</a>() for an explanation of the <em>widget</em> and <em>opt</em> arguments. @@ -1062,7 +1062,7 @@ logical coordinates. <p> The <em>widget</em> argument is a pointer to a <a href="qwidget.html">TQWidget</a> or one of its subclasses. The widget can be cast to the appropriate type based on the value of <em>control</em>. The <em>opt</em> argument can be used to -pass extra information retquired when drawing the ComplexControl. +pass extra information required when drawing the ComplexControl. Note that <em>opt</em> may be the default value even for ComplexControls that can make use of the extra options. See <a href="#drawComplexControl">drawComplexControl</a>() for an explanation of the <em>widget</em> and <em>opt</em> arguments. @@ -1080,7 +1080,7 @@ for an explanation of the <em>widget</em> and <em>opt</em> arguments. <p> The <em>widget</em> argument is a pointer to a <a href="qwidget.html">TQWidget</a> or one of its subclasses. The widget can be cast to the appropriate type based on the value of <em>contents</em>. The <em>opt</em> argument can be used to -pass extra information retquired when calculating the size. Note +pass extra information required when calculating the size. Note that <em>opt</em> may be the default value even for ContentsTypes that can make use of the extra options. See the table below for the appropriate <em>widget</em> and <em>opt</em> usage: @@ -1114,7 +1114,7 @@ allow for future enhancements. </h3> <p> Returns a pixmap for <em>stylepixmap</em>. -<p> The <em>opt</em> argument can be used to pass extra information retquired +<p> The <em>opt</em> argument can be used to pass extra information required when drawing the ControlElement. Note that <em>opt</em> may be the default value even for StylePixmaps that can make use of the extra options. Currently, the <em>opt</em> argument is unused. diff --git a/doc/html/qstylefactory-h.html b/doc/html/qstylefactory-h.html index 64a7058e..b29e3415 100644 --- a/doc/html/qstylefactory-h.html +++ b/doc/html/qstylefactory-h.html @@ -52,7 +52,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qstyleoption.html b/doc/html/qstyleoption.html index 15107868..3575890a 100644 --- a/doc/html/qstyleoption.html +++ b/doc/html/qstyleoption.html @@ -76,7 +76,7 @@ body { background: #ffffff; color: black; } The TQStyleOption class specifies optional parameters for <a href="qstyle.html">TQStyle</a> functions. <p> Some TQStyle functions take an optional argument specifying extra -information that is retquired for a paritical primitive or control. +information that is required for a paritical primitive or control. So that the TQStyle class can be extended, TQStyleOption is used to provide a variable-argument for these options. <p> The TQStyleOption class has constructors for each type of optional diff --git a/doc/html/qstyleplugin-h.html b/doc/html/qstyleplugin-h.html index 7ca607f9..9d7c45f2 100644 --- a/doc/html/qstyleplugin-h.html +++ b/doc/html/qstyleplugin-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qstyleplugin.html b/doc/html/qstyleplugin.html index 1380b87d..c54424e2 100644 --- a/doc/html/qstyleplugin.html +++ b/doc/html/qstyleplugin.html @@ -73,7 +73,7 @@ automatically when it is no longer used. </h3> <p> Creates and returns a <a href="qstyle.html">TQStyle</a> object for the style key <em>key</em>. The -style key is usually the class name of the retquired style. +style key is usually the class name of the required style. <p> <p>See also <a href="#keys">keys</a>(). <h3 class=fn><a href="qstringlist.html">TQStringList</a> <a name="keys"></a>TQStylePlugin::keys () const<tt> [pure virtual]</tt> diff --git a/doc/html/qstylesheet-h.html b/doc/html/qstylesheet-h.html index 696db736..8651b435 100644 --- a/doc/html/qstylesheet-h.html +++ b/doc/html/qstylesheet-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsyntaxhighlighter-h.html b/doc/html/qsyntaxhighlighter-h.html index b2a27e91..cf89657f 100644 --- a/doc/html/qsyntaxhighlighter-h.html +++ b/doc/html/qsyntaxhighlighter-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qsyntaxhighlighter.html b/doc/html/qsyntaxhighlighter.html index 6d4add4c..196d1d57 100644 --- a/doc/html/qsyntaxhighlighter.html +++ b/doc/html/qsyntaxhighlighter.html @@ -94,7 +94,7 @@ paragraph is currently highlighted. i.e. on paragraphs which have changed. <p> In your reimplementation you should parse the paragraph's <em>text</em> and call <a href="#setFormat">setFormat</a>() as often as necessary to apply any font and -color changes that you retquire. Your function must return a value +color changes that you require. Your function must return a value which indicates the paragraph's end state: see below. <p> Some syntaxes can have constructs that span paragraphs. For example, a C++ syntax highlighter should be able to cope with diff --git a/doc/html/qt-template-lib.html b/doc/html/qt-template-lib.html index e4f75444..68f44377 100644 --- a/doc/html/qt-template-lib.html +++ b/doc/html/qt-template-lib.html @@ -61,7 +61,7 @@ other TQPtrCollection based containers, provides far more sanity checking than a speed-optimized value based container. <p> If you have objects that implement value semantics, and the STL is not available on your target platform, the TQt Template Library can be used -instead. Value semantics retquire at least: +instead. Value semantics require at least: <ul> <li> a copy constructor; <li> an assignment operator; @@ -117,7 +117,7 @@ operator (it++, it--), since the former is slightly faster. <p> There are two kind of iterators, the volatile iterator shown in the examples above and a version that returns a const reference to its -current object, the ConstIterator. Const iterators are retquired +current object, the ConstIterator. Const iterators are required whenever the container itself is const, such as a member variable inside a const function. Assigning a ConstIterator to a normal Iterator is not allowed as it would violate const semantics. diff --git a/doc/html/qtabbar-h.html b/doc/html/qtabbar-h.html index ee53fb77..af470c8b 100644 --- a/doc/html/qtabbar-h.html +++ b/doc/html/qtabbar-h.html @@ -52,7 +52,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qtabdialog-h.html b/doc/html/qtabdialog-h.html index 180edd67..fbf4f489 100644 --- a/doc/html/qtabdialog-h.html +++ b/doc/html/qtabdialog-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qtable-h.html b/doc/html/qtable-h.html index 16e43523..6af76807 100644 --- a/doc/html/qtable-h.html +++ b/doc/html/qtable-h.html @@ -53,7 +53,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qtable.html b/doc/html/qtable.html index c077e526..7031ac02 100644 --- a/doc/html/qtable.html +++ b/doc/html/qtable.html @@ -302,19 +302,19 @@ identifying a particular cell. <p> There are two approaches to populating the table's cells. The first and simplest approach is to use TQTableItems or <a href="qtableitem.html">TQTableItem</a> subclasses. The second approach doesn't use TQTableItems at all -which is useful for very large sparse tables but retquires you to +which is useful for very large sparse tables but requires you to reimplement a number of functions. We'll look at each approach in turn. <p> To put a string in a cell use <a href="#setText">setText</a>(). This function will create a new TQTableItem for the cell if one doesn't already exist, and displays the text in it. By default the table item's widget will be a <a href="qlineedit.html">TQLineEdit</a>. A pixmap may be put in a cell with <a href="#setPixmap">setPixmap</a>(), -which also creates a table item if retquired. A cell may contain <em>both</em> a pixmap and text; the pixmap is displayed to the left of the +which also creates a table item if required. A cell may contain <em>both</em> a pixmap and text; the pixmap is displayed to the left of the text. Another approach is to construct a TQTableItem or TQTableItem subclass, set its properties, then insert it into a cell with <a href="#setItem">setItem</a>(). <p> If you want cells which contain comboboxes use the <a href="qcombotableitem.html">TQComboTableItem</a> -class. Similarly if you retquire cells containing checkboxes use +class. Similarly if you require cells containing checkboxes use the <a href="qchecktableitem.html">TQCheckTableItem</a> class. These table items look and behave just like the combobox or checkbox widgets but consume far less memory. <p> @@ -350,7 +350,7 @@ approach. The cell's widget (if there is one) can be removed with <a name="1-2-1"></a><p> For large, sparse, tables using TQTableItems or other widgets is inefficient. The solution is to <em>draw</em> the cell as it should appear and to create and destroy cell editors on demand. -<p> This approach retquires that you reimplement various functions. +<p> This approach requires that you reimplement various functions. Reimplement <a href="#paintCell">paintCell</a>() to display your data, and <a href="#createEditor">createEditor</a>() and <a href="#setCellContentFromEditor">setCellContentFromEditor</a>() to support in-place editing. It is very important to reimplement <a href="#resizeData">resizeData</a>() to have no diff --git a/doc/html/qtabwidget-h.html b/doc/html/qtabwidget-h.html index c330e15e..c2a0988f 100644 --- a/doc/html/qtabwidget-h.html +++ b/doc/html/qtabwidget-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qtextbrowser-h.html b/doc/html/qtextbrowser-h.html index a6f6642d..acc5c998 100644 --- a/doc/html/qtextbrowser-h.html +++ b/doc/html/qtextbrowser-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qtextcodec-h.html b/doc/html/qtextcodec-h.html index 6b93949d..e1b47a09 100644 --- a/doc/html/qtextcodec-h.html +++ b/doc/html/qtextcodec-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qtextcodec.html b/doc/html/qtextcodec.html index b2345532..c9d9f04e 100644 --- a/doc/html/qtextcodec.html +++ b/doc/html/qtextcodec.html @@ -196,7 +196,7 @@ ones. as a plugin; see the <a href="plugins-howto.html">plugin documentation</a> for more details. <p> The abstract virtual functions describe the encoder to the -system and the coder is used as retquired in the different +system and the coder is used as required in the different text file formats supported by <a href="qtextstream.html">TQTextStream</a>, and under X11, for the locale-specific character input and output. <p> To add support for another 8-bit encoding to TQt, make a subclass @@ -220,8 +220,8 @@ bytes. For such encodings, you must implement: </pre> Return a <a href="qtextdecoder.html">TQTextDecoder</a> that remembers incomplete multi-byte sequence -prefixes or other retquired state. -<p> If the encoding does <em>not</em> retquire state, you should implement: +prefixes or other required state. +<p> If the encoding does <em>not</em> require state, you should implement: <p> <pre> <a href="qstring.html">TQString</a> toUnicode(const char* chars, int len) const </pre> diff --git a/doc/html/qtextcodecplugin-h.html b/doc/html/qtextcodecplugin-h.html index d98d65f4..89f6cd65 100644 --- a/doc/html/qtextcodecplugin-h.html +++ b/doc/html/qtextcodecplugin-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qtextdecoder.html b/doc/html/qtextdecoder.html index 06bbb8f3..70ce4e8e 100644 --- a/doc/html/qtextdecoder.html +++ b/doc/html/qtextdecoder.html @@ -48,7 +48,7 @@ The TQTextDecoder class provides a state-based decoder. <p> The decoder converts a text format into Unicode, remembering any -state that is retquired between calls. +state that is required between calls. <p> <p>See also <a href="qtextcodec.html#makeEncoder">TQTextCodec::makeEncoder</a>() and <a href="i18n.html">Internationalization with TQt</a>. <hr><h2>Member Function Documentation</h2> diff --git a/doc/html/qtextedit-h.html b/doc/html/qtextedit-h.html index 1133b5e7..7c7a21e8 100644 --- a/doc/html/qtextedit-h.html +++ b/doc/html/qtextedit-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qtextedit.html b/doc/html/qtextedit.html index 5b632601..45247a4a 100644 --- a/doc/html/qtextedit.html +++ b/doc/html/qtextedit.html @@ -1154,7 +1154,7 @@ the HTML anchor tag, e.g. <tt><a name="target"></tt>. <h3 class=fn>void <a name="scrollToBottom"></a>TQTextEdit::scrollToBottom ()<tt> [virtual slot]</tt> </h3> Scrolls to the bottom of the document and does formatting if -retquired. +required. <h3 class=fn>void <a name="selectAll"></a>TQTextEdit::selectAll ( bool select = TRUE )<tt> [virtual slot]</tt> </h3> diff --git a/doc/html/qtextencoder.html b/doc/html/qtextencoder.html index 69db0084..1a663736 100644 --- a/doc/html/qtextencoder.html +++ b/doc/html/qtextencoder.html @@ -48,7 +48,7 @@ The TQTextEncoder class provides a state-based encoder. <p> The encoder converts Unicode into another format, remembering any -state that is retquired between calls. +state that is required between calls. <p> <p>See also <a href="qtextcodec.html#makeEncoder">TQTextCodec::makeEncoder</a>() and <a href="i18n.html">Internationalization with TQt</a>. <hr><h2>Member Function Documentation</h2> diff --git a/doc/html/qtextstream-h.html b/doc/html/qtextstream-h.html index 1d381671..309eaabf 100644 --- a/doc/html/qtextstream-h.html +++ b/doc/html/qtextstream-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qtextview-h.html b/doc/html/qtextview-h.html index f9589ef4..7ee64da4 100644 --- a/doc/html/qtextview-h.html +++ b/doc/html/qtextview-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qthread-h.html b/doc/html/qthread-h.html index b67a9fff..adc8766b 100644 --- a/doc/html/qthread-h.html +++ b/doc/html/qthread-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qthreadstorage-h.html b/doc/html/qthreadstorage-h.html index 2ebd20cd..f12b062a 100644 --- a/doc/html/qthreadstorage-h.html +++ b/doc/html/qthreadstorage-h.html @@ -52,7 +52,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qtimer-h.html b/doc/html/qtimer-h.html index c1d7277f..149bb2d5 100644 --- a/doc/html/qtimer-h.html +++ b/doc/html/qtimer-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qtoolbar-h.html b/doc/html/qtoolbar-h.html index fd8ac53f..2d7fbfc4 100644 --- a/doc/html/qtoolbar-h.html +++ b/doc/html/qtoolbar-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qtoolbox-h.html b/doc/html/qtoolbox-h.html index b04fca16..88f5ecf4 100644 --- a/doc/html/qtoolbox-h.html +++ b/doc/html/qtoolbox-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qtoolbutton-h.html b/doc/html/qtoolbutton-h.html index b7952e3c..4dba9eaf 100644 --- a/doc/html/qtoolbutton-h.html +++ b/doc/html/qtoolbutton-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qtooltip-h.html b/doc/html/qtooltip-h.html index 44bc63b1..201e17ca 100644 --- a/doc/html/qtooltip-h.html +++ b/doc/html/qtooltip-h.html @@ -52,7 +52,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qtooltip.html b/doc/html/qtooltip.html index 4ddd9b9e..8082c132 100644 --- a/doc/html/qtooltip.html +++ b/doc/html/qtooltip.html @@ -127,7 +127,7 @@ function <a href="#add">TQToolTip::add</a>() with the widget, rectangle and tip arguments. (See the <a href="tooltip-example.html">tooltip/tooltip.cpp</a> example.) Again, you can supply a <tt>TQToolTipGroup *</tt> and another text if you want. <p> Both of these are one-liners and cover the majority of cases. The -third and most general way to use TQToolTip retquires you to +third and most general way to use TQToolTip requires you to reimplement a pure virtual function to decide whether to pop up a tool tip. The <a href="tooltip-example.html">tooltip/tooltip.cpp</a> example demonstrates this too. This mode can be used to implement tips for text that can diff --git a/doc/html/qtranslator-h.html b/doc/html/qtranslator-h.html index 7e845d2c..860537f2 100644 --- a/doc/html/qtranslator-h.html +++ b/doc/html/qtranslator-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qtranslator.html b/doc/html/qtranslator.html index 512bd88e..4ed8ee49 100644 --- a/doc/html/qtranslator.html +++ b/doc/html/qtranslator.html @@ -137,7 +137,7 @@ name; there would normally be no comment, and the translated text would be "Anuluj". <p> But it's not always so simple. The Spanish version of a printer dialog with settings for two-sided printing and binding would -probably retquire both "Activado" and "Activada" as translations +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 diff --git a/doc/html/qtsciicodec-h.html b/doc/html/qtsciicodec-h.html index 1c8f4f54..a04e7730 100644 --- a/doc/html/qtsciicodec-h.html +++ b/doc/html/qtsciicodec-h.html @@ -52,7 +52,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qurl-h.html b/doc/html/qurl-h.html index 397bc5ee..ff740ae6 100644 --- a/doc/html/qurl-h.html +++ b/doc/html/qurl-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qurl.html b/doc/html/qurl.html index 8464f882..1e0d1524 100644 --- a/doc/html/qurl.html +++ b/doc/html/qurl.html @@ -127,7 +127,7 @@ parse, decode, encode, etc. <p> The individual parts of a URL can be set with <a href="#setProtocol">setProtocol</a>(), <a href="#setHost">setHost</a>(), <a href="#setPort">setPort</a>(), <a href="#setPath">setPath</a>(), <a href="#setFileName">setFileName</a>(), <a href="#setRef">setRef</a>() and <a href="#setQuery">setQuery</a>(). A URL could contain, for example, an ftp address which -retquires a user name and password; these can be set with <a href="#setUser">setUser</a>() +requires a user name and password; these can be set with <a href="#setUser">setUser</a>() and <a href="#setPassword">setPassword</a>(). <p> Because path is always encoded internally you must not use "%00" in the path, although this is okay (but not recommended) for the diff --git a/doc/html/qurlinfo-h.html b/doc/html/qurlinfo-h.html index ccb38487..69422b43 100644 --- a/doc/html/qurlinfo-h.html +++ b/doc/html/qurlinfo-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qurloperator-h.html b/doc/html/qurloperator-h.html index cf302d9d..533689f6 100644 --- a/doc/html/qurloperator-h.html +++ b/doc/html/qurloperator-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/quuid-h.html b/doc/html/quuid-h.html index 394ade8f..c23e5bf2 100644 --- a/doc/html/quuid-h.html +++ b/doc/html/quuid-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qvalidator-h.html b/doc/html/qvalidator-h.html index b30e3e4c..fae4ba70 100644 --- a/doc/html/qvalidator-h.html +++ b/doc/html/qvalidator-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qvalidator.html b/doc/html/qvalidator.html index 78766fed..38ccdd97 100644 --- a/doc/html/qvalidator.html +++ b/doc/html/qvalidator.html @@ -59,7 +59,7 @@ TQValidator. The class has two virtual functions: <a href="#validate">validate</ <p> <a href="#validate">validate</a>() must be implemented by every subclass. It returns <a href="#State-enum">Invalid</a>, <a href="#State-enum">Intermediate</a> or <a href="#State-enum">Acceptable</a> depending on whether its argument is valid (for the subclass's definition of valid). -<p> These three states retquire some explanation. An <a href="#State-enum">Invalid</a> string +<p> These three states require some explanation. An <a href="#State-enum">Invalid</a> string is <em>clearly</em> invalid. <a href="#State-enum">Intermediate</a> is less obvious: the concept of validity is slippery when the string is incomplete (still being edited). TQValidator defines <a href="#State-enum">Intermediate</a> as the diff --git a/doc/html/qvaluelist-h.html b/doc/html/qvaluelist-h.html index 98d304e7..bed8835e 100644 --- a/doc/html/qvaluelist-h.html +++ b/doc/html/qvaluelist-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qvaluelist.html b/doc/html/qvaluelist.html index 8407b3dd..8ed3acc7 100644 --- a/doc/html/qvaluelist.html +++ b/doc/html/qvaluelist.html @@ -148,7 +148,7 @@ value the class must provide: <p> 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. -<p> In addition, some compilers (e.g. Sun CC) might retquire that the +<p> In addition, some compilers (e.g. Sun CC) might require that the class provides an equality operator (<a href="#operator-eq-eq">operator==</a>()). <p> TQValueList's function naming is consistent with the other TQt classes (e.g. <a href="#count">count</a>(), <a href="#isEmpty">isEmpty</a>()). TQValueList also provides extra diff --git a/doc/html/qvaluestack-h.html b/doc/html/qvaluestack-h.html index 6010eed6..cbbdf765 100644 --- a/doc/html/qvaluestack-h.html +++ b/doc/html/qvaluestack-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qvaluevector-h.html b/doc/html/qvaluevector-h.html index f80ff85f..a2916539 100644 --- a/doc/html/qvaluevector-h.html +++ b/doc/html/qvaluevector-h.html @@ -52,7 +52,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qvaluevector.html b/doc/html/qvaluevector.html index fadb68f0..e33fb761 100644 --- a/doc/html/qvaluevector.html +++ b/doc/html/qvaluevector.html @@ -318,7 +318,7 @@ For example with qHeapSort(): </pre> <p> TQValueVector stores its elements in contiguous memory. This means -that you can use a TQValueVector in any situation that retquires an +that you can use a TQValueVector in any situation that requires an array. <p>See also <a href="qtl.html">TQt Template Library Classes</a>, <a href="shared.html">Implicitly and Explicitly Shared Classes</a>, and <a href="tools.html">Non-GUI Classes</a>. diff --git a/doc/html/qvariant-h.html b/doc/html/qvariant-h.html index f009f3e9..93f402b2 100644 --- a/doc/html/qvariant-h.html +++ b/doc/html/qvariant-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qvbox-h.html b/doc/html/qvbox-h.html index 76a18163..9aae8df7 100644 --- a/doc/html/qvbox-h.html +++ b/doc/html/qvbox-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qvbuttongroup-h.html b/doc/html/qvbuttongroup-h.html index d10597fd..c2312bb1 100644 --- a/doc/html/qvbuttongroup-h.html +++ b/doc/html/qvbuttongroup-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qvgroupbox-h.html b/doc/html/qvgroupbox-h.html index c351dcab..a8135997 100644 --- a/doc/html/qvgroupbox-h.html +++ b/doc/html/qvgroupbox-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qwaitcondition-h.html b/doc/html/qwaitcondition-h.html index 39faea56..759369fd 100644 --- a/doc/html/qwaitcondition-h.html +++ b/doc/html/qwaitcondition-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qwhatsthis-h.html b/doc/html/qwhatsthis-h.html index 68af6fc5..9d132225 100644 --- a/doc/html/qwhatsthis-h.html +++ b/doc/html/qwhatsthis-h.html @@ -52,7 +52,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qwidget-h.html b/doc/html/qwidget-h.html index 10aa5595..fbd46649 100644 --- a/doc/html/qwidget-h.html +++ b/doc/html/qwidget-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qwidget.html b/doc/html/qwidget.html index 2d76389b..a027785c 100644 --- a/doc/html/qwidget.html +++ b/doc/html/qwidget.html @@ -2585,7 +2585,7 @@ that the auto mask calculation works, you should add: <p> at the end of your event handlers. This is true for all member functions that change the appearance of the widget in a way that -retquires a recalculation of the mask. +requires a recalculation of the mask. <p> While being a technically appealing concept, masks have a big drawback: when using complex masks that cannot be expressed easily with relatively simple regions, they can be very slow on some diff --git a/doc/html/qwidgetfactory-h.html b/doc/html/qwidgetfactory-h.html index 13bf5e9f..abda4c88 100644 --- a/doc/html/qwidgetfactory-h.html +++ b/doc/html/qwidgetfactory-h.html @@ -48,7 +48,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qwidgetplugin-h.html b/doc/html/qwidgetplugin-h.html index 397433e5..ee97f0ea 100644 --- a/doc/html/qwidgetplugin-h.html +++ b/doc/html/qwidgetplugin-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qwidgetplugin.html b/doc/html/qwidgetplugin.html index 87b4f72d..728dc7ad 100644 --- a/doc/html/qwidgetplugin.html +++ b/doc/html/qwidgetplugin.html @@ -84,7 +84,7 @@ automatically when it is no longer used. </h3> <p> Creates and returns a <a href="qwidget.html">TQWidget</a> object for the widget key <em>key</em>. -The widget key is the class name of the retquired widget. The <em>name</em> and <em>parent</em> arguments are passed to the custom widget's +The widget key is the class name of the required widget. The <em>name</em> and <em>parent</em> arguments are passed to the custom widget's constructor. <p> <p>See also <a href="#keys">keys</a>(). diff --git a/doc/html/qwidgetstack-h.html b/doc/html/qwidgetstack-h.html index d6570cd3..fae3e3ef 100644 --- a/doc/html/qwidgetstack-h.html +++ b/doc/html/qwidgetstack-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qwindowdefs-h.html b/doc/html/qwindowdefs-h.html index 1c3be79b..95055962 100644 --- a/doc/html/qwindowdefs-h.html +++ b/doc/html/qwindowdefs-h.html @@ -55,7 +55,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qwindowsstyle-h.html b/doc/html/qwindowsstyle-h.html index 5921b03a..dcdcfe6b 100644 --- a/doc/html/qwindowsstyle-h.html +++ b/doc/html/qwindowsstyle-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qwindowsystem_qws-h.html b/doc/html/qwindowsystem_qws-h.html index 7e46ef33..83b18d55 100644 --- a/doc/html/qwindowsystem_qws-h.html +++ b/doc/html/qwindowsystem_qws-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qwizard-h.html b/doc/html/qwizard-h.html index 9695054a..baf095fd 100644 --- a/doc/html/qwizard-h.html +++ b/doc/html/qwizard-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qwmatrix-h.html b/doc/html/qwmatrix-h.html index 6893311d..a625aa27 100644 --- a/doc/html/qwmatrix-h.html +++ b/doc/html/qwmatrix-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qworkspace-h.html b/doc/html/qworkspace-h.html index 9c8cadc4..d91abefc 100644 --- a/doc/html/qworkspace-h.html +++ b/doc/html/qworkspace-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qwsdecoration_qws-h.html b/doc/html/qwsdecoration_qws-h.html index f9516095..4f884ba6 100644 --- a/doc/html/qwsdecoration_qws-h.html +++ b/doc/html/qwsdecoration_qws-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qxml-h.html b/doc/html/qxml-h.html index efca6e7f..a3fccff6 100644 --- a/doc/html/qxml-h.html +++ b/doc/html/qxml-h.html @@ -54,7 +54,7 @@ body { background: #ffffff; color: black; } ** and the KDE Free TQt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/html/qxmldtdhandler.html b/doc/html/qxmldtdhandler.html index 6a6ad46a..971d7b7a 100644 --- a/doc/html/qxmldtdhandler.html +++ b/doc/html/qxmldtdhandler.html @@ -57,7 +57,7 @@ DTD content of XML data. entities, it can implement this interface and register an instance with <a href="qxmlreader.html#setDTDHandler">TQXmlReader::setDTDHandler</a>(). <p> Note that this interface includes only those DTD events that the -XML recommendation retquires processors to report, i.e. notation +XML recommendation requires processors to report, i.e. notation and unparsed entity declarations using <a href="#notationDecl">notationDecl</a>() and <a href="#unparsedEntityDecl">unparsedEntityDecl</a>() respectively. <p> See also the <a href="xml.html#sax2Intro">Introduction to SAX2</a>. diff --git a/doc/html/qxtwidget.html b/doc/html/qxtwidget.html index 46f5a182..c464a1d9 100644 --- a/doc/html/qxtwidget.html +++ b/doc/html/qxtwidget.html @@ -102,7 +102,7 @@ Constructs a TQXtWidget of the given <em>widget_class</em> called <em>name</em>. <p> Use this constructor to utilize Xt or <a href="motif-extension.html#Motif">Motif</a> widgets in a TQt application. The TQXtWidget looks and behaves like the Xt class, but can be used like any <a href="qwidget.html">TQWidget</a>. -<p> Note that Xt retquires that the most top level Xt widget is a shell. +<p> Note that Xt requires that the most top level Xt widget is a shell. This means, if <em>parent</em> is a TQXtWidget, the <em>widget_class</em> can be of any kind. If there isn't a parent or the parent is just a normal TQWidget, <em>widget_class</em> should be something like <tt>topLevelShellWidgetClass</tt>. diff --git a/doc/html/signalsandslots.html b/doc/html/signalsandslots.html index a3f18f2a..4cca6721 100644 --- a/doc/html/signalsandslots.html +++ b/doc/html/signalsandslots.html @@ -237,13 +237,13 @@ increased flexibility they provide, although the difference for real applications is insignificant. In general, emitting a signal that is connected to some slots, is approximately ten times slower than calling the receivers directly, with non-virtual function calls. This -is the overhead retquired to locate the connection object, to safely +is the overhead required to locate the connection object, to safely iterate over all connections (i.e. checking that subsequent receivers have not been destroyed during the emission) and to marshall any parameters in a generic fashion. While ten non-virtual function calls may sound like a lot, it's much less overhead than any 'new' or 'delete' operation, for example. As soon as you perform a string, -vector or list operation that behind the scene retquires 'new' or +vector or list operation that behind the scene requires 'new' or 'delete', the signals and slots overhead is only responsible for a very small proportion of the complete function call costs. The same is true whenever you do a system call in a slot; or indirectly call more diff --git a/doc/html/simple-application.html b/doc/html/simple-application.html index b029bc84..f9d0a045 100644 --- a/doc/html/simple-application.html +++ b/doc/html/simple-application.html @@ -307,7 +307,7 @@ will implement later. </pre> <p> Now that we have done the File menu we shift our focus back to the menu bar and insert a separator. From now on further menu bar entries -will be aligned to the right if the windows system style retquires it. +will be aligned to the right if the windows system style requires it. <p> <pre> <a href="qpopupmenu.html">TQPopupMenu</a> * help = new <a href="qpopupmenu.html">TQPopupMenu</a>( this ); <a href="qmainwindow.html#menuBar">menuBar</a>()->insertItem( "&Help", help ); diff --git a/doc/html/sql-driver.html b/doc/html/sql-driver.html index 03ea5800..2838e34e 100644 --- a/doc/html/sql-driver.html +++ b/doc/html/sql-driver.html @@ -105,7 +105,7 @@ instead of <tt>C:\program files\mysql</tt>. <p> Use the <tt>-qt-sql-<driver></tt> parameter to build the database driver statically into your TQt library or <tt>-plugin-sql-<driver></tt> to build the driver as a plugin. Look at the sections that follow for -additional information about retquired libraries. +additional information about required libraries. <p> <a name="buildingmanually"></a> <h2> Building the plugins manually </h2> @@ -169,7 +169,7 @@ encoding to communicate with the server. <p> <h4> BLOB/LOB support </h4> <a name="3-2-3"></a><p> Binary Large Objects (BLOBs) can be read and written, but be aware -that this process may retquire a lot of memory. +that this process may require a lot of memory. <p> Note that Oracle 9 doesn't support scrollable result sets with LOB columns, you have to use a forward only query to select LOB fields (see <a href="qsqlquery.html#setForwardOnly">TQSqlQuery::setForwardOnly</a>()). @@ -183,9 +183,9 @@ position the query on the last record and return TRUE, but subsequent calls to <a href="qsqlquery.html#value">TQSqlQuery::value</a>() will only return NULLs. <p> <h4> How to build the plugin on Unix/Linux </h4> -<a name="3-2-5"></a><p> All files retquired to build driver should ship with the standard Oracle +<a name="3-2-5"></a><p> All files required to build driver should ship with the standard Oracle Client install. -<p> Oracle library files retquired to build driver: +<p> Oracle library files required to build driver: <p> <ul> <li> <tt>libclntsh.so</tt> (all versions) <li> <tt>libwtc8.so</tt> (only Oracle 8) or <tt>libwtc9.so</tt> (only Oracle 9) @@ -257,7 +257,7 @@ then allows you to use these data sources in your TQt project. <p> On Windows systems after 95 an ODBC driver manager should be installed by default, for Unix systems there are some implementations which must be installed first. Note that every client that uses your application -is retquired to have an ODBC driver manager installed, otherwise the +is required to have an ODBC driver manager installed, otherwise the TQODBC3 plugin will not work. <p> Be aware that when connecting to an ODBC datasource you must pass in the name of the ODBC datasource to the <a href="qsqldatabase.html#setDatabaseName">TQSqlDatabase::setDatabaseName</a>() @@ -483,7 +483,7 @@ make Firebird databases. Interbase can either be used as a client/server or without a server operating on local files. The database file must exist before a connection can be established. -<p> Note that Interbase retquires you to specify the full path to the +<p> Note that Interbase requires you to specify the full path to the database file, no matter whether it is stored locally or on another server. <p> <pre> @@ -531,7 +531,7 @@ errors. Some compilers have tools to convert libraries, e.g. Borland ships the tool <tt>COFF2OMF.EXE</tt> to convert libraries that have been generated with Microsoft Visual C++. <p> If the compilation of a plugin succeeds but it cannot be loaded, -make sure that the following retquirements are met: +make sure that the following requirements are met: <p> <ul> <li> Ensure that you are using a shared TQt library; you cannot use the plugins with a static build. diff --git a/doc/html/sql.html b/doc/html/sql.html index 7be337f7..19db86b6 100644 --- a/doc/html/sql.html +++ b/doc/html/sql.html @@ -145,7 +145,7 @@ your TQt applications. This overview assumes that you have at least a basic knowledge of SQL. You should be able to understand simple <tt>SELECT</tt>, <tt>INSERT</tt>, <tt>UPDATE</tt> and <tt>DELETE</tt> commands. Although the <a href="qsqlcursor.html">TQSqlCursor</a> class provides an -interface to database browsing and editing that does not <em>retquire</em> a +interface to database browsing and editing that does not <em>require</em> a knowledge of SQL, a basic understanding of SQL is highly recommended. A standard text covering SQL databases is <em>An Introduction to Database Systems (7th ed.)</em> by C. J. Date, ISBN 0201385902. </blockquote> @@ -222,9 +222,9 @@ for more information). <a name="4"></a><p> At least one database connection must be created and opened before the <a href="qsqlquery.html">TQSqlQuery</a> or <a href="qsqlcursor.html">TQSqlCursor</a> classes can be used. <p> If the application only needs a single database connection, the <a href="qsqldatabase.html">TQSqlDatabase</a> class can create a connection which is used by default -for all SQL operations. If multiple database connections are retquired +for all SQL operations. If multiple database connections are required these can easily be set up. -<p> <a href="qsqldatabase.html">TQSqlDatabase</a> retquires the <a href="qsqldatabase-h.html">qsqldatabase.h</a> header file. +<p> <a href="qsqldatabase.html">TQSqlDatabase</a> requires the <a href="qsqldatabase-h.html">qsqldatabase.h</a> header file. <p> <a name="Connecting_to_a_Single_Database"></a> <h2> Connecting to a Single Database </h2> @@ -622,7 +622,7 @@ presented earlier. follows this one we show how to link widgets to database cursors. Once we have a knowledge of both cursors and data-aware widgets we can discuss <a href="#Subclassing_QSqlCursor">subclassing TQSqlCursor</a>. -<p> The <a href="qsqlcursor.html">TQSqlCursor</a> class retquires the <a href="qsqlcursor-h.html">qsqlcursor.h</a> header file. +<p> The <a href="qsqlcursor.html">TQSqlCursor</a> class requires the <a href="qsqlcursor-h.html">qsqlcursor.h</a> header file. <p> <a name="Retrieving_Records"></a> <h3> Retrieving Records </h3> @@ -874,7 +874,7 @@ iteration we call the cursor's primeInsert() method. This method returns a pointer to a <a href="qsqlrecord.html">TQSqlRecord</a> buffer in which all the fields are set to <tt>NULL</tt>. (Note that <a href="qsqlcursor.html#primeInsert">TQSqlCursor::primeInsert</a>() is virtual, and can be customized by derived classes. See <a href="qsqlcursor.html">TQSqlCursor</a>). Next we -call setValue() for each field that retquires a value. Finally we call +call setValue() for each field that requires a value. Finally we call insert() to insert the record. The insert() call returns the number of rows inserted. <p> We obtained a pointer to a <a href="qsqlrecord.html">TQSqlRecord</a> object from the primeInsert() @@ -974,7 +974,7 @@ examples provides additional information. } </pre><blockquote><p align="center"><em> From <a href="sql-overview-table1-main-cpp.html">sql/overview/table1/main.cpp</a> </em></p> -</blockquote><p> Data-Aware tables retquire the <a href="qdatatable-h.html">qdatatable.h</a> and <a href="qsqlcursor-h.html">qsqlcursor.h</a> header +</blockquote><p> Data-Aware tables require the <a href="qdatatable-h.html">qdatatable.h</a> and <a href="qsqlcursor-h.html">qsqlcursor.h</a> header files. We create our application object, call createConnections() and create the cursor. We create the <a href="qdatatable.html">TQDataTable</a> passing it a pointer to the cursor, and set the autoPopulate flag to TRUE. Next we make our <a href="qdatatable.html">TQDataTable</a> the main widget and call refresh() to populate it with data @@ -1370,7 +1370,7 @@ leave the loop. <p> When the user edits the status field in the <a href="qdatatable.html">TQDataTable</a> they will be presented with a combobox of valid status names taken from the status table. However the status displayed is still the raw statusid. To -display the status name when the field isn't being edited retquires us +display the status name when the field isn't being edited requires us to subclass TQDataTable and reimplement the paintField() function. <p> @@ -1487,7 +1487,7 @@ name of the table. We don't have any other characteristics to add at this stage. <p> <pre> InvoiceItemCursor invoiceItemCursor; </pre> -<p> Whenever we retquire a cursor over the invoiceitem table we can create +<p> Whenever we require a cursor over the invoiceitem table we can create an InvoiceItemCursor instead of a generic TQSqlCursor. <p> We still need to show the product name rather than the pricesid. <p> @@ -1541,7 +1541,7 @@ name. which perform real calculations. <p> The header file, <a href="sql-overview-subclass4-main-h.html">sql/overview/subclass4/main.h</a>, remains unchanged from the previous example, but the constructor and calculateField() -function retquire some simple expansion. We'll look at each in turn. +function require some simple expansion. We'll look at each in turn. <p> <pre> InvoiceItemCursor::InvoiceItemCursor() : diff --git a/doc/html/templates.html b/doc/html/templates.html index cd08a160..a7335e53 100644 --- a/doc/html/templates.html +++ b/doc/html/templates.html @@ -69,7 +69,7 @@ C++ source file generated by the <tt>moc</tt> must be compiled and linked with the implementation of the class (or it can be <tt>#included</tt> into the class's source file). Typically <tt>moc</tt> is not called manually, but automatically by the build system, so it -retquires no additional effort by the programmer. +requires no additional effort by the programmer. <p> There are other precompilers, for example, <tt>rpc</tt> and <tt>idl</tt>, that enable programs or objects to communicate over process or machine boundaries. The alternatives to precompilers are @@ -95,7 +95,7 @@ of Objective C when it comes to component-based graphical user interface programming. What's good for a high end database server or an operating system isn't necessarily the right design choice for a GUI frontend. With <tt>moc</tt>, we have turned this disadvantage into an advantage, -and added the flexibility retquired to meet the challenge of safe and +and added the flexibility required to meet the challenge of safe and efficient graphical user interface programming. <p> Our approach goes far beyond anything you can do with templates. For example, we can have object properties. And we can have overloaded @@ -116,7 +116,7 @@ generated and connected from TQt Designer's XML <tt>ui</tt> files. <p> TQt's signals and slots implementation is not as fast as a template-based solution. While emitting a signal is approximately the cost of four ordinary function calls with common template implementations, TQt -retquires effort comparable to about ten function calls. This is not +requires effort comparable to about ten function calls. This is not surprising since the TQt mechanism includes a generic marshaller, introspection and ultimately scriptability. It does not rely on excessive inlining and code expansion and it provides unmatched runtime @@ -132,7 +132,7 @@ cost of the call is only a small proportion of the entire cost of a slot. Benchmarking against TQt's signals and slots system is typically done with empty slots. As soon as you do anything useful in your slots, for example a few simple string operations, the calling overhead becomes -negligible. TQt's system is so optimized that anything that retquires +negligible. TQt's system is so optimized that anything that requires operator new or delete (for example, string operations or inserting/removing something from a template container) is significantly more expensive than emitting a signal. @@ -140,7 +140,7 @@ more expensive than emitting a signal. of a performance critical task and you identify this connection as the bottleneck, think about using the standard listener-interface pattern rather than signals and slots. In cases where this occurs, you probably -only retquire a 1:1 connection anyway. For example, if you have an object +only require a 1:1 connection anyway. For example, if you have an object that downloads data from the network, it's a perfectly sensible design to use a signal to indicate that the requested data arrived. But if you need to send out every single byte one by one to a consumer, use a diff --git a/doc/html/timers.html b/doc/html/timers.html index a8a0d0ff..ccf18b0f 100644 --- a/doc/html/timers.html +++ b/doc/html/timers.html @@ -89,7 +89,7 @@ single-threaded application without blocking the user interface. class Mandelbrot : public <a href="qobject.html">TQObject</a> { - <a href="metaobjects.html#Q_OBJECT">Q_OBJECT</a> // retquired for signals/slots + <a href="metaobjects.html#Q_OBJECT">Q_OBJECT</a> // required for signals/slots public: Mandelbrot( <a href="qobject.html">TQObject</a> *parent=0, const char *name ); ... diff --git a/doc/html/toplevel-example.html b/doc/html/toplevel-example.html index 4d6b998e..85323bbb 100644 --- a/doc/html/toplevel-example.html +++ b/doc/html/toplevel-example.html @@ -219,7 +219,7 @@ build the library. <hr> <ol> <li><a name="footnote1"></a> -Unfortunately some X11 window managers also retquire the <tt>WX11BypassWM</tt> flag to be set in addition; but some other X11 window +Unfortunately some X11 window managers also require the <tt>WX11BypassWM</tt> flag to be set in addition; but some other X11 window managers will have problems if this flag is set. <a href="#footnote-call1">Back...</a> <li><a name="footnote2"></a> The example uses <a href="qguardedptr.html">TQGuardedPtr</a> to make sure that the pointer is reset to zero when the widget object is destroyed diff --git a/doc/html/tutorial1-08.html b/doc/html/tutorial1-08.html index bd65a26d..25d8479a 100644 --- a/doc/html/tutorial1-08.html +++ b/doc/html/tutorial1-08.html @@ -213,7 +213,7 @@ loop upon the first change of one of the values. <p> <pre> <a href="qgridlayout.html">TQGridLayout</a> *grid = new <a href="qgridlayout.html">TQGridLayout</a>( this, 2, 2, 10 ); //2x2, 10 pixel border </pre> -<p> So far we have used the no-assembly-retquired <a href="qvbox.html">TQVBox</a> and <a href="qgrid.html">TQGrid</a> widgets +<p> So far we have used the no-assembly-required <a href="qvbox.html">TQVBox</a> and <a href="qgrid.html">TQGrid</a> widgets for geometry management. Now, however, we want to have a little more control over the layout, and we switch to the more powerful <a href="qgridlayout.html">TQGridLayout</a> class. TQGridLayout isn't a widget; it is a different class that can diff --git a/doc/html/tutorial2-02.html b/doc/html/tutorial2-02.html index 409e7e08..ad105b41 100644 --- a/doc/html/tutorial2-02.html +++ b/doc/html/tutorial2-02.html @@ -48,7 +48,7 @@ are launched from chart form menu options or toolbar buttons. <a href="qcanvas.html">TQCanvas</a> on which we draw the pie chart or bar graph. We subclass TQCanvasView to obtain some specialised behaviour. Similarly we subclass the <a href="qcanvastext.html">TQCanvasText</a> class (used to place text items on a canvas) -since we retquire slightly more than the standard class provides. +since we require slightly more than the standard class provides. <p> The project file, <tt>chart.pro</tt>, is used to create the Makefile that is used to build the application. <p> <p align="right"> diff --git a/doc/html/tutorial2-03.html b/doc/html/tutorial2-03.html index 44b039ab..bbc193b8 100644 --- a/doc/html/tutorial2-03.html +++ b/doc/html/tutorial2-03.html @@ -170,7 +170,7 @@ filter the data using a scripting language. #include <<a href="qstringlist-h.html">qstringlist.h</a>> #include <<a href="qtextstream-h.html">qtextstream.h</a>> </pre> -<p> Our implementation of the operators retquires the inclusion of <a href="qtextstream-h.html">qtextstream.h</a> and <a href="qstringlist-h.html">qstringlist.h</a>. +<p> Our implementation of the operators requires the inclusion of <a href="qtextstream-h.html">qtextstream.h</a> and <a href="qstringlist-h.html">qstringlist.h</a>. <p> <pre> const char FIELD_SEP = ':'; const char PROPOINT_SEP = ';'; const char XY_SEP = ','; diff --git a/doc/html/tutorial2-05.html b/doc/html/tutorial2-05.html index 93195a32..23e6c76d 100644 --- a/doc/html/tutorial2-05.html +++ b/doc/html/tutorial2-05.html @@ -167,7 +167,7 @@ toolbar buttons stay in sync and saves duplicating code. </pre> <p> When we construct an action we give it a name, an optional icon, a menu text, and an accelerator short-cut key (or 0 if no accelerator is -retquired). We also make it a child of the form (by passing <tt>this</tt>). +required). We also make it a child of the form (by passing <tt>this</tt>). When the user clicks a toolbar button or clicks a menu option the <tt>activated()</tt> signal is emitted. We connect() this signal to the action's slot, in the snippet shown above, to fileNew(). <p> The chart types are all mutually exclusive: you can have a pie chart diff --git a/doc/html/tutorial2-06.html b/doc/html/tutorial2-06.html index c126b189..09dab572 100644 --- a/doc/html/tutorial2-06.html +++ b/doc/html/tutorial2-06.html @@ -114,7 +114,7 @@ TQt rather than good (or bad) algorithms for drawing charts. </pre> <p> To draw a horizontal bar chart we need the array of scaled values, the total value (so that we can calculate and draw percentages if -retquired) and a count of the number of values. +required) and a count of the number of values. <p> <pre> double width = m_canvas->width(); double height = m_canvas->height(); int proheight = int(height / count); diff --git a/doc/html/tutorial2-08.html b/doc/html/tutorial2-08.html index b8dbfd86..ebffded5 100644 --- a/doc/html/tutorial2-08.html +++ b/doc/html/tutorial2-08.html @@ -195,7 +195,7 @@ correct number of decimal places. <li> The OK button is connected to the accept() slot; we will update the elements vector in this slot. <li> The Cancel button is connected to the <a href="qdialog.html">TQDialog</a> reject() slot, and -retquires no further code or action on our part. +requires no further code or action on our part. </ul> <p> <pre> TQPixmap patterns[MAX_PATTERNS]; patterns[0] = TQPixmap( pattern01 ); diff --git a/doc/html/winsystem.html b/doc/html/winsystem.html index 7188a2da..eed76b36 100644 --- a/doc/html/winsystem.html +++ b/doc/html/winsystem.html @@ -74,7 +74,7 @@ XRender support only is not enough. <p> <em>Not documented here. Please contact Trolltech Technical Support if you have queries.</em> <p> <h3> Microsoft Visual Studio 2005 Deployment Issues </h3> -<a name="2-1"></a><p> Executables compiled with Microsoft Visual Studio 2005 retquire +<a name="2-1"></a><p> Executables compiled with Microsoft Visual Studio 2005 require a manifest file that points to the C and C++ runtime libraries that TQt and the application itself depend on. The manifest file is automatically generated for you, but it always needs to be located diff --git a/doc/html/wizard-example.html b/doc/html/wizard-example.html index ec553fd4..43f4853d 100644 --- a/doc/html/wizard-example.html +++ b/doc/html/wizard-example.html @@ -161,7 +161,7 @@ void <a name="f184"></a>Wizard::setupPage2() info-><a href="qlabel.html#setText">setText</a>( "\n" "Enter your personal\n" "data here.\n\n" - "The retquired fields are\n" + "The required fields are\n" "First Name, Last Name \n" "and E-Mail.\n" ); info-><a href="qwidget.html#setMaximumWidth">setMaximumWidth</a>( info-><a href="qwidget.html#sizeHint">sizeHint</a>().width() ); diff --git a/doc/html/wizard-wizard-cpp.html b/doc/html/wizard-wizard-cpp.html index 27f649eb..621858f3 100644 --- a/doc/html/wizard-wizard-cpp.html +++ b/doc/html/wizard-wizard-cpp.html @@ -107,7 +107,7 @@ void <a name="f5"></a>Wizard::setupPage2() info-><a href="qlabel.html#setText">setText</a>( "\n" "Enter your personal\n" "data here.\n\n" - "The retquired fields are\n" + "The required fields are\n" "First Name, Last Name \n" "and E-Mail.\n" ); info-><a href="qwidget.html#setMaximumWidth">setMaximumWidth</a>( info-><a href="qwidget.html#sizeHint">sizeHint</a>().width() ); diff --git a/doc/html/xml.html b/doc/html/xml.html index 688f5a0f..c233ff9e 100644 --- a/doc/html/xml.html +++ b/doc/html/xml.html @@ -257,7 +257,7 @@ switched on. (namespace processing, implies <em>http://xml.org/sax/features/namespace-prefixes</em>) and <em>http://xml.org/sax/features/validation</em> (the ability to report validation errors). <p> Whilst SAX2 leaves it to the user to define and implement whatever -features are retquired, support for <em>http://xml.org/sax/features/namespace</em> (and thus <em>http://xml.org/sax/features/namespace-prefixes</em>) is mandantory. +features are required, support for <em>http://xml.org/sax/features/namespace</em> (and thus <em>http://xml.org/sax/features/namespace-prefixes</em>) is mandantory. The <a href="qxmlsimplereader.html">TQXmlSimpleReader</a> implementation of <a href="qxmlreader.html">TQXmlReader</a>, supports them, and can do namespace processing. <p> <a href="qxmlsimplereader.html">TQXmlSimpleReader</a> is not validating, so it @@ -340,7 +340,7 @@ must take care that they pass the right type. Properties are useful if a reader supports special handler classes. <p> The URIs used for features and properties often look like URLs, e.g. <a href="http://xml.org/sax/features/namespace">http://xml.org/sax/features/namespace</a>. This does not mean that the -data retquired is at this address. It is simply a way of defining +data required is at this address. It is simply a way of defining unique names. <p> Anyone can define and use new SAX2 properties for their readers. Property support is not mandatory. @@ -556,7 +556,7 @@ is the part to the left of the ":". (<em>book</em> is the namespace prefix in local part of <em>book:title</em>.) <li> The <em>namespace URI</em> ("Uniform Resource Identifier") is a unique identifier for a namespace. It looks like a URL -(e.g. <em>http://trolltech.com/fnord/</em> ) but does not retquire +(e.g. <em>http://trolltech.com/fnord/</em> ) but does not require data to be accessible by the given protocol at the named address. </ul> <p> Elements without a ":" (like <em>chapter</em> in the example) do not have a diff --git a/doc/html/y2k.html b/doc/html/y2k.html index c2ea7f29..faf6f66d 100644 --- a/doc/html/y2k.html +++ b/doc/html/y2k.html @@ -32,7 +32,7 @@ body { background: #ffffff; color: black; } <td align="right" valign="center"><img src="logo32.png" align="right" width="64" height="32" border="0"></td></tr></table><h1 align=center>Year 2000 Compliance Statement</h1> -<p> Trolltech defines <i>Year 2000 Compliance</i> as a retquirement that a +<p> Trolltech defines <i>Year 2000 Compliance</i> as a requirement that a product or part of product does not contain errors related to transition from December 31, 1999 to January 1, 2000, or to the existence of February 29, 2000. diff --git a/doc/i18n.doc b/doc/i18n.doc index 76646402..02bb1954 100644 --- a/doc/i18n.doc +++ b/doc/i18n.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -49,10 +49,10 @@ the application usable by people in countries other than one's own. \tableofcontents In some cases internationalization is simple, for example, making a US -application accessible to Australian or British users may retquire +application accessible to Australian or British users may require little more than a few spelling corrections. But to make a US application usable by Japanese users, or a Korean application usable -by German users, will retquire that the software operate not only in +by German users, will require that the software operate not only in different languages, but use different input techniques, character encodings and presentation conventions. @@ -72,7 +72,7 @@ Qt supports most languages in use today, in particular: \i Greek \i Hebrew \i Thai and Lao -\i All scripts in Unicode 3.2 that do not retquire special processing +\i All scripts in Unicode 3.2 that do not require special processing \endlist On Windows NT/2000/XP and Unix/X11 with Xft (client side font support) @@ -141,7 +141,7 @@ takes a QRect since this will align in accordance with the language. QFontMetrics::charWidth() to determine the width of a character in a string. In some languages (e.g. Arabic or languages from the Indian subcontinent), the width and shape of a glyph changes depending on the -surrounding characters. Writing input controls usually retquires a +surrounding characters. Writing input controls usually requires a certain knowledge of the scripts it is going to be used in. Usually the easiest way is to subclass QLineEdit or QTextEdit. @@ -425,7 +425,7 @@ application starts, the locale of the machine will determine the 8-bit encoding used when dealing with 8-bit data: such as for font selection, text display, 8-bit text I/O and character input. -The application may occasionally retquire encodings other than the +The application may occasionally require encodings other than the default local 8-bit encoding. For example, an application in a Cyrillic KOI8-R locale (the de-facto standard locale in Russia) might need to output Cyrillic in the ISO 8859-5 encoding. Code for this diff --git a/doc/indices.doc b/doc/indices.doc index 5cf68950..c1444b01 100644 --- a/doc/indices.doc +++ b/doc/indices.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/installation.doc b/doc/installation.doc index 5ee3129f..aa2e4b66 100644 --- a/doc/installation.doc +++ b/doc/installation.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/integration.doc b/doc/integration.doc index 4d9cf989..25b63944 100644 --- a/doc/integration.doc +++ b/doc/integration.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/layout.doc b/doc/layout.doc index bb51aebf..4c5a8461 100644 --- a/doc/layout.doc +++ b/doc/layout.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -123,11 +123,11 @@ only get more space if no other widgets want the space. Of these, space is allocated to widgets with an \c Expanding size policy first. \i Any widgets that are allocated less space than their minimum size (or minimum size hint if no minimum size is specified) are allocated -this minimum size they retquire. (Widgets don't have to have a minimum +this minimum size they require. (Widgets don't have to have a minimum size or minimum size hint in which case the strech factor is their determining factor.) \i Any widgets that are allocated more space than their maximum size -are allocated the maximum size space they retquire. (Widgets don't have +are allocated the maximum size space they require. (Widgets don't have to have a maximum size in which case the strech factor is their determining factor.) \endlist @@ -237,7 +237,7 @@ layout, you should reimplement the following QWidget member functions: \i QWidget::sizeHint() returns the preferred size of the widget. \i QWidget::minimumSizeHint() returns the smallest size the widget can have. \i QWidget::sizePolicy() returns a \l QSizePolicy; a value describing - the space retquirements of the widget. + the space requirements of the widget. \endlist Call QWidget::updateGeometry() whenever the size hint, minimum size @@ -257,13 +257,13 @@ support heightForWidth() (both QGridLayout and QBoxLayout support it). For further guidance when implementing these functions, see their implementations in existing Qt classes that have similar layout -retquirements to your new widget. +requirements to your new widget. \section1 Manual Layout If you are making a one-of-a-kind special layout, you can also make a custom widget as described above. Reimplement QWidget::resizeEvent() -to calculate the retquired distribution of sizes and call \link +to calculate the required distribution of sizes and call \link QWidget::setGeometry() setGeometry\endlink() on each child. The widget will get an event with \link QEvent::type() type \endlink @@ -405,7 +405,7 @@ addItem() implements the default placement strategy for layout items. It must be implemented. It is used by QLayout::add(), by the QLayout constructor that takes a layout as parent, and it is used to implement the \link QLayout::autoAdd() auto-add\endlink feature. If your layout -has advanced placement options that retquire parameters, you must +has advanced placement options that require parameters, you must provide extra access functions such as \l QGridLayout::addMultiCell(). \code diff --git a/doc/mac.doc b/doc/mac.doc index 56bf0b15..2447901b 100644 --- a/doc/mac.doc +++ b/doc/mac.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -100,7 +100,7 @@ libraries inside /usr/lib and similar default locations. We still strongly recommend to build static applications where the library code is incorporated into the Mac OS X binary. However, in case you ship -applications that retquire plugin support,then you need to use dynamic +applications that require plugin support,then you need to use dynamic libraries as part of your application. @@ -187,7 +187,7 @@ Do not forget to enclosure this in an #if defined(Q_OS_MACX) macro statement. \section2 Translating the Application Menu and native dialogs You need to do a little extra to get the Application Menu and native dialogs -localized. This is a retquirement of Mac OS X and not of Qt. +localized. This is a requirement of Mac OS X and not of Qt. First, you must add a localized resource folder inside the Bundle see: diff --git a/doc/makeqpf.doc b/doc/makeqpf.doc index 183990bc..74600ba4 100644 --- a/doc/makeqpf.doc +++ b/doc/makeqpf.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/man/man1/lrelease.1 b/doc/man/man1/lrelease.1 index 2c66f840..4b282723 100644 --- a/doc/man/man1/lrelease.1 +++ b/doc/man/man1/lrelease.1 @@ -11,7 +11,7 @@ .\" and the KDE Free Qt Foundation. .\" .\" Please review the following information to ensure GNU General -.\" Public Licensing retquirements will be met: +.\" Public Licensing requirements will be met: .\" http://trolltech.com/products/qt/licenses/licensing/opensource/. .\" If you are unsure which license is appropriate for your use, please .\" review the following information: diff --git a/doc/man/man1/lupdate.1 b/doc/man/man1/lupdate.1 index c8516992..cb0f652a 100644 --- a/doc/man/man1/lupdate.1 +++ b/doc/man/man1/lupdate.1 @@ -11,7 +11,7 @@ .\" and the KDE Free Qt Foundation. .\" .\" Please review the following information to ensure GNU General -.\" Public Licensing retquirements will be met: +.\" Public Licensing requirements will be met: .\" http://trolltech.com/products/qt/licenses/licensing/opensource/. .\" If you are unsure which license is appropriate for your use, please .\" review the following information: @@ -48,7 +48,7 @@ translation files are given to the translator who uses to read the files and insert the translations. .PP The .ts file format is a simple human-readable XML format that can be -used with version control systems if retquired. +used with version control systems if required. .PP .SH OPTIONS .TP diff --git a/doc/man/man1/moc.1 b/doc/man/man1/moc.1 index 5f806ec9..749b3de5 100644 --- a/doc/man/man1/moc.1 +++ b/doc/man/man1/moc.1 @@ -29,7 +29,7 @@ If you use .B qmake to create your Makefiles, build rules will be included that call the .B moc -when retquired, so you will not need to use the +when required, so you will not need to use the .B moc directly. .PP @@ -226,7 +226,7 @@ signals: Less importantly, the following constructs are illegal. All of them have have alternatives which we think are usually better, so removing these limitations is not a high priority for us. -.SS "Multiple inheritance retquires QObject to be first." +.SS "Multiple inheritance requires QObject to be first." If you are using multiple inheritance, .B moc assumes that the diff --git a/doc/man/man3/qapplication.3qt b/doc/man/man3/qapplication.3qt index 19693773..a62a6d9e 100644 --- a/doc/man/man3/qapplication.3qt +++ b/doc/man/man3/qapplication.3qt @@ -830,7 +830,7 @@ The default implementation requests interaction and sends a close event to all v .PP See also isSessionRestored(), sessionId(), saveState(), and the Session Management overview. .SH "int QApplication::cursorFlashTime ()\fC [static]\fR" -Returns the text cursor's flash (blink) time in milliseconds. The flash time is the time retquired to display, invert and restore the caret display. +Returns the text cursor's flash (blink) time in milliseconds. The flash time is the time required to display, invert and restore the caret display. .PP The default value on X11 is 1000 milliseconds. On Windows, the control panel value is used. .PP @@ -1258,7 +1258,7 @@ QApplication::NormalColor. This is the default color allocation strategy. Use th .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. .TP -QApplication::ManyColor. Use this option if your application is very color hungry (e.g. it retquires thousands of colors). Under X11 the effect is: +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 @@ -1295,7 +1295,7 @@ See also colorSpec(), QColor::numBitPlanes(), and QColor::enterAllocContext(). Examples: .)l helpviewer/main.cpp, opengl/main.cpp, showimg/main.cpp, t9/main.cpp, tetrax/tetrax.cpp, tetrix/tetrix.cpp, and themes/main.cpp. .SH "void QApplication::setCursorFlashTime ( int msecs )\fC [static]\fR" -Sets the text cursor's flash (blink) time to \fImsecs\fR milliseconds. The flash time is the time retquired to display, invert and restore the caret display. Usually the text cursor is displayed for \fImsecs/2\fR milliseconds, then hidden for \fImsecs/2\fR milliseconds, but this may vary. +Sets the text cursor's flash (blink) time to \fImsecs\fR milliseconds. The flash time is the time required to display, invert and restore the caret display. Usually the text cursor is displayed for \fImsecs/2\fR milliseconds, then hidden for \fImsecs/2\fR milliseconds, but this may vary. .PP Note that on Microsoft Windows, calling this function sets the cursor flash time for all windows. .PP @@ -1451,7 +1451,7 @@ See also QWidget::palette, palette(), and QStyle::polish(). Examples: .)l i18n/main.cpp, themes/metal.cpp, themes/themes.cpp, and themes/wood.cpp. .SH "void QApplication::setReverseLayout ( bool b )\fC [static]\fR" -If \fIb\fR is TRUE, all dialogs and widgets will be laid out in a mirrored fashion, as retquired by right to left languages such as Arabic and Hebrew. If \fIb\fR is FALSE, dialogs and widgets are laid out left to right. +If \fIb\fR is TRUE, all dialogs and widgets will be laid out in a mirrored fashion, as required by right to left languages such as Arabic and Hebrew. If \fIb\fR is FALSE, dialogs and widgets are laid out left to right. .PP Changing this flag in runtime does not cause a relayout of already instantiated widgets. .PP diff --git a/doc/man/man3/qassistantclient.3qt b/doc/man/man3/qassistantclient.3qt index a48f2ebd..cc22b529 100644 --- a/doc/man/man3/qassistantclient.3qt +++ b/doc/man/man3/qassistantclient.3qt @@ -63,7 +63,7 @@ The QAssistantClient class provides a means of using Qt Assistant as an applicat .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. .PP -The QAssistantClient instance can open (openAssistant()) or close (closeAssistant()) Qt Assistant whenever retquired. If Qt Assistant is open, isOpen() returns TRUE. +The QAssistantClient instance can open (openAssistant()) or close (closeAssistant()) Qt Assistant whenever required. If Qt 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. .PP diff --git a/doc/man/man3/qaxbase.3qt b/doc/man/man3/qaxbase.3qt index 7c17b261..154031b5 100644 --- a/doc/man/man3/qaxbase.3qt +++ b/doc/man/man3/qaxbase.3qt @@ -263,7 +263,7 @@ If you reimplement this function you must also reimplement the destructor to cal .SH "QString QAxBase::control () const" Returns the name of the COM object wrapped by this QAxBase object. See the "control" property for details. .SH "void QAxBase::disableClassInfo ()" -Disables the class info generation for this ActiveX container. If you don't retquire any class information about the ActiveX control use this function to speed up the meta object generation. +Disables the class info generation for this ActiveX container. If you don't require any class information about the ActiveX control use this function to speed up the meta object generation. .PP Note that this function must be called immediately after construction of the object (without passing an object identifier), and before calling QAxWidget->setControl(). .SH "void QAxBase::disableEventSink ()" diff --git a/doc/man/man3/qaxbindable.3qt b/doc/man/man3/qaxbindable.3qt index 186e7f6c..756b1514 100644 --- a/doc/man/man3/qaxbindable.3qt +++ b/doc/man/man3/qaxbindable.3qt @@ -48,7 +48,7 @@ This class is defined in the \fBQt ActiveQt Extension\fR, which can be found in .PP The QAxBindable class provides an interface between a QWidget and an ActiveX client. .PP -The functions provided by this class allow an ActiveX control to communicate property changes to a client application. Inherit your control class from both QWidget (directly or indirectly) and this class to get access to this class's functions. The meta object compiler retquires you to inherit from QWidget \fIfirst\fR. +The functions provided by this class allow an ActiveX control to communicate property changes to a client application. Inherit your control class from both QWidget (directly or indirectly) and this class to get access to this class's functions. The meta object compiler requires you to inherit from QWidget \fIfirst\fR. .PP .nf .br diff --git a/doc/man/man3/qaxwidget.3qt b/doc/man/man3/qaxwidget.3qt index dda250d9..5aaf3c98 100644 --- a/doc/man/man3/qaxwidget.3qt +++ b/doc/man/man3/qaxwidget.3qt @@ -187,7 +187,7 @@ l - l. WM_SYSKEYDOWN WM_SYSKEYUP WM_KEYDOWN All keycodes VK_MENU .PP This table is the result of experimenting with popular ActiveX controls, ie. Internet Explorer and Microsoft Office applications, but for some -controls it might retquire modification. +controls it might require modification. .SH "SEE ALSO" .BR http://doc.trolltech.com/qaxwidget.html diff --git a/doc/man/man3/qbitarray.3qt b/doc/man/man3/qbitarray.3qt index 3f7777a4..5b155f89 100644 --- a/doc/man/man3/qbitarray.3qt +++ b/doc/man/man3/qbitarray.3qt @@ -106,7 +106,7 @@ Because QBitArray is a QMemArray, it uses explicit sharing with a reference coun .PP A QBitArray is a special byte array that can access individual bits and perform bit-operations (AND, OR, XOR and NOT) on entire arrays or bits. .PP -Bits can be manipulated by the setBit() and clearBit() functions, but it is also possible to use the indexing [] operator to test and set individual bits. The [] operator is a little slower than setBit() and clearBit() because some tricks are retquired to implement single-bit assignments. +Bits can be manipulated by the setBit() and clearBit() functions, but it is also possible to use the indexing [] operator to test and set individual bits. The [] operator is a little slower than setBit() and clearBit() because some tricks are required to implement single-bit assignments. .PP Example: .PP diff --git a/doc/man/man3/qbitval.3qt b/doc/man/man3/qbitval.3qt index d3778e42..6f23a0f6 100644 --- a/doc/man/man3/qbitval.3qt +++ b/doc/man/man3/qbitval.3qt @@ -31,7 +31,7 @@ All the functions in this class are reentrant when Qt is built with thread suppo .SH DESCRIPTION The QBitVal class is an internal class, used with QBitArray. .PP -The QBitVal is retquired by the indexing [] operator on bit arrays. It is not for use in any other context. +The QBitVal is required by the indexing [] operator on bit arrays. It is not for use in any other context. .PP See also Collection Classes. .SH MEMBER FUNCTION DOCUMENTATION diff --git a/doc/man/man3/qcanvas.3qt b/doc/man/man3/qcanvas.3qt index eade4e78..4067e90b 100644 --- a/doc/man/man3/qcanvas.3qt +++ b/doc/man/man3/qcanvas.3qt @@ -240,7 +240,7 @@ Destroys the canvas and all the canvas's canvas items. .SH "void QCanvas::advance ()\fC [virtual slot]\fR" 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 retquired, 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 Qt do anything interesting in phase 0. .PP The canvas can be configured to call this function periodically with setAdvancePeriod(). .PP @@ -331,7 +331,7 @@ This signal is emitted whenever the canvas is resized. Each QCanvasView connects .SH "void QCanvas::retune ( int chunksze, int mxclusters = 100 )\fC [virtual]\fR" Change the efficiency tuning parameters to \fImxclusters\fR clusters, each of size \fIchunksze\fR. This is a slow operation if there are many objects on the canvas. .PP -The canvas is divided into chunks which are rectangular areas \fIchunksze\fR wide by \fIchunksze\fR high. Use a chunk size which is about the average size of the canvas items. If you choose a chunk size which is too small it will increase the amount of calculation retquired when drawing since each change will affect many chunks. If you choose a chunk size which is too large the amount of drawing retquired will increase because for each change, a lot of drawing will be retquired since there will be many (unchanged) canvas items which are in the same chunk as the changed canvas items. +The canvas is divided into chunks which are rectangular areas \fIchunksze\fR wide by \fIchunksze\fR high. Use a chunk size which is about the average size of the canvas items. If you choose a chunk size which is too small it will increase the amount of calculation required when drawing since each change will affect many chunks. If you choose a chunk size which is too large the amount of drawing required will increase because for each change, a lot of drawing will be required since there will be many (unchanged) canvas items which are in the same chunk as the changed canvas items. .PP Internally, a canvas uses a low-resolution "chunk matrix" to keep track of all the items in the canvas. A 64x64 chunk matrix is the default for a 1024x1024 pixel canvas, where each chunk collects canvas items in a 16x16 pixel square. This default is also affected by setTiles(). You can tune this default using this function. For example if you have a very large canvas and want to trade off speed for memory then you might set the chunk size to 32 or 64. .PP diff --git a/doc/man/man3/qcanvaspolygonalitem.3qt b/doc/man/man3/qcanvaspolygonalitem.3qt index f622d513..8d417628 100644 --- a/doc/man/man3/qcanvaspolygonalitem.3qt +++ b/doc/man/man3/qcanvaspolygonalitem.3qt @@ -74,7 +74,7 @@ The QCanvasPolygonalItem class provides a polygonal canvas item on a QCanvas. .PP The mostly rectangular classes, such as QCanvasSprite and QCanvasText, use the object's bounding rectangle for movement, repainting and collision calculations. For most other items, the bounding rectangle can be far too large -- a diagonal line being the worst case, and there are many other cases which are also bad. QCanvasPolygonalItem provides polygon-based bounding rectangle handling, etc., which is much faster for non-rectangular items. .PP -Derived classes should try to define as small an area as possible to maximize efficiency, but the polygon must \fIdefinitely\fR be contained completely within the polygonal area. Calculating the exact retquirements is usually difficult, but if you allow a small overestimate it can be easy and tquick, while still getting almost all of QCanvasPolygonalItem's speed. +Derived classes should try to define as small an area as possible to maximize efficiency, but the polygon must \fIdefinitely\fR be contained completely within the polygonal area. Calculating the exact requirements is usually difficult, but if you allow a small overestimate it can be easy and tquick, while still getting almost all of QCanvasPolygonalItem's speed. .PP Note that all subclasses \fImust\fR call hide() in their destructor since hide() needs to be able to access areaPoints(). .PP diff --git a/doc/man/man3/qcanvasspline.3qt b/doc/man/man3/qcanvasspline.3qt index 349eb042..7f5f296c 100644 --- a/doc/man/man3/qcanvasspline.3qt +++ b/doc/man/man3/qcanvasspline.3qt @@ -70,9 +70,9 @@ Reimplemented from QCanvasPolygon. .SH "void QCanvasSpline::setControlPoints ( QPointArray ctrl, bool close = TRUE )" Set the spline control points to \fIctrl\fR. .PP -If \fIclose\fR is TRUE, then the first point in \fIctrl\fR will be re-used as the last point, and the number of control points must be a multiple of 3. If \fIclose\fR is FALSE, one additional control point is retquired, and the number of control points must be one of (4, 7, 10, 13, ...). +If \fIclose\fR is TRUE, then the first point in \fIctrl\fR will be re-used as the last point, and the number of control points must be a multiple of 3. If \fIclose\fR is FALSE, one additional control point is required, and the number of control points must be one of (4, 7, 10, 13, ...). .PP -If the number of control points doesn't meet the above conditions, the number of points will be truncated to the largest number of points that do meet the retquirement. +If the number of control points doesn't meet the above conditions, the number of points will be truncated to the largest number of points that do meet the requirement. .PP Example: canvas/canvas.cpp. diff --git a/doc/man/man3/qcolor.3qt b/doc/man/man3/qcolor.3qt index d493a402..ff039730 100644 --- a/doc/man/man3/qcolor.3qt +++ b/doc/man/man3/qcolor.3qt @@ -285,7 +285,7 @@ See also enterAllocContext(). .SH "int QColor::blue () const" Returns the B (blue) component of the RGB value. .SH "void QColor::cleanup ()\fC [static]\fR" -Internal clean up retquired for QColor. This function is called from the QApplication destructor. +Internal clean up required for QColor. This function is called from the QApplication destructor. .PP See also initialize(). .SH "QStringList QColor::colorNames ()\fC [static]\fR" @@ -408,7 +408,7 @@ Returns the G (green) component of the RGB value. .PP Example: themes/metal.cpp. .SH "void QColor::initialize ()\fC [static]\fR" -Internal initialization retquired for QColor. This function is called from the QApplication constructor. +Internal initialization required for QColor. This function is called from the QApplication constructor. .PP See also cleanup(). .SH "bool QColor::isValid () const" diff --git a/doc/man/man3/qcopchannel.3qt b/doc/man/man3/qcopchannel.3qt index f621d319..2a3515c5 100644 --- a/doc/man/man3/qcopchannel.3qt +++ b/doc/man/man3/qcopchannel.3qt @@ -109,7 +109,7 @@ Example: .fi This example assumes that the \fImsg\fR is a DCOP-style function signature and the \fIdata\fR contains the function's arguments. (See send().) .PP -Using the DCOP convention is a recommendation, but not a retquirement. Whatever convention you use the sender and receiver \fImust\fR agree on the argument types. +Using the DCOP convention is a recommendation, but not a requirement. Whatever convention you use the sender and receiver \fImust\fR agree on the argument types. .PP See also send(). .SH "void QCopChannel::received ( const QCString & msg, const QByteArray & data )\fC [signal]\fR" @@ -134,7 +134,7 @@ Example: .fi Here the channel is "System/Shell". The \fImsg\fR is an arbitrary string, but in the example we've used the DCOP convention of passing a function signature. Such a signature is formatted as functionname(types) where types is a list of zero or more comma-separated type names, with no whitespace, no consts and no pointer or reference marks, i.e. no "*" or "&". .PP -Using the DCOP convention is a recommendation, but not a retquirement. Whatever convention you use the sender and receiver \fImust\fR agree on the argument types. +Using the DCOP convention is a recommendation, but not a requirement. Whatever convention you use the sender and receiver \fImust\fR agree on the argument types. .PP See also receive(). .SH "bool QCopChannel::send ( const QCString & channel, const QCString & msg )\fC [static]\fR" diff --git a/doc/man/man3/qdatastream.3qt b/doc/man/man3/qdatastream.3qt index 9e895033..8b8b7edd 100644 --- a/doc/man/man3/qdatastream.3qt +++ b/doc/man/man3/qdatastream.3qt @@ -288,7 +288,7 @@ Then read it in with: .br .fi .PP -You can select which byte order to use when serializing data. The default setting is big endian (MSB first). Changing it to little endian breaks the portability (unless the reader also changes to little endian). We recommend keeping this setting unless you have special retquirements. +You can select which byte order to use when serializing data. The default setting is big endian (MSB first). Changing it to little endian breaks the portability (unless the reader also changes to little endian). We recommend keeping this setting unless you have special requirements. .SH "Reading and writing raw binary data" You may wish to read/write your own raw binary data to/from the data stream directly. Data may be read from the stream into a preallocated char* using readRawBytes(). Similarly data can be written to the stream using writeRawBytes(). Notice that any encoding/decoding of the data must be done by you. .PP @@ -488,7 +488,7 @@ Sets the serialization byte order to \fIbo\fR. .PP The \fIbo\fR parameter can be QDataStream::BigEndian or QDataStream::LittleEndian. .PP -The default setting is big endian. We recommend leaving this setting unless you have special retquirements. +The default setting is big endian. We recommend leaving this setting unless you have special requirements. .PP See also byteOrder(). .SH "void QDataStream::setDevice ( QIODevice * d )" diff --git a/doc/man/man3/qdialog.3qt b/doc/man/man3/qdialog.3qt index 7d23207f..adaaa29d 100644 --- a/doc/man/man3/qdialog.3qt +++ b/doc/man/man3/qdialog.3qt @@ -116,7 +116,7 @@ If the user presses the Esc key in a dialog, QDialog::reject() will be called. T .SH "Extensibility" Extensibility is the ability to show the dialog in two ways: a partial dialog that shows the most commonly used options, and a full dialog that shows all the options. Typically an extensible dialog will initially appear as a partial dialog, but with a" More" toggle button. If the user presses the "More" button down, the full dialog will appear. The extension widget will be resized to its sizeHint(). If orientation is Horizontal the extension widget's height() will be expanded to the height() of the dialog. If the orientation is Vertical the extension widget's width() will be expanded to the width() of the dialog. Extensibility is controlled with setExtension(), setOrientation() and showExtension(). .SH "Return value (modal dialogs)" -Modal dialogs are often used in situations where a return value is retquired, e.g. to indicate whether the user pressed "OK" or" Cancel". A dialog can be closed by calling the accept() or the reject() slots, and exec() will return Accepted or Rejected as appropriate. The exec() call returns the result of the dialog. The result is also available from result() if the dialog has not been destroyed. If the WDestructiveClose flag is set, the dialog is deleted after exec() returns. +Modal dialogs are often used in situations where a return value is required, e.g. to indicate whether the user pressed "OK" or" Cancel". A dialog can be closed by calling the accept() or the reject() slots, and exec() will return Accepted or Rejected as appropriate. The exec() call returns the result of the dialog. The result is also available from result() if the dialog has not been destroyed. If the WDestructiveClose flag is set, the dialog is deleted after exec() returns. .SH "Examples" A modal dialog. .PP diff --git a/doc/man/man3/qdockwindow.3qt b/doc/man/man3/qdockwindow.3qt index 8af28b6e..013f260a 100644 --- a/doc/man/man3/qdockwindow.3qt +++ b/doc/man/man3/qdockwindow.3qt @@ -390,7 +390,7 @@ Set this property's value with setMovingEnabled() and get this property's value .SH "bool newLine" This property holds whether the dock window prefers to start a new line in the dock area. .PP -The default is FALSE, i.e. the dock window doesn't retquire a new line in the dock area. +The default is FALSE, i.e. the dock window doesn't require a new line in the dock area. .PP Set this property's value with setNewLine() and get this property's value with newLine(). .SH "int offset" diff --git a/doc/man/man3/qdomdocument.3qt b/doc/man/man3/qdomdocument.3qt index d70f67b4..5651e040 100644 --- a/doc/man/man3/qdomdocument.3qt +++ b/doc/man/man3/qdomdocument.3qt @@ -345,7 +345,7 @@ Assigns \fIx\fR to this DOM document. .PP The data of the copy is shared (shallow copy): modifying one node will also change the other. If you want to make a deep copy, use cloneNode(). .SH "bool QDomDocument::setContent ( const QByteArray & buffer, bool namespaceProcessing, QString * errorMsg = 0, int * errorLine = 0, int * errorColumn = 0 )" -This function parses the XML document from the byte array \fIbuffer\fR and sets it as the content of the document. It tries to detect the encoding of the document as retquired by the XML specification. +This function parses the XML document from the byte array \fIbuffer\fR and sets it as the content of the document. It tries to detect the encoding of the document as required by the XML specification. .PP If \fInamespaceProcessing\fR is TRUE, the parser recognizes namespaces in the XML file and sets the prefix name, local name and namespace URI to appropriate values. If \fInamespaceProcessing\fR is FALSE, the parser does no namespace processing when it reads the XML file. .PP diff --git a/doc/man/man3/qdomnodelist.3qt b/doc/man/man3/qdomnodelist.3qt index e65dabc2..bb787935 100644 --- a/doc/man/man3/qdomnodelist.3qt +++ b/doc/man/man3/qdomnodelist.3qt @@ -46,7 +46,7 @@ All the functions in this class are reentrant when Qt is built with thread suppo .SH DESCRIPTION The QDomNodeList class is a list of QDomNode objects. .PP -Lists can be obtained by QDomDocument::elementsByTagName() and QDomNode::childNodes(). The Document Object Model (DOM) retquires these lists to be "live": whenever you change the underlying document, the contents of the list will get updated. +Lists can be obtained by QDomDocument::elementsByTagName() and QDomNode::childNodes(). The Document Object Model (DOM) requires these lists to be "live": whenever you change the underlying document, the contents of the list will get updated. .PP You can get a particular node from the list with item(). The number of items in the list is returned by count() (and by length()). .PP diff --git a/doc/man/man3/qfiledialog.3qt b/doc/man/man3/qfiledialog.3qt index 34f0b1cb..f4683ed2 100644 --- a/doc/man/man3/qfiledialog.3qt +++ b/doc/man/man3/qfiledialog.3qt @@ -479,7 +479,7 @@ See also addToolButton(), addLeftWidget(), and addRightWidget(). .SH "const QDir * QFileDialog::dir () const" Returns the current directory shown in the file dialog. .PP -The ownership of the QDir pointer is transferred to the caller, so it must be deleted by the caller when no longer retquired. +The ownership of the QDir pointer is transferred to the caller, so it must be deleted by the caller when no longer required. .PP See also setDir(). .SH "void QFileDialog::dirEntered ( const QString & )\fC [signal]\fR" diff --git a/doc/man/man3/qfont.3qt b/doc/man/man3/qfont.3qt index d3c413ff..ce1bfac7 100644 --- a/doc/man/man3/qfont.3qt +++ b/doc/man/man3/qfont.3qt @@ -679,7 +679,7 @@ See also pointSize(), setPointSizeFloat(), pixelSize(), QFontInfo::pointSize(), .SH "void QFont::qwsRenderToDisk ( bool all = TRUE )" Saves the glyphs in the font that have previously been accessed as a QPF file. If \fIall\fR is TRUE (the default), then before saving, all glyphs are marked as used. .PP -If the font is large and you are sure that only a subset of characters will ever be retquired on the target device, passing FALSE for the \fIall\fR parameter can save a significant amount of disk space. +If the font is large and you are sure that only a subset of characters will ever be required on the target device, passing FALSE for the \fIall\fR parameter can save a significant amount of disk space. .PP Note that this function is only applicable on Qt/Embedded. .SH "bool QFont::rawMode () const" diff --git a/doc/man/man3/qglcontext.3qt b/doc/man/man3/qglcontext.3qt index 13ff2fbc..0207b2f1 100644 --- a/doc/man/man3/qglcontext.3qt +++ b/doc/man/man3/qglcontext.3qt @@ -131,7 +131,7 @@ On Windows, it calls the virtual function choosePixelFormat(), which finds a mat .SH "void * QGLContext::chooseMacVisual ( GDHandle device )\fC [virtual protected]\fR" \fBMac only\fR: This virtual function tries to find a visual that matches the format using the given \fIdevice\fR handle, reducing the demands if the original request cannot be met. .PP -The algorithm for reducing the demands of the format is quite simple-minded, so override this method in your subclass if your application has specific retquirements on visual selection. +The algorithm for reducing the demands of the format is quite simple-minded, so override this method in your subclass if your application has specific requirements on visual selection. .PP See also chooseContext(). .SH "int QGLContext::choosePixelFormat ( void * dummyPfd, HDC pdc )\fC [virtual protected]\fR" @@ -143,7 +143,7 @@ See also chooseContext(). .SH "void * QGLContext::chooseVisual ()\fC [virtual protected]\fR" \fBX11 only\fR: This virtual function tries to find a visual that matches the format, reducing the demands if the original request cannot be met. .PP -The algorithm for reducing the demands of the format is quite simple-minded, so override this method in your subclass if your application has spcific retquirements on visual selection. +The algorithm for reducing the demands of the format is quite simple-minded, so override this method in your subclass if your application has spcific requirements on visual selection. .PP See also chooseContext(). .SH "bool QGLContext::create ( const QGLContext * shareContext = 0 )\fC [virtual]\fR" diff --git a/doc/man/man3/qglformat.3qt b/doc/man/man3/qglformat.3qt index dd250082..34d43ebb 100644 --- a/doc/man/man3/qglformat.3qt +++ b/doc/man/man3/qglformat.3qt @@ -184,7 +184,7 @@ After the widget has been created, you can find out which of the requested featu .br if ( !w->format().hasOverlay() ) { .br - qFatal( "Cool hardware retquired" ); + qFatal( "Cool hardware required" ); .br } .br diff --git a/doc/man/man3/qglwidget.3qt b/doc/man/man3/qglwidget.3qt index 177fdc51..c818b08f 100644 --- a/doc/man/man3/qglwidget.3qt +++ b/doc/man/man3/qglwidget.3qt @@ -371,13 +371,13 @@ Depending on your hardware, you can explicitly select which color buffer to grab .SH "void QGLWidget::initializeGL ()\fC [virtual protected]\fR" This virtual function is called once before the first call to paintGL() or resizeGL(), and then once whenever the widget has been assigned a new QGLContext. Reimplement it in a subclass. .PP -This function should set up any retquired OpenGL context rendering flags, defining display lists, etc. +This function should set up any required OpenGL context rendering flags, defining display lists, etc. .PP There is no need to call makeCurrent() because this has already been done when this function is called. .SH "void QGLWidget::initializeOverlayGL ()\fC [virtual protected]\fR" This virtual function is used in the same manner as initializeGL() except that it operates on the widget's overlay context instead of the widget's main context. This means that initializeOverlayGL() is called once before the first call to paintOverlayGL() or resizeOverlayGL(). Reimplement it in a subclass. .PP -This function should set up any retquired OpenGL context rendering flags, defining display lists, etc. for the overlay context. +This function should set up any required OpenGL context rendering flags, defining display lists, etc. for the overlay context. .PP There is no need to call makeOverlayCurrent() because this has already been done when this function is called. .SH "bool QGLWidget::isSharing () const" diff --git a/doc/man/man3/qguardedptr.3qt b/doc/man/man3/qguardedptr.3qt index 6e8d7350..7f13f897 100644 --- a/doc/man/man3/qguardedptr.3qt +++ b/doc/man/man3/qguardedptr.3qt @@ -85,7 +85,7 @@ The functions and operators available with a QGuardedPtr are the same as those a .PP For creating guarded pointers, you can construct or assign to them from an X* or from another guarded pointer of the same type. You can compare them with each other using operator==() and operator!=(), or test for 0 with isNull(). And you can dereference them using either the \fC*x\fR or the \fCx->member\fR notation. .PP -A guarded pointer will automatically cast to an X*, so you can freely mix guarded and unguarded pointers. This means that if you have a QGuardedPtr<QWidget>, you can pass it to a function that retquires a QWidget*. For this reason, it is of little value to declare functions to take a QGuardedPtr as a parameter; just use normal pointers. Use a QGuardedPtr when you are storing a pointer over time. +A guarded pointer will automatically cast to an X*, so you can freely mix guarded and unguarded pointers. This means that if you have a QGuardedPtr<QWidget>, you can pass it to a function that requires a QWidget*. For this reason, it is of little value to declare functions to take a QGuardedPtr as a parameter; just use normal pointers. Use a QGuardedPtr when you are storing a pointer over time. .PP Note again that class \fIX\fR must inherit QObject, or a compilation or link error will result. .PP @@ -104,7 +104,7 @@ Destroys the guarded pointer. Just like a normal pointer, destroying a guarded p .SH "bool QGuardedPtr::isNull () const" Returns \fCTRUE\fR if the referenced object has been destroyed or if there is no referenced object; otherwise returns FALSE. .SH "QGuardedPtr::operator T * () const" -Cast operator; implements pointer semantics. Because of this function you can pass a QGuardedPtr<X> to a function where an X* is retquired. +Cast operator; implements pointer semantics. Because of this function you can pass a QGuardedPtr<X> to a function where an X* is required. .SH "bool QGuardedPtr::operator!= ( const QGuardedPtr<T> & p ) const" Inequality operator; implements pointer semantics, the negation of operator==(). Returns TRUE if \fIp\fR and this guarded pointer are not pointing to the same object; otherwise returns FALSE. .SH "T & QGuardedPtr::operator* () const" diff --git a/doc/man/man3/qhttp.3qt b/doc/man/man3/qhttp.3qt index dee48b68..13482370 100644 --- a/doc/man/man3/qhttp.3qt +++ b/doc/man/man3/qhttp.3qt @@ -342,7 +342,7 @@ See also hasPendingRequests() and abort(). .SH "int QHttp::closeConnection ()" Closes the connection; this is useful if you have a keep-alive connection and want to close it. .PP -For the requests issued with get(), post() and head(), QHttp sets the connection to be keep-alive. You can also do this using the header you pass to the request() function. QHttp only closes the connection to the HTTP server if the response header retquires it to do so. +For the requests issued with get(), post() and head(), QHttp sets the connection to be keep-alive. You can also do this using the header you pass to the request() function. QHttp only closes the connection to the HTTP server if the response header requires it to do so. .PP The function does not block and returns immediately. The request is scheduled, and its execution is performed asynchronously. The function returns a unique identifier which is passed by requestStarted() and requestFinished(). .PP diff --git a/doc/man/man3/qiconset.3qt b/doc/man/man3/qiconset.3qt index cf040303..70f9d92c 100644 --- a/doc/man/man3/qiconset.3qt +++ b/doc/man/man3/qiconset.3qt @@ -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 retquired icon styles and sizes. For example: +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: .PP .nf .br @@ -165,7 +165,7 @@ This enum type describes the size at which a pixmap is intended to be used. The .TP \fCQIconSet::Large\fR - The pixmap is the larger of two. .PP -If a Small pixmap is not set by QIconSet::setPixmap(), the Large pixmap will be automatically scaled down to the size of a small pixmap to generate the Small pixmap when retquired. Similarly, a Small pixmap will be automatically scaled up to generate a Large pixmap. The preferred sizes for large/small generated icons can be set using setIconSize(). +If a Small pixmap is not set by QIconSet::setPixmap(), the Large pixmap will be automatically scaled down to the size of a small pixmap to generate the Small pixmap when required. Similarly, a Small pixmap will be automatically scaled up to generate a Large pixmap. The preferred sizes for large/small generated icons can be set using setIconSize(). .PP See also setIconSize(), iconSize(), setPixmap(), pixmap(), and QMainWindow::usesBigPixmaps. .SH "QIconSet::State" diff --git a/doc/man/man3/qimage.3qt b/doc/man/man3/qimage.3qt index 2b26b1f6..27920b0d 100644 --- a/doc/man/man3/qimage.3qt +++ b/doc/man/man3/qimage.3qt @@ -390,7 +390,7 @@ This enum type is used to describe the endianness of the CPU and graphics hardwa .TP \fCQImage::LittleEndian\fR - PC/Alpha byte order. .SH "QImage::ScaleMode" -The functions scale() and smoothScale() use different modes for scaling the image. The purpose of these modes is to retain the ratio of the image if this is retquired. +The functions scale() and smoothScale() use different modes for scaling the image. The purpose of these modes is to retain the ratio of the image if this is required. .PP <center> .ce 1 diff --git a/doc/man/man3/qimagedecoder.3qt b/doc/man/man3/qimagedecoder.3qt index 3f9c811b..9b2e3282 100644 --- a/doc/man/man3/qimagedecoder.3qt +++ b/doc/man/man3/qimagedecoder.3qt @@ -53,9 +53,9 @@ A QImageDecoder is a machine that decodes images. It takes encoded image data vi .PP QImageFormatType and QImageFormat are the classes that you might need to implement support for additional image formats. .PP -Qt supports GIF reading if it is configured that way during installation (see qgif.h). If it is, we are retquired 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." +Qt supports GIF reading if it is configured that way during installation (see qgif.h). If it is, 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 retquire you to license that technology. Such countries include Canada, Japan, the USA, France, Germany, Italy and the UK. +\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 GIF support may be removed completely in a future version of Qt. We recommend using the MNG or PNG format. .PP diff --git a/doc/man/man3/qimageio.3qt b/doc/man/man3/qimageio.3qt index b448a6b5..746f934e 100644 --- a/doc/man/man3/qimageio.3qt +++ b/doc/man/man3/qimageio.3qt @@ -117,7 +117,7 @@ For image files that contain sequences of images, only the first is read. See QM .PP PBM, PGM, and PPM format \fIoutput\fR is always in the more condensed raw format. PPM and PGM files with more than 256 levels of intensity are scaled down when reading. .PP -\fBWarning:\fR If you are in a country which recognizes software patents and in which Unisys holds a patent on LZW compression and/or decompression and you want to use GIF, Unisys may retquire you to license the technology. Such countries include Canada, Japan, the USA, France, Germany, Italy and the UK. +\fBWarning:\fR If you are in a country which 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 the technology. Such countries include Canada, Japan, the USA, France, Germany, Italy and the UK. .PP GIF support may be removed completely in a future version of Qt. We recommend using the PNG format. .PP @@ -289,7 +289,7 @@ Sets the image to \fIimage\fR. .PP See also image(). .SH "void QImageIO::setParameters ( const char * parameters )" -Sets the image's parameter string to \fIparameters\fR. This is for image handlers that retquire special parameters. +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). .PP diff --git a/doc/man/man3/qlibrary.3qt b/doc/man/man3/qlibrary.3qt index 48431dc6..a93e6e71 100644 --- a/doc/man/man3/qlibrary.3qt +++ b/doc/man/man3/qlibrary.3qt @@ -169,7 +169,7 @@ Returns the address of the exported symbol \fIsymb\fR. The library is loaded if .br .fi .PP -The symbol must be exported as a C-function from the library. This retquires the \fCextern "C"\fR notation if the library is compiled with a C++ compiler. On Windows you also have to explicitly export the function from the DLL using the \fC__declspec(dllexport)\fR compiler directive. +The symbol must be exported as a C-function from the library. This requires the \fCextern "C"\fR notation if the library is compiled with a C++ compiler. On Windows you also have to explicitly export the function from the DLL using the \fC__declspec(dllexport)\fR compiler directive. .PP .nf .br diff --git a/doc/man/man3/qlineedit.3qt b/doc/man/man3/qlineedit.3qt index f3a84b8f..413a5382 100644 --- a/doc/man/man3/qlineedit.3qt +++ b/doc/man/man3/qlineedit.3qt @@ -666,7 +666,7 @@ Unset the mask and return to normal QLineEdit operation by passing an empty stri .PP The mask format understands these mask characters: <center>.nf .TS -l - l. Character Meaning ASCII alphabetic character retquired. A-Z, a-z. ASCII alphabetic character permitted but not retquired. ASCII alphanumeric character retquired. A-Z, a-z, 0-9. ASCII alphanumeric character permitted but not retquired. Any character retquired. x Any character permitted but not retquired. ASCII digit retquired. 0-9. ASCII digit permitted but not retquired. ASCII digit retquired. 1-9. ASCII digit permitted but not retquired (1-9). ASCII digit or plus/minus sign permitted but not retquired. All following alphabetic characters are uppercased. All following alphabetic characters are lowercased. Switch off case conversion. Use +l - l. Character Meaning ASCII alphabetic character required. A-Z, a-z. ASCII alphabetic character permitted but not required. ASCII alphanumeric character required. A-Z, a-z, 0-9. ASCII alphanumeric character permitted but not required. Any character required. x Any character permitted but not required. ASCII digit required. 0-9. ASCII digit permitted but not required. ASCII digit required. 1-9. ASCII digit permitted but not required (1-9). ASCII digit or plus/minus sign permitted but not required. All following alphabetic characters are uppercased. All following alphabetic characters are lowercased. Switch off case conversion. Use .TE .fi </center> diff --git a/doc/man/man3/qlistbox.3qt b/doc/man/man3/qlistbox.3qt index 7608d627..b44858d3 100644 --- a/doc/man/man3/qlistbox.3qt +++ b/doc/man/man3/qlistbox.3qt @@ -423,7 +423,7 @@ There are a variety of selection modes described in the QListBox::SelectionMode .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 -The list box normally arranges its items in a single column and adds a vertical scroll bar if retquired. It is possible to have a different fixed number of columns (setColumnMode()), or as many columns as will fit in the list box's assigned screen space (setColumnMode(FitToWidth)), or to have a fixed number of rows (setRowMode()) or as many rows as will fit in the list box's assigned screen space (setRowMode(FitToHeight)). In all these cases QListBox will add scroll bars, as appropriate, in at least one direction. +The list box normally arranges its items in a single column and adds a vertical scroll bar if required. It is possible to have a different fixed number of columns (setColumnMode()), or as many columns as will fit in the list box's assigned screen space (setColumnMode(FitToWidth)), or to have a fixed number of rows (setRowMode()) or as many rows as will fit in the list box's assigned screen space (setRowMode(FitToHeight)). In all these cases QListBox will add scroll bars, as appropriate, in at least one direction. .PP If multiple rows are used, each row can be as high as necessary (the normal setting), or you can request that all items will have the same height by calling setVariableHeight(FALSE). The same applies to a column's width, see setVariableWidth(). .PP @@ -467,7 +467,7 @@ This enum type is used to specify how QListBox lays out its rows and columns. .TP \fCQListBox::FitToHeight\fR - There are as many rows as will fit on-screen. .TP -\fCQListBox::Variable\fR - There are as many rows as are retquired by the column mode. (Or as many columns as retquired by the row mode.) +\fCQListBox::Variable\fR - There are as many rows as are required by the column mode. (Or as many columns as required by the row mode.) .PP Example: When you call setRowMode( FitToHeight ), columnMode() automatically becomes Variable to accommodate the row mode you've set. .SH "QListBox::SelectionMode" diff --git a/doc/man/man3/qlistview.3qt b/doc/man/man3/qlistview.3qt index 5de30c75..f9975c5b 100644 --- a/doc/man/man3/qlistview.3qt +++ b/doc/man/man3/qlistview.3qt @@ -659,7 +659,7 @@ If the user presses the mouse on an item and starts moving the mouse, and the it .PP By default this function returns 0. You should reimplement it and create a QDragObject depending on the selected items. .SH "void QListView::drawContentsOffset ( QPainter * p, int ox, int oy, int cx, int cy, int cw, int ch )\fC [virtual protected]\fR" -Calls QListViewItem::paintCell() and QListViewItem::paintBranches() as necessary for all list view items that retquire repainting in the \fIcw\fR pixels wide and \fIch\fR pixels high bounding rectangle starting at position \fIcx\fR, \fIcy\fR with offset \fIox\fR, \fIoy\fR. Uses the painter \fIp\fR. +Calls QListViewItem::paintCell() and QListViewItem::paintBranches() as necessary for all list view items that require repainting in the \fIcw\fR pixels wide and \fIch\fR pixels high bounding rectangle starting at position \fIcx\fR, \fIcy\fR with offset \fIox\fR, \fIoy\fR. Uses the painter \fIp\fR. .PP Reimplemented from QScrollView. .SH "void QListView::dropped ( QDropEvent * e )\fC [signal]\fR" @@ -667,7 +667,7 @@ This signal is emitted, when a drop event occurred on the viewport (not onto an .PP \fIe\fR provides all the information about the drop. .SH "void QListView::ensureItemVisible ( const QListViewItem * i )" -Ensures that item \fIi\fR is visible, scrolling the list view vertically if necessary and opening (expanding) any parent items if this is retquired to show the item. +Ensures that item \fIi\fR is visible, scrolling the list view vertically if necessary and opening (expanding) any parent items if this is required to show the item. .PP See also itemRect() and QScrollView::ensureVisible(). .SH "bool QListView::eventFilter ( QObject * o, QEvent * e )\fC [virtual]\fR" diff --git a/doc/man/man3/qlistviewitem.3qt b/doc/man/man3/qlistviewitem.3qt index 56b91109..976b2a7e 100644 --- a/doc/man/man3/qlistviewitem.3qt +++ b/doc/man/man3/qlistviewitem.3qt @@ -688,7 +688,7 @@ Functions which can affect the total height are, setHeight() which is used to se .PP See also height(). .SH "int QListViewItem::width ( const QFontMetrics & fm, const QListView * lv, int c ) const\fC [virtual]\fR" -Returns the number of pixels of width retquired to draw column \fIc\fR of list view \fIlv\fR, using the metrics \fIfm\fR without cropping. The list view containing this item may use this information depending on the QListView::WidthMode settings for the column. +Returns the number of pixels of width required to draw column \fIc\fR of list view \fIlv\fR, using the metrics \fIfm\fR without cropping. The list view containing this item may use this information depending on the QListView::WidthMode settings for the column. .PP The default implementation returns the width of the bounding rectangle of the text of column \fIc\fR. .PP diff --git a/doc/man/man3/qmainwindow.3qt b/doc/man/man3/qmainwindow.3qt index 897f1670..711f04a7 100644 --- a/doc/man/man3/qmainwindow.3qt +++ b/doc/man/man3/qmainwindow.3qt @@ -374,7 +374,7 @@ QMainWindow provides a QToolTipGroup connected to the status bar. The function t .PP New dock windows and toolbars can be added to a QMainWindow using addDockWindow(). Dock windows can be moved using moveDockWindow() and removed with removeDockWindow(). QMainWindow allows default dock window (toolbar) docking in all its dock areas (Top, Left, Right, Bottom). You can use setDockEnabled() to enable and disable docking areas for dock windows. When adding or moving dock windows you can specify their 'edge' (dock area). The currently available edges are: Top, Left, Right, Bottom, Minimized (effectively a 'hidden' dock area) and TornOff (floating). See Qt::Dock for an explanation of these areas. Note that the *ToolBar functions are included for backward compatibility; all new code should use the *DockWindow functions. QToolbar is a subclass of QDockWindow so all functions that work with dock windows work on toolbars in the same way. .PP -If the user clicks the close button, then the dock window is hidden. A dock window can be hidden or unhidden by the user by right clicking a dock area and clicking the name of the relevant dock window on the pop up dock window menu. This menu lists the names of every dock window; visible dock windows have a tick beside their names. The dock window menu is created automatically as retquired by createDockWindowMenu(). Since it may not always be appropriate for a dock window to appear on this menu the setAppropriate() function is used to inform the main window whether or not the dock window menu should include a particular dock window. Double clicking a dock window handle (usually on the left-hand side of the dock window) undocks (floats) the dock window. Double clicking a floating dock window's titlebar will dock the floating dock window. (See also QMainWindow::DockWindows.) +If the user clicks the close button, then the dock window is hidden. A dock window can be hidden or unhidden by the user by right clicking a dock area and clicking the name of the relevant dock window on the pop up dock window menu. This menu lists the names of every dock window; visible dock windows have a tick beside their names. The dock window menu is created automatically as required by createDockWindowMenu(). Since it may not always be appropriate for a dock window to appear on this menu the setAppropriate() function is used to inform the main window whether or not the dock window menu should include a particular dock window. Double clicking a dock window handle (usually on the left-hand side of the dock window) undocks (floats) the dock window. Double clicking a floating dock window's titlebar will dock the floating dock window. (See also QMainWindow::DockWindows.) .PP Some functions change the appearance of a QMainWindow globally: .TP diff --git a/doc/man/man3/qmap.3qt b/doc/man/man3/qmap.3qt index 8498190b..356e78d1 100644 --- a/doc/man/man3/qmap.3qt +++ b/doc/man/man3/qmap.3qt @@ -186,7 +186,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 -The class used for the key retquires that the \fCoperator<\fR is implemented to define ordering of the keys. +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. .PP diff --git a/doc/man/man3/qmemarray.3qt b/doc/man/man3/qmemarray.3qt index 344e0a78..40f2c207 100644 --- a/doc/man/man3/qmemarray.3qt +++ b/doc/man/man3/qmemarray.3qt @@ -161,7 +161,7 @@ The QPtrVector collection class is also a kind of array. Like most collection cl .PP QMemArray uses explicit sharing with a reference count. If more than one array shares common data and one of the arrays is modified, all the arrays are modified. .PP -The benefit of sharing is that a program does not need to duplicate data when it is not retquired, which results in lower memory use and less copying of data. +The benefit of sharing is that a program does not need to duplicate data when it is not required, which results in lower memory use and less copying of data. .PP An alternative to QMemArray is QValueVector. The QValueVector class also provides an array of objects, but can deal with objects that have constructors (specifically a copy constructor and a default constructor). QValueVector provides an STL-compatible syntax and is implicitly shared. .PP @@ -281,7 +281,7 @@ You can make a shallow copy of the array with assign() (or operator=()) and a de .PP Search for values in the array with find() and contains(). For sorted arrays (see sort()) you can search using bsearch(). .PP -You can set the data directly using setRawData() and resetRawData(), although this retquires care. +You can set the data directly using setRawData() and resetRawData(), although this requires care. .PP See also Shared Classes and Non-GUI Classes. .SS "Member Type Documentation" diff --git a/doc/man/man3/qmessagebox.3qt b/doc/man/man3/qmessagebox.3qt index 4785bbc6..9124b7fe 100644 --- a/doc/man/man3/qmessagebox.3qt +++ b/doc/man/man3/qmessagebox.3qt @@ -724,11 +724,11 @@ Sets the message box text to be displayed. See the "text" property for details. .SH "void QMessageBox::setTextFormat ( TextFormat )" Sets the format of the text displayed by the message box. See the "textFormat" property for details. .SH "QPixmap QMessageBox::standardIcon ( Icon icon )\fC [static]\fR" -Returns the pixmap used for a standard icon. This allows the pixmaps to be used in more complex message boxes. \fIicon\fR specifies the retquired icon, e.g. QMessageBox::Question, QMessageBox::Information, QMessageBox::Warning or QMessageBox::Critical. +Returns the pixmap used for a standard icon. This allows the pixmaps to be used in more complex message boxes. \fIicon\fR specifies the required icon, e.g. QMessageBox::Question, QMessageBox::Information, QMessageBox::Warning or QMessageBox::Critical. .SH "QPixmap QMessageBox::standardIcon ( Icon icon, GUIStyle style )\fC [static]\fR" \fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code. .PP -Returns the pixmap used for a standard icon. This allows the pixmaps to be used in more complex message boxes. \fIicon\fR specifies the retquired icon, e.g. QMessageBox::Information, QMessageBox::Warning or QMessageBox::Critical. +Returns the pixmap used for a standard icon. This allows the pixmaps to be used in more complex message boxes. \fIicon\fR specifies the required icon, e.g. QMessageBox::Information, QMessageBox::Warning or QMessageBox::Critical. .PP \fIstyle\fR is unused. .SH "QString QMessageBox::text () const" diff --git a/doc/man/man3/qmetaobject.3qt b/doc/man/man3/qmetaobject.3qt index e7c8844b..e651283a 100644 --- a/doc/man/man3/qmetaobject.3qt +++ b/doc/man/man3/qmetaobject.3qt @@ -64,7 +64,7 @@ The QMetaObject class contains meta information about Qt 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. .PP -This class is not normally retquired for application programming. But if you write meta applications, such as scripting engines or GUI builders, you might find these functions useful: +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 className() to get the name of a class. .TP diff --git a/doc/man/man3/qmotifdialog.3qt b/doc/man/man3/qmotifdialog.3qt index 8f5baa5a..96539cf3 100644 --- a/doc/man/man3/qmotifdialog.3qt +++ b/doc/man/man3/qmotifdialog.3qt @@ -58,7 +58,7 @@ The QMotifDialog class provides the QDialog API for Motif-based dialogs. .PP QMotifDialog provides two separate modes of operation. The application programmer can use QMotifDialog with an existing Motif-based dialog and a QWidget parent, or the application programmer can use QMotifDialog with a custom Qt-based dialog and a Motif-based parent. Modality continues to work as expected. .PP -Motif-based dialogs must have a \fCShell\fR widget parent with a single child, due to retquirements of the Motif toolkit. The \fCShell\fR widget, which is a special subclass of \fCXmDialogShell\fR, is created during construction. It can be accessed using the shell() member function. +Motif-based dialogs must have a \fCShell\fR widget parent with a single child, due to requirements of the Motif toolkit. The \fCShell\fR widget, which is a special subclass of \fCXmDialogShell\fR, is created during construction. It can be accessed using the shell() member function. .PP The single child of the \fCShell\fR can be accessed using the dialog() member function \fIafter\fR it has been created. .PP diff --git a/doc/man/man3/qmovie.3qt b/doc/man/man3/qmovie.3qt index 1d35da9c..2d42419d 100644 --- a/doc/man/man3/qmovie.3qt +++ b/doc/man/man3/qmovie.3qt @@ -134,9 +134,9 @@ The set of data formats supported by QMovie is determined by the decoder factori .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 qgif.h). .PP -If Qt is configured to support GIF reading, we are retquired 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 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. .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 retquire you to license that technology. Such countries include Canada, Japan, the USA, France, Germany, Italy and the UK. +\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 GIF support may be removed completely in a future version of Qt. We recommend using the MNG or PNG format. .PP diff --git a/doc/man/man3/qnpinstance.3qt b/doc/man/man3/qnpinstance.3qt index 6721e938..3b77dfe8 100644 --- a/doc/man/man3/qnpinstance.3qt +++ b/doc/man/man3/qnpinstance.3qt @@ -109,7 +109,7 @@ The QNPInstance class provides a QObject that is a web browser plugin. .PP Deriving from QNPInstance creates an object that represents a single \fC<EMBED>\fR tag in an HTML document. .PP -The QNPInstance is responsible for creating an appropriate QNPWidget window if retquired (not all plugins have windows), and for interacting with the input/output facilities intrinsic to plugins. +The QNPInstance is responsible for creating an appropriate QNPWidget window if required (not all plugins have windows), and for interacting with the input/output facilities intrinsic to plugins. .PP Note that there is \fIabsolutely no guarantee\fR regarding the order in which functions are called. Sometimes the browser will call newWindow() first, at other times, newStreamCreated() will be called first (assuming the \fC<EMBED>\fR tag has a SRC parameter). .PP @@ -180,7 +180,7 @@ Returns the value of the \fIi\fR-th argument. .SH "void * QNPInstance::getJavaPeer () const" Returns the Java object associated with the plugin instance, an object of the plugin's Java class, or 0 if the plug-in does not have a Java class, Java is disabled, or an error occurred. .PP -The return value is actually a \fCjref\fR we use \fCvoid*\fR so as to avoid burdening plugins which do not retquire Java. +The return value is actually a \fCjref\fR we use \fCvoid*\fR so as to avoid burdening plugins which do not require Java. .PP See also QNPlugin::getJavaClass() and QNPlugin::getJavaEnv(). .SH "void QNPInstance::getURL ( const char * url, const char * window = 0 )" @@ -198,13 +198,13 @@ This function is \fInot tested\fR. .PP Requests the creation of a new data stream \fIfrom\fR the plugin. The MIME type and window are passed in \fImimetype\fR and \fIwindow\fR. \fIas_file\fR holds the AsFileOnly flag. It is an interface to the NPN_NewStream function of the Netscape Plugin API. .SH "bool QNPInstance::newStreamCreated ( QNPStream *, StreamMode & smode )\fC [virtual]\fR" -This function is called when a new stream has been created. The instance should return TRUE if it accepts the processing of the stream. If the instance retquires the stream as a file, it should set \fIsmode\fR to AsFileOnly, in which case the data will be delivered some time later to the streamAsFile() function. Otherwise, the data will be delivered in chunks to the write() function, which must consume at least as much data as returned by the most recent call to writeReady(). +This function is called when a new stream has been created. The instance should return TRUE if it accepts the processing of the stream. If the instance requires the stream as a file, it should set \fIsmode\fR to AsFileOnly, in which case the data will be delivered some time later to the streamAsFile() function. Otherwise, the data will be delivered in chunks to the write() function, which must consume at least as much data as returned by the most recent call to writeReady(). .PP Note that the AsFileOnly method is not supported by Netscape 2.0 and MSIE 3.0. .PP The default implementation accepts any stream. .SH "QNPWidget * QNPInstance::newWindow ()\fC [virtual]\fR" -Called at most once, at some time after the QNPInstance is created. If the plugin retquires a window, this function should return a derived class of QNPWidget that provides the retquired interface. +Called at most once, at some time after the QNPInstance is created. If the plugin requires a window, this function should return a derived class of QNPWidget that provides the required interface. .PP Example: grapher/grapher.cpp. .SH "void QNPInstance::notifyURL ( const char * url, Reason r, void * notifyData )\fC [virtual]\fR" diff --git a/doc/man/man3/qnplugin.3qt b/doc/man/man3/qnplugin.3qt index 7d2a7203..33a5feb1 100644 --- a/doc/man/man3/qnplugin.3qt +++ b/doc/man/man3/qnplugin.3qt @@ -80,13 +80,13 @@ Override this function to return a reference to the Java class that represents t .PP If you override this class, you must also override QNPlugin::unuseJavaClass(). .PP -The return value is actually a \fCjref\fR; we use \fCvoid*\fR so as to avoid burdening plugins which do not retquire Java. +The return value is actually a \fCjref\fR; we use \fCvoid*\fR so as to avoid burdening plugins which do not require Java. .PP See also getJavaEnv() and QNPInstance::getJavaPeer(). .SH "void * QNPlugin::getJavaEnv () const" Returns a pointer to the Java execution environment, or 0 if either Java is disabled or an error occurred. .PP -The return value is actually a \fCJRIEnv*\fR; we use \fCvoid*\fR so as to avoid burdening plugins which do not retquire Java. +The return value is actually a \fCJRIEnv*\fR; we use \fCvoid*\fR so as to avoid burdening plugins which do not require Java. .PP See also getJavaClass() and QNPInstance::getJavaPeer(). .SH "const char * QNPlugin::getMIMEDescription () const\fC [pure virtual]\fR" diff --git a/doc/man/man3/qnpwidget.3qt b/doc/man/man3/qnpwidget.3qt index 40ad33ba..ac17887a 100644 --- a/doc/man/man3/qnpwidget.3qt +++ b/doc/man/man3/qnpwidget.3qt @@ -91,7 +91,7 @@ The default implementation is an empty window. .SH "QNPWidget::QNPWidget ()" Creates a QNPWidget. .SH "QNPWidget::~QNPWidget ()" -Destroys the window. This will be called by the plugin binding code when the window is no longer retquired. The web browser will delete windows when they leave the page. The bindings will change the QWidget::winId() of the window when the window is resized, but this should not affect normal widget behavior. +Destroys the window. This will be called by the plugin binding code when the window is no longer required. The web browser will delete windows when they leave the page. The bindings will change the QWidget::winId() of the window when the window is resized, but this should not affect normal widget behavior. .SH "void QNPWidget::enterInstance ()\fC [virtual]\fR" Called when the mouse enters the plugin window. Does nothing by default. .PP diff --git a/doc/man/man3/qobject.3qt b/doc/man/man3/qobject.3qt index e1d36547..fe34d199 100644 --- a/doc/man/man3/qobject.3qt +++ b/doc/man/man3/qobject.3qt @@ -743,7 +743,7 @@ Returns a pointer to the meta object of this object. .PP A meta object contains information about a class that inherits QObject, e.g. class name, superclass name, properties, signals and slots. Every class that contains the Q_OBJECT macro will also have a meta object. .PP -The meta object information is retquired by the signal/slot connection mechanism and the property system. The functions isA() and inherits() also make use of the meta object. +The meta object information is required by the signal/slot connection mechanism and the property system. The functions isA() and inherits() also make use of the meta object. .SH "const char * QObject::name () const" Returns the name of this object. See the "name" property for details. .SH "const char * QObject::name ( const char * defaultName ) const" diff --git a/doc/man/man3/qpaintdevice.3qt b/doc/man/man3/qpaintdevice.3qt index 6001ae75..d8933e2e 100644 --- a/doc/man/man3/qpaintdevice.3qt +++ b/doc/man/man3/qpaintdevice.3qt @@ -189,7 +189,7 @@ Example (scroll widget contents 10 pixels to the right): .br .fi .PP -\fBWarning:\fR Qt retquires 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 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. .PP See also Graphics Classes and Image Processing Classes. .SH MEMBER FUNCTION DOCUMENTATION diff --git a/doc/man/man3/qpainter.3qt b/doc/man/man3/qpainter.3qt index f44f185b..b94def7a 100644 --- a/doc/man/man3/qpainter.3qt +++ b/doc/man/man3/qpainter.3qt @@ -441,7 +441,7 @@ Inherited by QDirectPainter. .SH DESCRIPTION The QPainter class does low-level painting e.g. on widgets. .PP -The painter provides highly optimized functions to do most of the drawing GUI programs retquire. QPainter can draw everything from simple lines to complex shapes like pies and chords. It can also draw aligned text and pixmaps. Normally, it draws in a "natural" coordinate system, but it can also do view and world transformation. +The painter provides highly optimized functions to do most of the drawing GUI programs require. QPainter can draw everything from simple lines to complex shapes like pies and chords. It can also draw aligned text and pixmaps. Normally, it draws in a "natural" coordinate system, but it can also do view and world transformation. .PP The typical use of a painter is: .TP @@ -695,7 +695,7 @@ Example: .PP See also end(). .SH "QRect QPainter::boundingRect ( int x, int y, int w, int h, int flags, const QString &, int len = -1, QTextParag ** intern = 0 )" -Returns the bounding rectangle of the aligned text that would be printed with the corresponding drawText() function using the first \fIlen\fR characters of the string if \fIlen\fR is > -1, or the whole of the string if \fIlen\fR is -1. The drawing, and hence the bounding rectangle, is constrained to the rectangle that begins at point \fI(x, y)\fR with width \fIw\fR and hight \fIh\fR, or to the rectangle retquired to draw the text, whichever is the larger. +Returns the bounding rectangle of the aligned text that would be printed with the corresponding drawText() function using the first \fIlen\fR characters of the string if \fIlen\fR is > -1, or the whole of the string if \fIlen\fR is -1. The drawing, and hence the bounding rectangle, is constrained to the rectangle that begins at point \fI(x, y)\fR with width \fIw\fR and hight \fIh\fR, or to the rectangle required to draw the text, whichever is the larger. .PP The \fIflags\fR argument is the bitwise OR of the following flags: <center>.nf .TS @@ -714,7 +714,7 @@ See also Qt::TextFlags. .SH "QRect QPainter::boundingRect ( const QRect & r, int flags, const QString & str, int len = -1, QTextParag ** internal = 0 )" This is an overloaded member function, provided for convenience. It behaves essentially like the above function. .PP -Returns the bounding rectangle of the aligned text that would be printed with the corresponding drawText() function using the first \fIlen\fR characters from \fIstr\fR if \fIlen\fR is > -1, or the whole of \fIstr\fR if \fIlen\fR is -1. The drawing, and hence the bounding rectangle, is constrained to the rectangle \fIr\fR, or to the rectangle retquired to draw the text, whichever is the larger. +Returns the bounding rectangle of the aligned text that would be printed with the corresponding drawText() function using the first \fIlen\fR characters from \fIstr\fR if \fIlen\fR is > -1, or the whole of \fIstr\fR if \fIlen\fR is -1. The drawing, and hence the bounding rectangle, is constrained to the rectangle \fIr\fR, or to the rectangle required to draw the text, whichever is the larger. .PP The \fIinternal\fR parameter should not be used. .PP diff --git a/doc/man/man3/qpicture.3qt b/doc/man/man3/qpicture.3qt index ca74215f..2ae1a530 100644 --- a/doc/man/man3/qpicture.3qt +++ b/doc/man/man3/qpicture.3qt @@ -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 retquires 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 Qt 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 retquires 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 Qt XML module. The corresponding \fIformat\fR string is "svg". .PP See also load(). .PP diff --git a/doc/man/man3/qpngimagepacker.3qt b/doc/man/man3/qpngimagepacker.3qt index 5744ab69..73aa3624 100644 --- a/doc/man/man3/qpngimagepacker.3qt +++ b/doc/man/man3/qpngimagepacker.3qt @@ -33,7 +33,7 @@ Images are added using packImage(). See also Graphics Classes and Image Processing Classes. .SH MEMBER FUNCTION DOCUMENTATION .SH "QPNGImagePacker::QPNGImagePacker ( QIODevice * iod, int storage_depth, int conversionflags )" -Creates an image packer that writes PNG data to IO device \fIiod\fR using a \fIstorage_depth\fR bit encoding (use 8 or 32, depending on the desired quality and compression retquirements). +Creates an image packer that writes PNG data to IO device \fIiod\fR using a \fIstorage_depth\fR bit encoding (use 8 or 32, depending on the desired quality and compression requirements). .PP If the image needs to be modified to fit in a lower-resolution result (e.g. converting from 32-bit to 8-bit), use the \fIconversionflags\fR to specify how you'd prefer this to happen. .PP diff --git a/doc/man/man3/qprinter.3qt b/doc/man/man3/qprinter.3qt index ead2b387..dfd2599f 100644 --- a/doc/man/man3/qprinter.3qt +++ b/doc/man/man3/qprinter.3qt @@ -486,7 +486,7 @@ Examples: .SH "int QPrinter::numCopies () const" Returns the number of copies to be printed. The default value is 1. .PP -This value will return the number of times the application is retquired to print in order to match the number specified in the printer setup dialog. This has been done since some printer drivers are not capable of buffering up the copies and the application in those cases have to make an explicit call to the print code for each copy. +This value will return the number of times the application is required to print in order to match the number specified in the printer setup dialog. This has been done since some printer drivers are not capable of buffering up the copies and the application in those cases have to make an explicit call to the print code for each copy. .PP See also setNumCopies(). .SH "Orientation QPrinter::orientation () const" diff --git a/doc/man/man3/qprocess.3qt b/doc/man/man3/qprocess.3qt index f9e85193..8624d697 100644 --- a/doc/man/man3/qprocess.3qt +++ b/doc/man/man3/qprocess.3qt @@ -223,7 +223,7 @@ Note that if you are expecting a lot of output from the process, you may hit pla .PP Please note that QProcess does not emulate a shell. This means that QProcess does not do any expansion of arguments: a '*' is passed as a '*' to the program and is \fInot\fR replaced by all the files, a '$HOME' is also passed literally and is \fInot\fR replaced by the environment variable HOME and the special characters for IO redirection ('>', '|', etc.) are also passed literally and do \fInot\fR have the special meaning as they have in a shell. .PP -Also note that QProcess does not emulate a terminal. This means that certain programs which need direct terminal control, do not work as expected with QProcess. Such programs include console email programs (like pine and mutt) but also programs which retquire the user to enter a password (like su and ssh). +Also note that QProcess does not emulate a terminal. This means that certain programs which need direct terminal control, do not work as expected with QProcess. Such programs include console email programs (like pine and mutt) but also programs which require the user to enter a password (like su and ssh). .SH "Notes for Windows users" Some Windows commands, for example, \fCdir\fR, are not provided by separate applications, but by the command interpreter. If you attempt to use QProcess to execute these commands directly it won't work. One possible solution is to execute the command interpreter itself (\fCcmd.exe\fR on some Windows systems), and ask the interpreter to execute the desired command. .PP @@ -240,7 +240,7 @@ This enum type defines the communication channels connected to the process. .TP \fCQProcess::Stderr\fR - Data can be read from the process's standard error. .TP -\fCQProcess::DupStderr\fR - Both the process's standard error output \fIand\fR its standard output are written to its standard output. (Like Unix's dup2().) This means that nothing is sent to the standard error output. This is especially useful if your application retquires that the output on standard output and on standard error must be read in the same order that they are produced. This is a flag, so to activate it you must pass \fCStdout|Stderr|DupStderr\fR, or \fCStdin|Stdout|Stderr|DupStderr\fR if you want to provide input, to the setCommunication() call. +\fCQProcess::DupStderr\fR - Both the process's standard error output \fIand\fR its standard output are written to its standard output. (Like Unix's dup2().) This means that nothing is sent to the standard error output. This is especially useful if your application requires that the output on standard output and on standard error must be read in the same order that they are produced. This is a flag, so to activate it you must pass \fCStdout|Stderr|DupStderr\fR, or \fCStdin|Stdout|Stderr|DupStderr\fR if you want to provide input, to the setCommunication() call. .PP See also setCommunication() and communication(). .SH MEMBER FUNCTION DOCUMENTATION @@ -317,7 +317,7 @@ This function also deletes any pending data that has not been written to standar .PP See also wroteToStdin(). .SH "int QProcess::communication () const" -Returns the communication retquired with the process, i.e. some combination of the Communication flags. +Returns the communication required with the process, i.e. some combination of the Communication flags. .PP See also setCommunication(). .SH "int QProcess::exitStatus () const" @@ -441,7 +441,7 @@ Note for Windows users. The standard Windows shells, e.g. \fCcommand.com\fR and .PP See also arguments() and addArgument(). .SH "void QProcess::setCommunication ( int commFlags )" -Sets \fIcommFlags\fR as the communication retquired with the process. +Sets \fIcommFlags\fR as the communication required with the process. .PP \fIcommFlags\fR is a bitwise OR of the flags defined by the Communication enum. .PP diff --git a/doc/man/man3/qprogressdialog.3qt b/doc/man/man3/qprogressdialog.3qt index e45029a0..d7ad2e62 100644 --- a/doc/man/man3/qprogressdialog.3qt +++ b/doc/man/man3/qprogressdialog.3qt @@ -335,7 +335,7 @@ See also totalSteps. .SH "void QProgressDialog::setTotalSteps ( int totalSteps )\fC [slot]\fR" Sets the total number of steps to \fItotalSteps\fR. See the "totalSteps" property for details. .SH "QSize QProgressDialog::sizeHint () const\fC [virtual]\fR" -Returns a size that fits the contents of the progress dialog. The progress dialog resizes itself as retquired, so you should not need to call this yourself. +Returns a size that fits the contents of the progress dialog. The progress dialog resizes itself as required, so you should not need to call this yourself. .SH "int QProgressDialog::totalSteps () const" Returns the total number of steps. See the "totalSteps" property for details. .SH "bool QProgressDialog::wasCanceled () const" diff --git a/doc/man/man3/qptrcollection.3qt b/doc/man/man3/qptrcollection.3qt index cf2f93e5..4ba1ebaf 100644 --- a/doc/man/man3/qptrcollection.3qt +++ b/doc/man/man3/qptrcollection.3qt @@ -58,7 +58,7 @@ The QPtrCollection class is an abstract base class for the Qt collection classes .PP A QPtrCollection only knows about the number of objects in the collection and the deletion strategy (see setAutoDelete()). .PP -A collection is implemented using the Item (generic collection item) type, which is a \fCvoid*\fR. The template classes that create the real collections cast the Item to the retquired type. +A collection is implemented using the Item (generic collection item) type, which is a \fCvoid*\fR. The template classes that create the real collections cast the Item to the required type. .PP See also Collection Classes and Non-GUI Classes. .SS "Member Type Documentation" diff --git a/doc/man/man3/qptrlist.3qt b/doc/man/man3/qptrlist.3qt index 24974a55..e2d747e0 100644 --- a/doc/man/man3/qptrlist.3qt +++ b/doc/man/man3/qptrlist.3qt @@ -357,7 +357,7 @@ This function returns \fIint\fR rather than \fIbool\fR so that reimplementations .TP < 0 (negative integer) if \fIitem1\fR < \fIitem2\fR .PP -inSort() retquires that compareItems() is implemented as described here. +inSort() requires that compareItems() is implemented as described here. .PP This function should not modify the list because some const functions call compareItems(). .PP diff --git a/doc/man/man3/qptrvector.3qt b/doc/man/man3/qptrvector.3qt index 8d771306..fc4ad3ad 100644 --- a/doc/man/man3/qptrvector.3qt +++ b/doc/man/man3/qptrvector.3qt @@ -184,7 +184,7 @@ This function returns \fIint\fR rather than \fIbool\fR so that reimplementations .TP < 0 (negative integer) if \fId1\fR < \fId2\fR .PP -The sort() and bsearch() functions retquire compareItems() to be implemented as described here. +The sort() and bsearch() functions require compareItems() to be implemented as described here. .PP This function should not modify the vector because some const functions call compareItems(). .SH "uint QPtrVector::contains ( const type * d ) const" diff --git a/doc/man/man3/qregexp.3qt b/doc/man/man3/qregexp.3qt index 73f961bd..54013861 100644 --- a/doc/man/man3/qregexp.3qt +++ b/doc/man/man3/qregexp.3qt @@ -151,7 +151,7 @@ Regexps are built up from expressions, quantifiers, and assertions. The simplest .PP Note that in general regexps cannot be used to check for balanced brackets or tags. For example if you want to match an opening html \fC<b>\fR and its closing \fC</b>\fR you can only use a regexp if you know that these tags are not nested; the html fragment, \fC<b>bold <b>bolder</b></b>\fR will not match as expected. If you know the maximum level of nesting it is possible to create a regexp that will match correctly, but for an unknown level of nesting, regexps will fail. .PP -We'll start by writing a regexp to match integers in the range 0 to 99. We will retquire at least one digit so we will start with \fB[0-9]{1,1}\fR which means match a digit exactly once. This regexp alone will match integers in the range 0 to 9. To match one or two digits we can increase the maximum number of occurrences so the regexp becomes \fB[0-9]{1,2}\fR meaning match a digit at least once and at most twice. However, this regexp as it stands will not match correctly. This regexp will match one or two digits \fIwithin\fR a string. To ensure that we match against the whole string we must use the anchor assertions. We need \fB^\fR (caret) which when it is the first character in the regexp means that the regexp must match from the beginning of the string. And we also need \fB$\fR (dollar) which when it is the last character in the regexp means that the regexp must match until the end of the string. So now our regexp is \fB^[0-9]{1,2}$\fR. Note that assertions, such as \fB^\fR and \fB$\fR, do not match any characters. +We'll start by writing a regexp to match integers in the range 0 to 99. We will require at least one digit so we will start with \fB[0-9]{1,1}\fR which means match a digit exactly once. This regexp alone will match integers in the range 0 to 9. To match one or two digits we can increase the maximum number of occurrences so the regexp becomes \fB[0-9]{1,2}\fR meaning match a digit at least once and at most twice. However, this regexp as it stands will not match correctly. This regexp will match one or two digits \fIwithin\fR a string. To ensure that we match against the whole string we must use the anchor assertions. We need \fB^\fR (caret) which when it is the first character in the regexp means that the regexp must match from the beginning of the string. And we also need \fB$\fR (dollar) which when it is the last character in the regexp means that the regexp must match until the end of the string. So now our regexp is \fB^[0-9]{1,2}$\fR. Note that assertions, such as \fB^\fR and \fB$\fR, do not match any characters. .PP If you've seen regexps elsewhere they may have looked different from the ones above. This is because some sets of characters and some quantifiers are so common that they have special symbols to represent them. \fB[0-9]\fR can be replaced with the symbol \fB\\d\fR. The quantifier to match exactly one occurrence, \fB{1,1}\fR, can be replaced with the expression itself. This means that \fBx{1,1}\fR is exactly the same as \fBx\fR alone. So our 0 to 99 matcher could be written \fB^\\d{1,2}$\fR. Another way of writing it would be \fB^\\d\\d{0,1}$\fR, i.e. from the start of the string match a digit followed by zero or one digits. In practice most people would write it \fB^\\d\\d?$\fR. The \fB?\fR is a shorthand for the quantifier \fB{0,1}\fR, i.e. a minimum of no occurrences a maximum of one occurrence. This is used to make an expression optional. The regexp \fB^\\d\\d?$\fR means "from the beginning of the string match one digit followed by zero or one digits and then the end of the string". .PP @@ -285,7 +285,7 @@ Most of the character class abbreviations supported by Perl are supported by QRe .PP In QRegExp, apart from within character classes, \fC^\fR always signifies the start of the string, so carets must always be escaped unless used for that purpose. In Perl the meaning of caret varies automagically depending on where it occurs so escaping it is rarely necessary. The same applies to \fC$\fR which in QRegExp always signifies the end of the string. .PP -QRegExp's quantifiers are the same as Perl's greedy quantifiers. Non-greedy matching cannot be applied to individual quantifiers, but can be applied to all the quantifiers in the pattern. For example, to match the Perl regexp \fBro+?m\fR retquires: +QRegExp's quantifiers are the same as Perl's greedy quantifiers. Non-greedy matching cannot be applied to individual quantifiers, but can be applied to all the quantifiers in the pattern. For example, to match the Perl regexp \fBro+?m\fR requires: .PP .nf .br diff --git a/doc/man/man3/qsettings.3qt b/doc/man/man3/qsettings.3qt index 571d5c4b..f9509cb2 100644 --- a/doc/man/man3/qsettings.3qt +++ b/doc/man/man3/qsettings.3qt @@ -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 retquired 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 Qt 4. .PP See also readListEntry(), readNumEntry(), readDoubleEntry(), readBoolEntry(), and removeEntry(). .PP diff --git a/doc/man/man3/qsocket.3qt b/doc/man/man3/qsocket.3qt index 65072178..05c70d0a 100644 --- a/doc/man/man3/qsocket.3qt +++ b/doc/man/man3/qsocket.3qt @@ -279,7 +279,7 @@ Attempts to make a connection to \fIhost\fR on the specified \fIport\fR and retu .PP Any connection or pending connection is closed immediately, and QSocket goes into the HostLookup state. When the lookup succeeds, it emits hostFound(), starts a TCP connection and goes into the Connecting state. Finally, when the connection succeeds, it emits connected() and goes into the Connected state. If there is an error at any point, it emits error(). .PP -\fIhost\fR may be an IP address in string form, or it may be a DNS name. QSocket will do a normal DNS lookup if retquired. Note that \fIport\fR is in native byte order, unlike some other libraries. +\fIhost\fR may be an IP address in string form, or it may be a DNS name. QSocket will do a normal DNS lookup if required. Note that \fIport\fR is in native byte order, unlike some other libraries. .PP See also state(). .PP diff --git a/doc/man/man3/qsound.3qt b/doc/man/man3/qsound.3qt index 295b1774..4f19488b 100644 --- a/doc/man/man3/qsound.3qt +++ b/doc/man/man3/qsound.3qt @@ -61,7 +61,7 @@ Inherits QObject. .SH DESCRIPTION The QSound class provides access to the platform audio facilities. .PP -Qt provides the most commonly retquired audio operation in GUI applications: asynchronously playing a sound file. This is most easily accomplished with a single call: +Qt provides the most commonly required audio operation in GUI applications: asynchronously playing a sound file. This is most easily accomplished with a single call: .PP .nf .br diff --git a/doc/man/man3/qsqlcursor.3qt b/doc/man/man3/qsqlcursor.3qt index 8b75415b..166665bc 100644 --- a/doc/man/man3/qsqlcursor.3qt +++ b/doc/man/man3/qsqlcursor.3qt @@ -204,7 +204,7 @@ For example: .PP In the above example, a cursor is created specifying a table or view name in the database. Then, select() is called, which can be optionally parameterised to filter and order the records retrieved. Each record in the cursor is retrieved using next(). When next() returns FALSE, there are no more records to process, and the loop terminates. .PP -For editing records (rows of data), a cursor contains a separate edit buffer which is independent of the fields used when browsing. The functions insert(), update() and del() operate on the edit buffer. This allows the cursor to be repositioned to other records while simultaneously maintaining a separate buffer for edits. You can get a pointer to the edit buffer using editBuffer(). The primeInsert(), primeUpdate() and primeDelete() functions also return a pointer to the edit buffer and prepare it for insert, update and delete respectively. Edit operations only affect a single row at a time. Note that update() and del() retquire that the table or view contain a primaryIndex() to ensure that edit operations affect a unique record within the database. +For editing records (rows of data), a cursor contains a separate edit buffer which is independent of the fields used when browsing. The functions insert(), update() and del() operate on the edit buffer. This allows the cursor to be repositioned to other records while simultaneously maintaining a separate buffer for edits. You can get a pointer to the edit buffer using editBuffer(). The primeInsert(), primeUpdate() and primeDelete() functions also return a pointer to the edit buffer and prepare it for insert, update and delete respectively. Edit operations only affect a single row at a time. Note that update() and del() require that the table or view contain a primaryIndex() to ensure that edit operations affect a unique record within the database. .PP For example: .PP diff --git a/doc/man/man3/qsqldatabase.3qt b/doc/man/man3/qsqldatabase.3qt index 5dd745e4..e5c33941 100644 --- a/doc/man/man3/qsqldatabase.3qt +++ b/doc/man/man3/qsqldatabase.3qt @@ -516,7 +516,7 @@ options .TP tty .TP -retquiressl +requiressl .TP service DB2 OCI TDS .TP @@ -551,7 +551,7 @@ Example of usage: .br // PostgreSQL connection .br - db->setConnectOptions( "retquiressl=1" ); // enable PostgreSQL SSL connections + db->setConnectOptions( "requiressl=1" ); // enable PostgreSQL SSL connections .br if ( !db->open() ) { .br @@ -606,7 +606,7 @@ For the QODBC3 driver it can either be a DSN, a DSN filename (the file must have ... .br .fi -("FIL" is the retquired spelling in Microsoft's API.) +("FIL" is the required spelling in Microsoft's API.) .PP There is no default value. .PP diff --git a/doc/man/man3/qsqldriverplugin.3qt b/doc/man/man3/qsqldriverplugin.3qt index 545acfcd..b8211b17 100644 --- a/doc/man/man3/qsqldriverplugin.3qt +++ b/doc/man/man3/qsqldriverplugin.3qt @@ -42,7 +42,7 @@ Destroys the SQL driver plugin. .PP You never have to call this explicitly. Qt destroys a plugin automatically when it is no longer used. .SH "QSqlDriver * QSqlDriverPlugin::create ( const QString & key )\fC [pure virtual]\fR" -Creates and returns a QSqlDriver object for the driver key \fIkey\fR. The driver key is usually the class name of the retquired driver. +Creates and returns a QSqlDriver object for the driver key \fIkey\fR. The driver key is usually the class name of the required driver. .PP See also keys(). .SH "QStringList QSqlDriverPlugin::keys () const\fC [pure virtual]\fR" diff --git a/doc/man/man3/qsqlfieldinfo.3qt b/doc/man/man3/qsqlfieldinfo.3qt index c7b20c60..36378c86 100644 --- a/doc/man/man3/qsqlfieldinfo.3qt +++ b/doc/man/man3/qsqlfieldinfo.3qt @@ -14,7 +14,7 @@ QSqlFieldInfo \- Stores meta data associated with a SQL field .SS "Public Members" .in +1c .ti -1c -.BI "\fBQSqlFieldInfo\fR ( const QString & name = QString::null, QVariant::Type typ = QVariant::Invalid, int retquired = -1, int len = -1, int prec = -1, const QVariant & defValue = QVariant ( ), int typeID = 0, bool generated = TRUE, bool trim = FALSE, bool calculated = FALSE )" +.BI "\fBQSqlFieldInfo\fR ( const QString & name = QString::null, QVariant::Type typ = QVariant::Invalid, int required = -1, int len = -1, int prec = -1, const QVariant & defValue = QVariant ( ), int typeID = 0, bool generated = TRUE, bool trim = FALSE, bool calculated = FALSE )" .br .ti -1c .BI "\fBQSqlFieldInfo\fR ( const QSqlFieldInfo & other )" @@ -83,10 +83,10 @@ All values must be set in the constructor, and may be retrieved using isRequired .PP See also Database Classes. .SH MEMBER FUNCTION DOCUMENTATION -.SH "QSqlFieldInfo::QSqlFieldInfo ( const QString & name = QString::null, QVariant::Type typ = QVariant::Invalid, int retquired = -1, int len = -1, int prec = -1, const QVariant & defValue = QVariant ( ), int typeID = 0, bool generated = TRUE, bool trim = FALSE, bool calculated = FALSE )" +.SH "QSqlFieldInfo::QSqlFieldInfo ( const QString & name = QString::null, QVariant::Type typ = QVariant::Invalid, int required = -1, int len = -1, int prec = -1, const QVariant & defValue = QVariant ( ), int typeID = 0, bool generated = TRUE, bool trim = FALSE, bool calculated = FALSE )" Constructs a QSqlFieldInfo with the following parameters: <center>.nf .TS -l - l. \fIname\fR the name of the field. \fItyp\fR the field's type in a QVariant. \fIretquired\fR greater than 0 if the field is retquired, 0 if its value can be NULL and less than 0 if it cannot be determined whether the field is retquired or not. \fIlen\fR the length of the field. Note that for non-character types some databases return either the length in bytes or the number of digits. -1 signifies that the length cannot be determined. \fIprec\fR the precision of the field, or -1 if the field has no precision or it cannot be determined. \fIdefValue\fR the default value that is inserted into the table if none is specified by the user. QVariant() if there is no default value or it cannot be determined. \fItypeID\fR the internal typeID of the database system (only useful for low-level programming). 0 if unknown. \fIgenerated\fR TRUE indicates that this field should be included in auto-generated SQL statments, e.g. in QSqlCursor. \fItrim\fR TRUE indicates that widgets should remove trailing whitespace from character fields. This does not affect the field value but only its representation inside widgets. \fIcalculated\fR +l - l. \fIname\fR the name of the field. \fItyp\fR the field's type in a QVariant. \fIrequired\fR greater than 0 if the field is required, 0 if its value can be NULL and less than 0 if it cannot be determined whether the field is required or not. \fIlen\fR the length of the field. Note that for non-character types some databases return either the length in bytes or the number of digits. -1 signifies that the length cannot be determined. \fIprec\fR the precision of the field, or -1 if the field has no precision or it cannot be determined. \fIdefValue\fR the default value that is inserted into the table if none is specified by the user. QVariant() if there is no default value or it cannot be determined. \fItypeID\fR the internal typeID of the database system (only useful for low-level programming). 0 if unknown. \fIgenerated\fR TRUE indicates that this field should be included in auto-generated SQL statments, e.g. in QSqlCursor. \fItrim\fR TRUE indicates that widgets should remove trailing whitespace from character fields. This does not affect the field value but only its representation inside widgets. \fIcalculated\fR .TE .fi </center> @@ -107,7 +107,7 @@ Returns TRUE if the field should be included in auto-generated SQL statments, e. .PP See also setGenerated(). .SH "int QSqlFieldInfo::isRequired () const" -Returns a value greater than 0 if the field is retquired (NULL values are not allowed), 0 if it isn't retquired (NULL values are allowed) or less than 0 if it cannot be determined whether the field is retquired or not. +Returns a value greater than 0 if the field is required (NULL values are not allowed), 0 if it isn't required (NULL values are allowed) or less than 0 if it cannot be determined whether the field is required or not. .SH "bool QSqlFieldInfo::isTrim () const" Returns TRUE if trailing whitespace should be removed from character fields; otherwise returns FALSE. .PP diff --git a/doc/man/man3/qsqlquery.3qt b/doc/man/man3/qsqlquery.3qt index f1a6553a..978e47e9 100644 --- a/doc/man/man3/qsqlquery.3qt +++ b/doc/man/man3/qsqlquery.3qt @@ -178,7 +178,7 @@ For example: .PP 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 retquired 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 retquires 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 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. .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). .PP diff --git a/doc/man/man3/qstring.3qt b/doc/man/man3/qstring.3qt index b5be1e27..1e41f0af 100644 --- a/doc/man/man3/qstring.3qt +++ b/doc/man/man3/qstring.3qt @@ -597,7 +597,7 @@ The QString class provides an abstraction of Unicode text and the classic C '	 .PP QString uses implicit sharing, which makes it very efficient and easy to use. .PP -In all of the QString methods that take \fCconst char *\fR parameters, the \fCconst char *\fR is interpreted as a classic C-style '\0'-terminated ASCII string. It is legal for the \fCconst char *\fR parameter to be 0. If the \fCconst char *\fR is not '\0'-terminated, the results are undefined. Functions that copy classic C strings into a QString will not copy the terminating '\0' character. The QChar array of the QString (as returned by unicode()) is generally not terminated by a '\0'. If you need to pass a QString to a function that retquires a C '\0'-terminated string use latin1(). +In all of the QString methods that take \fCconst char *\fR parameters, the \fCconst char *\fR is interpreted as a classic C-style '\0'-terminated ASCII string. It is legal for the \fCconst char *\fR parameter to be 0. If the \fCconst char *\fR is not '\0'-terminated, the results are undefined. Functions that copy classic C strings into a QString will not copy the terminating '\0' character. The QChar array of the QString (as returned by unicode()) is generally not terminated by a '\0'. If you need to pass a QString to a function that requires a C '\0'-terminated string use latin1(). .PP A QString that has not been assigned to anything is \fInull\fR, i.e. both the length and data pointer is 0. A QString that references the empty string ("", a single '\0' char) is \fIempty\fR. Both null and empty QStrings are legal parameters to the methods. Assigning \fC(const char *) 0\fR to QString gives a null QString. For convenience, QString::null is a null QString. When sorting, empty strings come first, followed by non-empty strings, followed by null strings. We recommend using \fCif ( !str.isNull() )\fR to check for a non-null string rather than \fCif ( !str )\fR; see operator!() for an explanation. .PP @@ -947,7 +947,7 @@ Lexically compares this string with \fIs\fR and returns an integer less than, eq .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. .PP -Applies possible ligatures to a QString. Useful when composition-rich text retquires 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). +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" Returns the QChar at index \fIi\fR by value. .PP diff --git a/doc/man/man3/qstringlist.3qt b/doc/man/man3/qstringlist.3qt index 17d3e251..a27a2d32 100644 --- a/doc/man/man3/qstringlist.3qt +++ b/doc/man/man3/qstringlist.3qt @@ -167,7 +167,7 @@ See also Implicitly and Explicitly Shared Classes, Text Related Classes, and Non .SH "QStringList::QStringList ()" Creates an empty string list. .SH "QStringList::QStringList ( const QStringList & l )" -Creates a copy of the list \fIl\fR. This function is very fast because QStringList is implicitly shared. In most situations this acts like a deep copy, for example, if this list or the original one or some other list referencing the same shared data is modified, the modifying list first makes a copy, i.e. copy-on-write. In a threaded environment you may retquire a real deep copy +Creates a copy of the list \fIl\fR. This function is very fast because QStringList is implicitly shared. In most situations this acts like a deep copy, for example, if this list or the original one or some other list referencing the same shared data is modified, the modifying list first makes a copy, i.e. copy-on-write. In a threaded environment you may require a real deep copy . .SH "QStringList::QStringList ( const QValueList<QString> & l )" Constructs a new string list that is a copy of \fIl\fR. diff --git a/doc/man/man3/qstyle.3qt b/doc/man/man3/qstyle.3qt index 014efc24..d1f7192c 100644 --- a/doc/man/man3/qstyle.3qt +++ b/doc/man/man3/qstyle.3qt @@ -286,7 +286,7 @@ This enum represents a PixelMetric. A PixelMetric is a style dependent size repr .TP \fCQStyle::PM_MDIMinimizedWidth\fR - width of a minimized MSI window. .TP -\fCQStyle::PM_MaximumDragDistance\fR - Some feels retquire the scrollbar or other sliders to jump back to the original position when the mouse pointer is too far away while dragging. A value of -1 disables this behavior. +\fCQStyle::PM_MaximumDragDistance\fR - Some feels require the scrollbar or other sliders to jump back to the original position when the mouse pointer is too far away while dragging. A value of -1 disables this behavior. .TP \fCQStyle::PM_ScrollBarExtent\fR - width of a vertical scrollbar and the height of a horizontal scrollbar. .TP @@ -787,7 +787,7 @@ The rect \fIr\fR should be in logical coordinates. Reimplementations of this fun .PP The \fIhow\fR argument is used to control how the ComplexControl is drawn. Multiple flags can OR'ed together. See the table below for an explanation of which flags are used with the various ComplexControls. .PP -The \fIwidget\fR argument is a pointer to a QWidget or one of its subclasses. The widget can be cast to the appropriate type based on the value of \fIcontrol\fR. The \fIopt\fR argument can be used to pass extra information retquired when drawing the ComplexControl. Note that \fIopt\fR may be the default value even for ComplexControls that can make use of the extra options. See the table below for the appropriate \fIwidget\fR and \fIopt\fR usage: +The \fIwidget\fR argument is a pointer to a QWidget or one of its subclasses. The widget can be cast to the appropriate type based on the value of \fIcontrol\fR. The \fIopt\fR argument can be used to pass extra information required when drawing the ComplexControl. Note that \fIopt\fR may be the default value even for ComplexControls that can make use of the extra options. See the table below for the appropriate \fIwidget\fR and \fIopt\fR usage: .PP <center>.nf .TS @@ -816,7 +816,7 @@ The rect \fIr\fR should be in screen coordinates. .PP The \fIhow\fR argument is used to control how the ControlElement is drawn. Multiple flags can be OR'ed together. See the table below for an explanation of which flags are used with the various ControlElements. .PP -The \fIwidget\fR argument is a pointer to a QWidget or one of its subclasses. The widget can be cast to the appropriate type based on the value of \fIelement\fR. The \fIopt\fR argument can be used to pass extra information retquired when drawing the ControlElement. Note that \fIopt\fR may be the default value even for ControlElements that can make use of the extra options. See the table below for the appropriate \fIwidget\fR and \fIopt\fR usage: +The \fIwidget\fR argument is a pointer to a QWidget or one of its subclasses. The widget can be cast to the appropriate type based on the value of \fIelement\fR. The \fIopt\fR argument can be used to pass extra information required when drawing the ControlElement. Note that \fIopt\fR may be the default value even for ControlElements that can make use of the extra options. See the table below for the appropriate \fIwidget\fR and \fIopt\fR usage: .PP <center>.nf .TS @@ -962,13 +962,13 @@ See also unPolish(). .SH "void QStyle::polish ( QPalette & )\fC [virtual]\fR" This is an overloaded member function, provided for convenience. It behaves essentially like the above function. .PP -The style may have certain retquirements for color palettes. In this function it has the chance to change the palette according to these retquirements. +The style may have certain requirements for color palettes. In this function it has the chance to change the palette according to these requirements. .PP See also QPalette and QApplication::setPalette(). .SH "void QStyle::polishPopupMenu ( QPopupMenu * )\fC [pure virtual]\fR" Polishes the popup menu according to the GUI style. This usually means setting the mouse tracking (QPopupMenu::setMouseTracking()) and whether the menu is checkable by default (QPopupMenu::setCheckable()). .SH "SubControl QStyle::querySubControl ( ComplexControl control, const QWidget * widget, const QPoint & pos, const QStyleOption & opt = QStyleOption::Default ) const\fC [pure virtual]\fR" -Returns the SubControl for \fIwidget\fR at the point \fIpos\fR. The \fIwidget\fR argument is a pointer to a QWidget or one of its subclasses. The widget can be cast to the appropriate type based on the value of \fIcontrol\fR. The \fIopt\fR argument can be used to pass extra information retquired when drawing the ComplexControl. Note that \fIopt\fR may be the default value even for ComplexControls that can make use of the extra options. See drawComplexControl() for an explanation of the \fIwidget\fR and \fIopt\fR arguments. +Returns the SubControl for \fIwidget\fR at the point \fIpos\fR. The \fIwidget\fR argument is a pointer to a QWidget or one of its subclasses. The widget can be cast to the appropriate type based on the value of \fIcontrol\fR. The \fIopt\fR argument can be used to pass extra information required when drawing the ComplexControl. Note that \fIopt\fR may be the default value even for ComplexControls that can make use of the extra options. See drawComplexControl() for an explanation of the \fIwidget\fR and \fIopt\fR arguments. .PP Note that \fIpos\fR is passed in screen coordinates. When using querySubControlMetrics() to check for hits and misses, use visualRect() to change the logical coordinates into screen coordinates. .PP @@ -976,7 +976,7 @@ See also drawComplexControl(), ComplexControl, SubControl, and querySubControlMe .SH "QRect QStyle::querySubControlMetrics ( ComplexControl control, const QWidget * widget, SubControl subcontrol, const QStyleOption & opt = QStyleOption::Default ) const\fC [pure virtual]\fR" Returns the rect for the SubControl \fIsubcontrol\fR for \fIwidget\fR in logical coordinates. .PP -The \fIwidget\fR argument is a pointer to a QWidget or one of its subclasses. The widget can be cast to the appropriate type based on the value of \fIcontrol\fR. The \fIopt\fR argument can be used to pass extra information retquired when drawing the ComplexControl. Note that \fIopt\fR may be the default value even for ComplexControls that can make use of the extra options. See drawComplexControl() for an explanation of the \fIwidget\fR and \fIopt\fR arguments. +The \fIwidget\fR argument is a pointer to a QWidget or one of its subclasses. The widget can be cast to the appropriate type based on the value of \fIcontrol\fR. The \fIopt\fR argument can be used to pass extra information required when drawing the ComplexControl. Note that \fIopt\fR may be the default value even for ComplexControls that can make use of the extra options. See drawComplexControl() for an explanation of the \fIwidget\fR and \fIopt\fR arguments. .PP See also drawComplexControl(), ComplexControl, and SubControl. .SH "QSize QStyle::scrollBarExtent () const" @@ -984,7 +984,7 @@ See also drawComplexControl(), ComplexControl, and SubControl. .SH "QSize QStyle::sizeFromContents ( ContentsType contents, const QWidget * widget, const QSize & contentsSize, const QStyleOption & opt = QStyleOption::Default ) const\fC [pure virtual]\fR" Returns the size of \fIwidget\fR based on the contents size \fIcontentsSize\fR. .PP -The \fIwidget\fR argument is a pointer to a QWidget or one of its subclasses. The widget can be cast to the appropriate type based on the value of \fIcontents\fR. The \fIopt\fR argument can be used to pass extra information retquired when calculating the size. Note that \fIopt\fR may be the default value even for ContentsTypes that can make use of the extra options. See the table below for the appropriate \fIwidget\fR and \fIopt\fR usage: +The \fIwidget\fR argument is a pointer to a QWidget or one of its subclasses. The widget can be cast to the appropriate type based on the value of \fIcontents\fR. The \fIopt\fR argument can be used to pass extra information required when calculating the size. Note that \fIopt\fR may be the default value even for ContentsTypes that can make use of the extra options. See the table below for the appropriate \fIwidget\fR and \fIopt\fR usage: .PP <center>.nf .TS @@ -1001,7 +1001,7 @@ For an explanation of the return value see StyleHint. .SH "QPixmap QStyle::stylePixmap ( StylePixmap stylepixmap, const QWidget * widget = 0, const QStyleOption & opt = QStyleOption::Default ) const\fC [pure virtual]\fR" Returns a pixmap for \fIstylepixmap\fR. .PP -The \fIopt\fR argument can be used to pass extra information retquired when drawing the ControlElement. Note that \fIopt\fR may be the default value even for StylePixmaps that can make use of the extra options. Currently, the \fIopt\fR argument is unused. +The \fIopt\fR argument can be used to pass extra information required when drawing the ControlElement. Note that \fIopt\fR may be the default value even for StylePixmaps that can make use of the extra options. Currently, the \fIopt\fR argument is unused. .PP The \fIwidget\fR argument is a pointer to a QWidget or one of its subclasses. The widget can be cast to the appropriate type based on the value of \fIstylepixmap\fR. See the table below for the appropriate \fIwidget\fR casts: .PP diff --git a/doc/man/man3/qstyleoption.3qt b/doc/man/man3/qstyleoption.3qt index 875d48a3..58c40a8f 100644 --- a/doc/man/man3/qstyleoption.3qt +++ b/doc/man/man3/qstyleoption.3qt @@ -113,7 +113,7 @@ QStyleOption \- Optional parameters for QStyle functions .SH DESCRIPTION The QStyleOption class specifies optional parameters for QStyle functions. .PP -Some QStyle functions take an optional argument specifying extra information that is retquired 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. +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. .PP diff --git a/doc/man/man3/qstyleplugin.3qt b/doc/man/man3/qstyleplugin.3qt index 562e4abd..1c26aa55 100644 --- a/doc/man/man3/qstyleplugin.3qt +++ b/doc/man/man3/qstyleplugin.3qt @@ -42,7 +42,7 @@ Destroys the style plugin. .PP You never have to call this explicitly. Qt destroys a plugin automatically when it is no longer used. .SH "QStyle * QStylePlugin::create ( const QString & key )\fC [pure virtual]\fR" -Creates and returns a QStyle object for the style key \fIkey\fR. The style key is usually the class name of the retquired style. +Creates and returns a QStyle object for the style key \fIkey\fR. The style key is usually the class name of the required style. .PP See also keys(). .SH "QStringList QStylePlugin::keys () const\fC [pure virtual]\fR" diff --git a/doc/man/man3/qsyntaxhighlighter.3qt b/doc/man/man3/qsyntaxhighlighter.3qt index 936b4f44..f004c841 100644 --- a/doc/man/man3/qsyntaxhighlighter.3qt +++ b/doc/man/man3/qsyntaxhighlighter.3qt @@ -67,7 +67,7 @@ Usually this function is called from within highlightParagraph(). .SH "int QSyntaxHighlighter::highlightParagraph ( const QString & text, int endStateOfLastPara )\fC [pure virtual]\fR" This function is called when necessary by the rich text engine, i.e. on paragraphs which have changed. .PP -In your reimplementation you should parse the paragraph's \fItext\fR and call setFormat() as often as necessary to apply any font and color changes that you retquire. Your function must return a value which indicates the paragraph's end state: see below. +In your reimplementation you should parse the paragraph's \fItext\fR and call setFormat() as often as necessary to apply any font and color changes that you require. Your function must return a value which indicates the paragraph's end state: see below. .PP Some syntaxes can have constructs that span paragraphs. For example, a C++ syntax highlighter should be able to cope with \fC/\fR\fC*...*\fR\fC/\fR comments that span paragraphs. To deal with these cases it is necessary to know the end state of the previous paragraph (e.g. "in comment"). .PP diff --git a/doc/man/man3/qtable.3qt b/doc/man/man3/qtable.3qt index 7b9ec476..16ce0f62 100644 --- a/doc/man/man3/qtable.3qt +++ b/doc/man/man3/qtable.3qt @@ -519,11 +519,11 @@ Although many QTable functions operate in terms of rows and columns the indexOf( .SH "Cells" All of a QTable's cells are empty when the table is constructed. .PP -There are two approaches to populating the table's cells. The first and simplest approach is to use QTableItems or QTableItem subclasses. The second approach doesn't use QTableItems at all which is useful for very large sparse tables but retquires you to reimplement a number of functions. We'll look at each approach in turn. +There are two approaches to populating the table's cells. The first and simplest approach is to use QTableItems or QTableItem subclasses. The second approach doesn't use QTableItems at all which is useful for very large sparse tables but requires you to reimplement a number of functions. We'll look at each approach in turn. .PP -To put a string in a cell use setText(). This function will create a new QTableItem for the cell if one doesn't already exist, and displays the text in it. By default the table item's widget will be a QLineEdit. A pixmap may be put in a cell with setPixmap(), which also creates a table item if retquired. A cell may contain \fIboth\fR a pixmap and text; the pixmap is displayed to the left of the text. Another approach is to construct a QTableItem or QTableItem subclass, set its properties, then insert it into a cell with setItem(). +To put a string in a cell use setText(). This function will create a new QTableItem for the cell if one doesn't already exist, and displays the text in it. By default the table item's widget will be a QLineEdit. A pixmap may be put in a cell with setPixmap(), which also creates a table item if required. A cell may contain \fIboth\fR a pixmap and text; the pixmap is displayed to the left of the text. Another approach is to construct a QTableItem or QTableItem subclass, set its properties, then insert it into a cell with setItem(). .PP -If you want cells which contain comboboxes use the QComboTableItem class. Similarly if you retquire cells containing checkboxes use the QCheckTableItem class. These table items look and behave just like the combobox or checkbox widgets but consume far less memory. +If you want cells which contain comboboxes use the QComboTableItem class. Similarly if you require cells containing checkboxes use the QCheckTableItem class. These table items look and behave just like the combobox or checkbox widgets but consume far less memory. .PP .nf .br @@ -546,7 +546,7 @@ It is possible to use your own widget as a cell's widget using setCellWidget(), .PP For large, sparse, tables using QTableItems or other widgets is inefficient. The solution is to \fIdraw\fR the cell as it should appear and to create and destroy cell editors on demand. .PP -This approach retquires that you reimplement various functions. Reimplement paintCell() to display your data, and createEditor() and setCellContentFromEditor() to support in-place editing. It is very important to reimplement resizeData() to have no functionality, to prevent QTable from attempting to create a huge array. You will also need to reimplement item(), setItem(), takeItem(), clearCell(), and insertWidget(), cellWidget() and clearCellWidget(). In almost every circumstance (for sorting, removing and inserting columns and rows, etc.), you also need to reimplement swapRows(), swapCells() and swapColumns(), including header handling. +This approach requires that you reimplement various functions. Reimplement paintCell() to display your data, and createEditor() and setCellContentFromEditor() to support in-place editing. It is very important to reimplement resizeData() to have no functionality, to prevent QTable from attempting to create a huge array. You will also need to reimplement item(), setItem(), takeItem(), clearCell(), and insertWidget(), cellWidget() and clearCellWidget(). In almost every circumstance (for sorting, removing and inserting columns and rows, etc.), you also need to reimplement swapRows(), swapCells() and swapColumns(), including header handling. .PP If you represent active cells with a dictionary of QTableItems and QWidgets, i.e. only store references to cells that are actually used, many of the functions can be implemented with a single line of code. (See the table/bigtable/main.cpp example.) .PP diff --git a/doc/man/man3/qtextcodec.3qt b/doc/man/man3/qtextcodec.3qt index caee026a..f83835cf 100644 --- a/doc/man/man3/qtextcodec.3qt +++ b/doc/man/man3/qtextcodec.3qt @@ -279,7 +279,7 @@ Built-in codecs can be overridden by custom codecs since more recently created Q .PP You may find it more convenient to make your codec class available as a plugin; see the plugin documentation for more details. .PP -The abstract virtual functions describe the encoder to the system and the coder is used as retquired in the different text file formats supported by QTextStream, and under X11, for the locale-specific character input and output. +The abstract virtual functions describe the encoder to the system and the coder is used as required in the different text file formats supported by QTextStream, and under X11, for the locale-specific character input and output. .PP To add support for another 8-bit encoding to Qt, make a subclass of QTextCodec and implement at least the following methods: .PP @@ -304,9 +304,9 @@ If the encoding is multi-byte then it will have "state"; that is, the interpreta QTextDecoder* makeDecoder() const .br .fi -Return a QTextDecoder that remembers incomplete multi-byte sequence prefixes or other retquired state. +Return a QTextDecoder that remembers incomplete multi-byte sequence prefixes or other required state. .PP -If the encoding does \fInot\fR retquire state, you should implement: +If the encoding does \fInot\fR require state, you should implement: .PP .nf .br diff --git a/doc/man/man3/qtextdecoder.3qt b/doc/man/man3/qtextdecoder.3qt index b08f76a0..b72bb031 100644 --- a/doc/man/man3/qtextdecoder.3qt +++ b/doc/man/man3/qtextdecoder.3qt @@ -25,7 +25,7 @@ All the functions in this class are reentrant when Qt is built with thread suppo .SH DESCRIPTION The QTextDecoder class provides a state-based decoder. .PP -The decoder converts a text format into Unicode, remembering any state that is retquired between calls. +The decoder converts a text format into Unicode, remembering any state that is required between calls. .PP See also QTextCodec::makeEncoder() and Internationalization with Qt. .SH MEMBER FUNCTION DOCUMENTATION diff --git a/doc/man/man3/qtextedit.3qt b/doc/man/man3/qtextedit.3qt index ed9a4fba..47b10fc9 100644 --- a/doc/man/man3/qtextedit.3qt +++ b/doc/man/man3/qtextedit.3qt @@ -1077,7 +1077,7 @@ This signal is emitted if the user pressed the Return or the Enter key. .SH "void QTextEdit::scrollToAnchor ( const QString & name )\fC [virtual slot]\fR" Scrolls the text edit to make the text at the anchor called \fIname\fR visible, if it can be found in the document. If the anchor isn't found no scrolling will occur. An anchor is defined using the HTML anchor tag, e.g. \fC<a name="target">\fR. .SH "void QTextEdit::scrollToBottom ()\fC [virtual slot]\fR" -Scrolls to the bottom of the document and does formatting if retquired. +Scrolls to the bottom of the document and does formatting if required. .SH "void QTextEdit::selectAll ( bool select = TRUE )\fC [virtual slot]\fR" If \fIselect\fR is TRUE (the default), all the text is selected as selection 0. If \fIselect\fR is FALSE any selected text is unselected, i.e. the default selection (selection 0) is cleared. .PP diff --git a/doc/man/man3/qtextencoder.3qt b/doc/man/man3/qtextencoder.3qt index 1f869fcd..93c23873 100644 --- a/doc/man/man3/qtextencoder.3qt +++ b/doc/man/man3/qtextencoder.3qt @@ -25,7 +25,7 @@ All the functions in this class are reentrant when Qt is built with thread suppo .SH DESCRIPTION The QTextEncoder class provides a state-based encoder. .PP -The encoder converts Unicode into another format, remembering any state that is retquired between calls. +The encoder converts Unicode into another format, remembering any state that is required between calls. .PP See also QTextCodec::makeEncoder() and Internationalization with Qt. .SH MEMBER FUNCTION DOCUMENTATION diff --git a/doc/man/man3/qtooltip.3qt b/doc/man/man3/qtooltip.3qt index 30be67b7..bdab2c3f 100644 --- a/doc/man/man3/qtooltip.3qt +++ b/doc/man/man3/qtooltip.3qt @@ -153,7 +153,7 @@ You can also display another text (typically in a status bar), courtesy of QTool .PP To add a tip to a fixed rectangle within a widget, call the static function QToolTip::add() with the widget, rectangle and tip as arguments. (See the tooltip/tooltip.cpp example.) Again, you can supply a \fCQToolTipGroup *\fR and another text if you want. .PP -Both of these are one-liners and cover the majority of cases. The third and most general way to use QToolTip retquires you to reimplement a pure virtual function to decide whether to pop up a tool tip. The tooltip/tooltip.cpp example demonstrates this too. This mode can be used to implement tips for text that can move as the user scrolls, for example. +Both of these are one-liners and cover the majority of cases. The third and most general way to use QToolTip requires you to reimplement a pure virtual function to decide whether to pop up a tool tip. The tooltip/tooltip.cpp example demonstrates this too. This mode can be used to implement tips for text that can move as the user scrolls, for example. .PP To use QToolTip like this, you must subclass QToolTip and reimplement maybeTip(). QToolTip calls maybeTip() when a tip should pop up, and maybeTip() decides whether to show a tip. .PP diff --git a/doc/man/man3/qtranslator.3qt b/doc/man/man3/qtranslator.3qt index f9202283..7f3df926 100644 --- a/doc/man/man3/qtranslator.3qt +++ b/doc/man/man3/qtranslator.3qt @@ -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 retquire 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 Qt 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 diff --git a/doc/man/man3/qurl.3qt b/doc/man/man3/qurl.3qt index 579bed77..28a29798 100644 --- a/doc/man/man3/qurl.3qt +++ b/doc/man/man3/qurl.3qt @@ -192,7 +192,7 @@ l - l. Function Returns protocol() "http" host() "doc.trolltech.com" fileName() .fi </center> .PP -The individual parts of a URL can be set with setProtocol(), setHost(), setPort(), setPath(), setFileName(), setRef() and setQuery(). A URL could contain, for example, an ftp address which retquires a user name and password; these can be set with setUser() and setPassword(). +The individual parts of a URL can be set with setProtocol(), setHost(), setPort(), setPath(), setFileName(), setRef() and setQuery(). A URL could contain, for example, an ftp address which requires a user name and password; these can be set with setUser() and setPassword(). .PP Because path is always encoded internally you must not use "%00" in the path, although this is okay (but not recommended) for the query. .PP diff --git a/doc/man/man3/qvalidator.3qt b/doc/man/man3/qvalidator.3qt index a1c9ab46..65e4e5d6 100644 --- a/doc/man/man3/qvalidator.3qt +++ b/doc/man/man3/qvalidator.3qt @@ -42,7 +42,7 @@ If the built-in validators aren't sufficient, you can subclass QValidator. The c .PP validate() must be implemented by every subclass. It returns Invalid, Intermediate or Acceptable depending on whether its argument is valid (for the subclass's definition of valid). .PP -These three states retquire some explanation. An Invalid string is \fIclearly\fR invalid. Intermediate is less obvious: the concept of validity is slippery when the string is incomplete (still being edited). QValidator defines Intermediate as the property of a string that is neither clearly invalid nor acceptable as a final result. Acceptable means that the string is acceptable as a final result. One might say that any string that is a plausible intermediate state during entry of an Acceptable string is Intermediate. +These three states require some explanation. An Invalid string is \fIclearly\fR invalid. Intermediate is less obvious: the concept of validity is slippery when the string is incomplete (still being edited). QValidator defines Intermediate as the property of a string that is neither clearly invalid nor acceptable as a final result. Acceptable means that the string is acceptable as a final result. One might say that any string that is a plausible intermediate state during entry of an Acceptable string is Intermediate. .PP Here are some examples: .IP diff --git a/doc/man/man3/qvaluelist.3qt b/doc/man/man3/qvaluelist.3qt index 04ee4146..5ec60288 100644 --- a/doc/man/man3/qvaluelist.3qt +++ b/doc/man/man3/qvaluelist.3qt @@ -244,7 +244,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 -In addition, some compilers (e.g. Sun CC) might retquire that the class provides an equality operator (operator==()). +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. .PP diff --git a/doc/man/man3/qvaluevector.3qt b/doc/man/man3/qvaluevector.3qt index 9427338b..b2e2584b 100644 --- a/doc/man/man3/qvaluevector.3qt +++ b/doc/man/man3/qvaluevector.3qt @@ -421,7 +421,7 @@ Example: .br .fi .PP -QValueVector stores its elements in contiguous memory. This means that you can use a QValueVector in any situation that retquires an array. +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. .SS "Member Type Documentation" diff --git a/doc/man/man3/qwidget.3qt b/doc/man/man3/qwidget.3qt index 2da51743..4ef1cb3e 100644 --- a/doc/man/man3/qwidget.3qt +++ b/doc/man/man3/qwidget.3qt @@ -2549,7 +2549,7 @@ Note: when you re-implement resizeEvent(), focusInEvent() or focusOutEvent() in .br .fi .PP -at the end of your event handlers. This is true for all member functions that change the appearance of the widget in a way that retquires a recalculation of the mask. +at the end of your event handlers. This is true for all member functions that change the appearance of the widget in a way that requires a recalculation of the mask. .PP While being a technically appealing concept, masks have a big drawback: when using complex masks that cannot be expressed easily with relatively simple regions, they can be very slow on some window systems. The classic example is a transparent label. The complex shape of its contents makes it necessary to represent its mask by a bitmap, which consumes both memory and time. If all you want is to blend the background of several neighboring widgets together seamlessly, you will probably want to use setBackgroundOrigin() rather than a mask. .PP diff --git a/doc/man/man3/qwidgetplugin.3qt b/doc/man/man3/qwidgetplugin.3qt index d5c53c2d..459f0b57 100644 --- a/doc/man/man3/qwidgetplugin.3qt +++ b/doc/man/man3/qwidgetplugin.3qt @@ -64,7 +64,7 @@ Destroys the widget plugin. .PP You never have to call this explicitly. Qt destroys a plugin automatically when it is no longer used. .SH "QWidget * QWidgetPlugin::create ( const QString & key, QWidget * parent = 0, const char * name = 0 )\fC [pure virtual]\fR" -Creates and returns a QWidget object for the widget key \fIkey\fR. The widget key is the class name of the retquired widget. The \fIname\fR and \fIparent\fR arguments are passed to the custom widget's constructor. +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 See also keys(). .SH "QString QWidgetPlugin::group ( const QString & key ) const\fC [virtual]\fR" diff --git a/doc/man/man3/qxmldtdhandler.3qt b/doc/man/man3/qxmldtdhandler.3qt index fc6f071a..4f0a0e28 100644 --- a/doc/man/man3/qxmldtdhandler.3qt +++ b/doc/man/man3/qxmldtdhandler.3qt @@ -32,7 +32,7 @@ The QXmlDTDHandler class provides an interface to report DTD content of XML data .PP If an application needs information about notations and unparsed entities, it can implement this interface and register an instance with QXmlReader::setDTDHandler(). .PP -Note that this interface includes only those DTD events that the XML recommendation retquires processors to report, i.e. notation and unparsed entity declarations using notationDecl() and unparsedEntityDecl() respectively. +Note that this interface includes only those DTD events that the XML recommendation requires processors to report, i.e. notation and unparsed entity declarations using notationDecl() and unparsedEntityDecl() respectively. .PP See also the Introduction to SAX2. .PP diff --git a/doc/metaobjects.doc b/doc/metaobjects.doc index 70592917..e53c95e0 100644 --- a/doc/metaobjects.doc +++ b/doc/metaobjects.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/misc.doc b/doc/misc.doc index cb7c84b3..3071ce77 100644 --- a/doc/misc.doc +++ b/doc/misc.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -93,7 +93,7 @@ tools are usually located in the \c bin subdirectory of Qt distributions. Either run \c "$QTDIR"/bin/moc and \c "$QTDIR"/bin/uic or add \c "$QTDIR"/bin to your \c PATH and run \c moc and \c uic. If you use \c qmake the appropriate lines will be added to your Makefiles so that \e uic and -\e moc will be executed as retquired. +\e moc will be executed as required. <dt>Static or shared libraries - Link time @@ -391,7 +391,7 @@ and development of free software which uses the Software. 6. You may develop application programs, reusable components and other software items that link with the original or modified versions of the Software. These items, when distributed, are subject to the following - retquirements: + requirements: <blockquote> a. You must ensure that all recipients of machine-executable forms of @@ -565,9 +565,9 @@ above, provided that you also meet all of these conditions: these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on - the Program is not retquired to print an announcement.) + the Program is not required to print an announcement.) -These retquirements apply to the modified work as a whole. If +These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those @@ -633,7 +633,7 @@ However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. - 5. You are not retquired to accept this License, since you have not + 5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by diff --git a/doc/moc.doc b/doc/moc.doc index daf8b004..f017a66e 100644 --- a/doc/moc.doc +++ b/doc/moc.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -53,7 +53,7 @@ The moc reads a C++ source file. If it finds one or more class declarations that contain the Q_OBJECT macro, it produces another C++ source file which contains the meta object code for the classes that use the Q_OBJECT macro. Among other things, meta object code is -retquired for the signal/slot mechanism, runtime type information and +required for the signal/slot mechanism, runtime type information and the dynamic property system. The C++ source file generated by the moc must be compiled and linked @@ -62,7 +62,7 @@ class's source file). If you use \link qmake-manual.book qmake\endlink to create your Makefiles, build rules will be included that call the moc when -retquired, so you will not need to use the moc directly. For more +required, so you will not need to use the moc directly. For more background information on moc, see \link templates.html Why doesn't Qt use templates for signals and slots?\endlink. @@ -317,7 +317,7 @@ Less importantly, the following constructs are illegal. All of them have alternatives which we think are usually better, so removing these limitations is not a high priority for us. -\section2 Multiple inheritance retquires QObject to be first +\section2 Multiple inheritance requires QObject to be first If you are using multiple inheritance, moc assumes that the \e first inherited class is a subclass of QObject. Also, be sure that \e only diff --git a/doc/modules.doc b/doc/modules.doc index 3dbc9163..ce0e6783 100644 --- a/doc/modules.doc +++ b/doc/modules.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/network.doc b/doc/network.doc index 5b2eaec5..f6b986d8 100644 --- a/doc/network.doc +++ b/doc/network.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -355,7 +355,7 @@ change the state of the \c QNetworkOperation during processing. You can also get and set \c QNetworkOperation arguments as the operation progresses. -It may occur that the network protocol you implement only retquires a +It may occur that the network protocol you implement only requires a subset of these operations. In such cases, simply reimplement the operations which are supported by the protocol. Additionally you must specify which operations you support. This is achieved by diff --git a/doc/networking.doc b/doc/networking.doc index 6d88a197..99d3ceb2 100644 --- a/doc/networking.doc +++ b/doc/networking.doc @@ -40,7 +40,7 @@ refer to them her. The QSocket and QServerSocket classes provide an easy-to-use API for client and server socket programming. -These classes retquire an event loop and must be used within an +These classes require an event loop and must be used within an application's GUI thread. They are ideal for end-user applications that need network access, but they are not suitable for console applications or for high performance daemons (services). @@ -253,7 +253,7 @@ This function sends a command to the server. Notice that is uses QTextStream to \printline } \printline } -Here we parse responses from the server. It's worth noting again that the communication is asynchronous and it must not be assumed when and how the data will come. The fact that server socket sends all data lines at once (in one loop) does not mean that client socket will receive them as one package and emit one readyRead() signal. That is why we designed our protocol to have termination line , with M = ' ' (e.g. "213 "). In this example the line code will determine its destination (infoList or infoText), but in more advanced usage client would probably retquire some sort of the finite state machine, as we'll se in the next example. +Here we parse responses from the server. It's worth noting again that the communication is asynchronous and it must not be assumed when and how the data will come. The fact that server socket sends all data lines at once (in one loop) does not mean that client socket will receive them as one package and emit one readyRead() signal. That is why we designed our protocol to have termination line , with M = ' ' (e.g. "213 "). In this example the line code will determine its destination (infoList or infoText), but in more advanced usage client would probably require some sort of the finite state machine, as we'll se in the next example. \skipto ::socketConnectionClosed() @@ -275,7 +275,7 @@ Protocol) is declared (\c network/infoprotocol/infourlclient/qip.h): \skipto Qip \printuntil }; -QNetworkProtocol is the base class for every Network Protocol class. Because this protocol uses network, we embedded one QSocket* member variable to which we'll delegate network communication. Protocols that doesn't retquire to use network will do it on their own way - e.g. QLocalFs uses QDir, some data actquisition protocol may use serial or USB connection, only retquirement is that protocol uses hierarchical structure and can be accessed using URLs (to have addressable nodes). +QNetworkProtocol is the base class for every Network Protocol class. Because this protocol uses network, we embedded one QSocket* member variable to which we'll delegate network communication. Protocols that doesn't require to use network will do it on their own way - e.g. QLocalFs uses QDir, some data actquisition protocol may use serial or USB connection, only requirement is that protocol uses hierarchical structure and can be accessed using URLs (to have addressable nodes). Let us go to the Qip implementation (\c network/infoprotocol/infourlclient/qip.cpp): @@ -310,7 +310,7 @@ Here we implement two supported operations. QUrlOperator is class that initiated \printuntil } \printuntil } -Implementation is very similar to previous example in addition that there are now some signal emitting retquirements, so we had to use simple state machine here. In list operation we have to emit start(QNetworkOperation*) before first child, and then to emit QNetworkProtocol::newChild (const QUrlInfo&, QNetworkOperation*) for each child listed from the server. For get operation, we should emit QNetworkProtocol::data (const QByteArray&, QNetworkOperation*) for each data chunk received (in this case, one text line). It is very important that \e every operation finishes with QNetworkProtocol::finished(QNetworkOperation*) signal! +Implementation is very similar to previous example in addition that there are now some signal emitting requirements, so we had to use simple state machine here. In list operation we have to emit start(QNetworkOperation*) before first child, and then to emit QNetworkProtocol::newChild (const QUrlInfo&, QNetworkOperation*) for each child listed from the server. For get operation, we should emit QNetworkProtocol::data (const QByteArray&, QNetworkOperation*) for each data chunk received (in this case, one text line). It is very important that \e every operation finishes with QNetworkProtocol::finished(QNetworkOperation*) signal! \skipto error \printuntil state diff --git a/doc/object.doc b/doc/object.doc index 9f03cdfa..4ff1e98a 100644 --- a/doc/object.doc +++ b/doc/object.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -44,7 +44,7 @@ The standard C++ Object Model provides very efficient runtime support for the object paradigm. But the C++ Object Model's static nature is inflexibile in certain problem domains. Graphical User Interface -programming is a domain that retquires both runtime efficiency and a +programming is a domain that requires both runtime efficiency and a high level of flexibility. Qt provides this, by combining the speed of C++ with the flexibility of the Qt Object Model. @@ -71,7 +71,7 @@ Qt adds these features to C++: Many of these Qt features are implemented with standard C++ techniques, based on inheritance from \l QObject. Others, like the object communication mechanism and the dynamic property system, -retquire the \link metaobjects.html Meta Object System \endlink provided +require the \link metaobjects.html Meta Object System \endlink provided by Qt's own \link moc.html Meta Object Compiler (moc) \endlink. The Meta Object System is a C++ extension that makes the language @@ -154,7 +154,7 @@ single-threaded application without blocking the user interface. class Mandelbrot : public QObject { - Q_OBJECT // retquired for signals/slots + Q_OBJECT // required for signals/slots public: Mandelbrot( QObject *parent=0, const char *name ); ... @@ -656,7 +656,7 @@ C++ source file generated by the <tt>moc</tt> must be compiled and linked with the implementation of the class (or it can be <tt>#included</tt> into the class's source file). Typically <tt>moc</tt> is not called manually, but automatically by the build system, so it -retquires no additional effort by the programmer. +requires no additional effort by the programmer. There are other precompilers, for example, <tt>rpc</tt> and <tt>idl</tt>, that enable programs or objects to communicate over @@ -687,7 +687,7 @@ of Objective C when it comes to component-based graphical user interface programming. What's good for a high end database server or an operating system isn't necessarily the right design choice for a GUI frontend. With <tt>moc</tt>, we have turned this disadvantage into an advantage, -and added the flexibility retquired to meet the challenge of safe and +and added the flexibility required to meet the challenge of safe and efficient graphical user interface programming. Our approach goes far beyond anything you can do with templates. For @@ -712,7 +712,7 @@ generated and connected from Qt Designer's XML <tt>ui</tt> files. Qt's signals and slots implementation is not as fast as a template-based solution. While emitting a signal is approximately the cost of four ordinary function calls with common template implementations, Qt -retquires effort comparable to about ten function calls. This is not +requires effort comparable to about ten function calls. This is not surprising since the Qt mechanism includes a generic marshaller, introspection and ultimately scriptability. It does not rely on excessive inlining and code expansion and it provides unmatched runtime @@ -729,7 +729,7 @@ cost of the call is only a small proportion of the entire cost of a slot. Benchmarking against Qt's signals and slots system is typically done with empty slots. As soon as you do anything useful in your slots, for example a few simple string operations, the calling overhead becomes -negligible. Qt's system is so optimized that anything that retquires +negligible. Qt's system is so optimized that anything that requires operator new or delete (for example, string operations or inserting/removing something from a template container) is significantly more expensive than emitting a signal. @@ -738,7 +738,7 @@ Aside: If you have a signals and slots connection in a tight inner loop of a performance critical task and you identify this connection as the bottleneck, think about using the standard listener-interface pattern rather than signals and slots. In cases where this occurs, you probably -only retquire a 1:1 connection anyway. For example, if you have an object +only require a 1:1 connection anyway. For example, if you have an object that downloads data from the network, it's a perfectly sensible design to use a signal to indicate that the requested data arrived. But if you need to send out every single byte one by one to a consumer, use a diff --git a/doc/opengl-x11-overlays.doc b/doc/opengl-x11-overlays.doc index bc3ac97c..9c310020 100644 --- a/doc/opengl-x11-overlays.doc +++ b/doc/opengl-x11-overlays.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -56,7 +56,7 @@ planes. In the typical case, X11 overlays can easily be used together with the current version of Qt and the Qt OpenGL Extension. The following -retquirements apply: +requirements apply: \list 1 \i Your X server and graphics card/hardware must support overlays. diff --git a/doc/overviews-list.doc b/doc/overviews-list.doc index 6e509836..9cfe3cd3 100644 --- a/doc/overviews-list.doc +++ b/doc/overviews-list.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/pictures.doc b/doc/pictures.doc index b3651eca..676df332 100644 --- a/doc/pictures.doc +++ b/doc/pictures.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/plugins-howto.doc b/doc/plugins-howto.doc index 813dc9c2..c9836686 100644 --- a/doc/plugins-howto.doc +++ b/doc/plugins-howto.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -90,7 +90,7 @@ set your own path or paths you can use \c{QApplication::setLibraryPaths()}. Suppose that you have a new style class called 'MyStyle' that you want -to make available as a plugin. The retquired code is straightforward: +to make available as a plugin. The required code is straightforward: \code class MyStylePlugin : public QStylePlugin { @@ -121,7 +121,7 @@ empty. There are only two virtual functions that must be implemented. The first is keys() which returns a string list of the classes implemented in the plugin. (We've just implemented one class in the example above.) The second is a function that returns an object of the -retquired class (or 0 if the plugin is asked to create an object of a +required class (or 0 if the plugin is asked to create an object of a class that it doesn't implement). For QStylePlugin, this second function is called create(). @@ -130,14 +130,14 @@ single plugin, providing they are all derived from the same base class, e.g. QStylePlugin. For database drivers, image formats, custom widgets and text codecs, -no explicit object creation is retquired. Qt will find and create them -as retquired. Styles are an exception, since you might want to set a +no explicit object creation is required. Qt will find and create them +as required. Styles are an exception, since you might want to set a style explicitly in code. To apply a style, use code like this: \code QApplication::setStyle( QStyleFactory::create( "MyStyle" ) ); \endcode -Some plugin classes retquire additional functions to be implemented. +Some plugin classes require additional functions to be implemented. See the \link designer-manual.book Qt Designer manual's\endlink, 'Creating Custom Widgets' section in the 'Creating Custom Widgets' chapter, for a complete example of a QWidgetPlugin, which implements @@ -150,7 +150,7 @@ must be reimplemented for each type of plugin. Qt applications automatically know which plugins are available, because plugins are stored in the standard plugin subdirectories. -Because of this applications don't retquire any code to find and load +Because of this applications don't require any code to find and load plugins, since Qt handles them automatically. The default directory for plugins is \c{QTDIR/plugins}<sup>*</sup>, @@ -259,7 +259,7 @@ The build key contains the following information: available in two different configurations. However, the developer writing plugins would need to know which features are in use, both in their plugin and internally by the utility - classes in Qt. The Qt library would retquire complex feature + classes in Qt. The Qt library would require complex feature and dependency queries and verification when loading plugins. Retquiring this would place an unnecessary burden on the developer, and increase the overhead of loading a plugin. To reduce both diff --git a/doc/porting2.doc b/doc/porting2.doc index 227ca1dd..3d0fb052 100644 --- a/doc/porting2.doc +++ b/doc/porting2.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -73,7 +73,7 @@ compiler errors (rather than mysterious results), or produce run-time messages. The result is that Qt 2.x includes many additional features, discards obsolete functionality that is easily converted to use the new features, and that porting an application from Qt 1.x to Qt 2.x is -a simple task well worth the amount of effort retquired. +a simple task well worth the amount of effort required. To port code using Qt 1.x to use Qt 2.x: @@ -257,7 +257,7 @@ that took const char* now take const QString&. <p> To take full advantage of the new Internationalization -functionality in Qt 2.x, the following steps are retquired: +functionality in Qt 2.x, the following steps are required: <ul> <li> Start converting all uses of "const char*" in parameters to @@ -890,7 +890,7 @@ use it outside a member function, you'll need to prefix with Qt::. <p>The binary storage format of QPicture is changed, but the Qt 2.x QPicture class can both read and write Qt 1.x format QPictures. No -special handling is retquired for reading; QPicture will automatically +special handling is required for reading; QPicture will automatically detect the version number. In order to write a Qt 1.x format QPicture, set the formatVersion parameter to 1 in the QPicture constructor. diff --git a/doc/porting3.doc b/doc/porting3.doc index bd67bd2f..9b7c0121 100644 --- a/doc/porting3.doc +++ b/doc/porting3.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -429,7 +429,7 @@ The \c echo parameter is the third parameter and defaults to QLineEdit::Normal. If you used calls to QInputDialog::getText(...) that provided more -than the first two retquired parameters you will must add a value +than the first two required parameters you will must add a value for the \c echo parameter. \section1 QLayout and Other Abstract Layout Classes @@ -479,7 +479,7 @@ published the internal data structure. In most cases, applications that used QMultiLineEdit will continue to work without problems. Applications that worked in terms of lines may -retquire some porting. +require some porting. The source code for the old 2.x version of QMultiLineEdit can be found in \c $QTDIR/src/attic/qtmultilineedit.h/cpp. Note that the class has diff --git a/doc/primes.doc b/doc/primes.doc index 8d2e122a..e02c4ef6 100644 --- a/doc/primes.doc +++ b/doc/primes.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/qasciicache.doc b/doc/qasciicache.doc index b2ddcd68..be6cada2 100644 --- a/doc/qasciicache.doc +++ b/doc/qasciicache.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/qasciidict.doc b/doc/qasciidict.doc index ce5cf841..7667684a 100644 --- a/doc/qasciidict.doc +++ b/doc/qasciidict.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/qcache.doc b/doc/qcache.doc index bc1cd9f0..998bb20d 100644 --- a/doc/qcache.doc +++ b/doc/qcache.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/qcollection-compat.doc b/doc/qcollection-compat.doc index 8c8e1639..c642d29f 100644 --- a/doc/qcollection-compat.doc +++ b/doc/qcollection-compat.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/qdict.doc b/doc/qdict.doc index 643fb8de..c522624c 100644 --- a/doc/qdict.doc +++ b/doc/qdict.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/qguardedptr.doc b/doc/qguardedptr.doc index dfa9aab8..872dbc0e 100644 --- a/doc/qguardedptr.doc +++ b/doc/qguardedptr.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/qintcache.doc b/doc/qintcache.doc index ea75eb25..e5960b3e 100644 --- a/doc/qintcache.doc +++ b/doc/qintcache.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/qintdict.doc b/doc/qintdict.doc index 7d26e822..4f6ecc83 100644 --- a/doc/qintdict.doc +++ b/doc/qintdict.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/qmap.doc b/doc/qmap.doc index 89f87442..bbd33820 100644 --- a/doc/qmap.doc +++ b/doc/qmap.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -83,7 +83,7 @@ copy constructors if no explicit version is supplied. In many cases, this is sufficient. - The class used for the key retquires that the \c operator< is + The class used for the key requires that the \c operator< is implemented to define ordering of the keys. QMap's function naming is consistent with the other Qt classes diff --git a/doc/qmemarray.doc b/doc/qmemarray.doc index f849222e..35c18939 100644 --- a/doc/qmemarray.doc +++ b/doc/qmemarray.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -66,7 +66,7 @@ of the arrays is modified, all the arrays are modified. The benefit of sharing is that a program does not need to duplicate - data when it is not retquired, which results in lower memory use + data when it is not required, which results in lower memory use and less copying of data. An alternative to QMemArray is QValueVector. The QValueVector class @@ -158,7 +158,7 @@ sorted arrays (see sort()) you can search using bsearch(). You can set the data directly using setRawData() and - resetRawData(), although this retquires care. + resetRawData(), although this requires care. \sa \link shclass.html Shared Classes\endlink */ diff --git a/doc/qpair.doc b/doc/qpair.doc index e126047f..2245cd10 100644 --- a/doc/qpair.doc +++ b/doc/qpair.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/qptrdict.doc b/doc/qptrdict.doc index df63de64..abc8f155 100644 --- a/doc/qptrdict.doc +++ b/doc/qptrdict.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/qptrlist.doc b/doc/qptrlist.doc index ef5427d1..911dc1b4 100644 --- a/doc/qptrlist.doc +++ b/doc/qptrlist.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -1182,7 +1182,7 @@ \i \< 0 (negative integer) if \a item1 \< \a item2 \endlist - inSort() retquires that compareItems() is implemented as described + inSort() requires that compareItems() is implemented as described here. This function should not modify the list because some const diff --git a/doc/qptrqueue.doc b/doc/qptrqueue.doc index f67f6d21..fbacc25d 100644 --- a/doc/qptrqueue.doc +++ b/doc/qptrqueue.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/qptrstack.doc b/doc/qptrstack.doc index 4829848e..1a84f56e 100644 --- a/doc/qptrstack.doc +++ b/doc/qptrstack.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/qptrvector.doc b/doc/qptrvector.doc index b3082498..4043fe4c 100644 --- a/doc/qptrvector.doc +++ b/doc/qptrvector.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -391,7 +391,7 @@ \i \< 0 (negative integer) if \a d1 \< \a d2 \endlist - The sort() and bsearch() functions retquire compareItems() to be + The sort() and bsearch() functions require compareItems() to be implemented as described here. This function should not modify the vector because some const diff --git a/doc/qsortedlist.doc b/doc/qsortedlist.doc index 2d1462e0..32624e55 100644 --- a/doc/qsortedlist.doc +++ b/doc/qsortedlist.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/qtl.doc b/doc/qtl.doc index bcd5b3ef..59162154 100644 --- a/doc/qtl.doc +++ b/doc/qtl.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -75,7 +75,7 @@ checking than a speed-optimized value based container. If you have objects that implement value semantics, and the STL is not available on your target platform, the Qt Template Library can be used -instead. Value semantics retquire at least: +instead. Value semantics require at least: \list \i a copy constructor; \i an assignment operator; @@ -138,7 +138,7 @@ The same concept applies to the other container classes: There are two kind of iterators, the volatile iterator shown in the examples above and a version that returns a const reference to its -current object, the ConstIterator. Const iterators are retquired +current object, the ConstIterator. Const iterators are required whenever the container itself is const, such as a member variable inside a const function. Assigning a ConstIterator to a normal Iterator is not allowed as it would violate const semantics. diff --git a/doc/qtmac-as-native.doc b/doc/qtmac-as-native.doc index 64849a90..57b281c0 100644 --- a/doc/qtmac-as-native.doc +++ b/doc/qtmac-as-native.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/qvaluelist.doc b/doc/qvaluelist.doc index a9c837d9..6a8a70e8 100644 --- a/doc/qvaluelist.doc +++ b/doc/qvaluelist.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -83,7 +83,7 @@ copy constructors if no explicit version is supplied. In many cases this is sufficient. - In addition, some compilers (e.g. Sun CC) might retquire that the + In addition, some compilers (e.g. Sun CC) might require that the class provides an equality operator (operator==()). QValueList's function naming is consistent with the other Qt diff --git a/doc/qvaluestack.doc b/doc/qvaluestack.doc index 062cde4c..8fa7b774 100644 --- a/doc/qvaluestack.doc +++ b/doc/qvaluestack.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/qvaluevector.doc b/doc/qvaluevector.doc index 1b7360e3..acc1a6c4 100644 --- a/doc/qvaluevector.doc +++ b/doc/qvaluevector.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -290,7 +290,7 @@ \endcode QValueVector stores its elements in contiguous memory. This means - that you can use a QValueVector in any situation that retquires an + that you can use a QValueVector in any situation that requires an array. */ diff --git a/doc/qvfb.doc b/doc/qvfb.doc index bfbf21f8..7bc15466 100644 --- a/doc/qvfb.doc +++ b/doc/qvfb.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/qws.doc b/doc/qws.doc index 1e49621b..419411dc 100644 --- a/doc/qws.doc +++ b/doc/qws.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -341,7 +341,7 @@ TrueType and Type1 support. \title Running Qt/Embedded applications -A Qt/Embedded application retquires a master application to be running +A Qt/Embedded application requires a master application to be running or to be a master application itself. The master application is primarily responsible for managing top-level window regions, and pointer and keyboard input. @@ -456,7 +456,7 @@ explicitly. \title Porting your applications to Qt/Embedded -Existing Qt applications should retquire no porting provided there is no +Existing Qt applications should require no porting provided there is no platform dependent code. Platform dependent code includes system calls, calls to the underlying window system (Windows or X11), and Qt platform specific methods such as QApplication::x11EventFilter(). @@ -472,7 +472,7 @@ using \c #ifdef directives: \row \i Qt/Embedded \i Q_WS_QWS \endtable -Qt/Embedded also retquires the following flags to be defined when compiling +Qt/Embedded also requires the following flags to be defined when compiling applications: \code -DQWS -fno-exceptions -fno-rtti @@ -538,7 +538,7 @@ of QWSMouseHandler in \c embedded/qmouse_qws.cpp. When building embedded applications on low-powered devices, a number of options are available that would not be considered in a desktop application environment. These options reduce the memory and/or CPU -retquirements at the cost of other factors. +requirements at the cost of other factors. \list \i \link emb-features.html <b>Tuning the functionality of Qt\endlink diff --git a/doc/session.doc b/doc/session.doc index 51341d47..6f3185fc 100644 --- a/doc/session.doc +++ b/doc/session.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/shclass.doc b/doc/shclass.doc index c0542f85..418dd459 100644 --- a/doc/shclass.doc +++ b/doc/shclass.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/signalsandslots.doc b/doc/signalsandslots.doc index fc46ce9e..2e1c4cbd 100644 --- a/doc/signalsandslots.doc +++ b/doc/signalsandslots.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -282,13 +282,13 @@ increased flexibility they provide, although the difference for real applications is insignificant. In general, emitting a signal that is connected to some slots, is approximately ten times slower than calling the receivers directly, with non-virtual function calls. This -is the overhead retquired to locate the connection object, to safely +is the overhead required to locate the connection object, to safely iterate over all connections (i.e. checking that subsequent receivers have not been destroyed during the emission) and to marshall any parameters in a generic fashion. While ten non-virtual function calls may sound like a lot, it's much less overhead than any 'new' or 'delete' operation, for example. As soon as you perform a string, -vector or list operation that behind the scene retquires 'new' or +vector or list operation that behind the scene requires 'new' or 'delete', the signals and slots overhead is only responsible for a very small proportion of the complete function call costs. The same is true whenever you do a system call in a slot; or indirectly call more diff --git a/doc/sql-driver.doc b/doc/sql-driver.doc index 584e24bb..0c961257 100644 --- a/doc/sql-driver.doc +++ b/doc/sql-driver.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -121,7 +121,7 @@ instead of \c{C:\program files\mysql}. Use the \c{-qt-sql-<driver>} parameter to build the database driver statically into your Qt library or \c{-plugin-sql-<driver>} to build the driver as a plugin. Look at the sections that follow for -additional information about retquired libraries. +additional information about required libraries. \target buildingmanually \section1 Building the plugins manually @@ -199,7 +199,7 @@ encoding to communicate with the server. \section3 BLOB/LOB support Binary Large Objects (BLOBs) can be read and written, but be aware -that this process may retquire a lot of memory. +that this process may require a lot of memory. Note that Oracle 9 doesn't support scrollable result sets with LOB columns, you have to use a forward only query to select LOB fields @@ -217,10 +217,10 @@ calls to QSqlQuery::value() will only return NULLs. \section3 How to build the plugin on Unix/Linux -All files retquired to build driver should ship with the standard Oracle +All files required to build driver should ship with the standard Oracle Client install. -Oracle library files retquired to build driver: +Oracle library files required to build driver: \list \i \c libclntsh.so (all versions) @@ -303,7 +303,7 @@ then allows you to use these data sources in your Qt project. On Windows systems after 95 an ODBC driver manager should be installed by default, for Unix systems there are some implementations which must be installed first. Note that every client that uses your application -is retquired to have an ODBC driver manager installed, otherwise the +is required to have an ODBC driver manager installed, otherwise the QODBC3 plugin will not work. Be aware that when connecting to an ODBC datasource you must pass in @@ -576,7 +576,7 @@ Firebird databases. Interbase can either be used as a client/server or without a server operating on local files. The database file must exist before a connection can be established. -Note that Interbase retquires you to specify the full path to the +Note that Interbase requires you to specify the full path to the database file, no matter whether it is stored locally or on another server. @@ -632,7 +632,7 @@ ships the tool \c{COFF2OMF.EXE} to convert libraries that have been generated with Microsoft Visual C++. If the compilation of a plugin succeeds but it cannot be loaded, -make sure that the following retquirements are met: +make sure that the following requirements are met: \list \i Ensure that you are using a shared Qt library; you cannot use the diff --git a/doc/sql.doc b/doc/sql.doc index 0c73d1d2..bfd85e8e 100644 --- a/doc/sql.doc +++ b/doc/sql.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -115,7 +115,7 @@ your Qt applications. This overview assumes that you have at least a basic knowledge of SQL. You should be able to understand simple \c SELECT, \c INSERT, \c UPDATE and \c DELETE commands. Although the \l QSqlCursor class provides an -interface to database browsing and editing that does not \e retquire a +interface to database browsing and editing that does not \e require a knowledge of SQL, a basic understanding of SQL is highly recommended. A standard text covering SQL databases is \e {An Introduction to Database Systems (7th ed.)} by C. J. Date, ISBN 0201385902. @@ -219,10 +219,10 @@ At least one database connection must be created and opened before the If the application only needs a single database connection, the \l QSqlDatabase class can create a connection which is used by default -for all SQL operations. If multiple database connections are retquired +for all SQL operations. If multiple database connections are required these can easily be set up. -\l QSqlDatabase retquires the \c qsqldatabase.h header file. +\l QSqlDatabase requires the \c qsqldatabase.h header file. \target Connecting_to_a_Single_Database \section1 Connecting to a Single Database @@ -513,7 +513,7 @@ follows this one we show how to link widgets to database cursors. Once we have a knowledge of both cursors and data-aware widgets we can discuss \link #Subclassing_QSqlCursor subclassing QSqlCursor \endlink. -The \l QSqlCursor class retquires the \c qsqlcursor.h header file. +The \l QSqlCursor class requires the \c qsqlcursor.h header file. \target Retrieving_Records \section2 Retrieving Records @@ -734,7 +734,7 @@ iteration we call the cursor's primeInsert() method. This method returns a pointer to a \l QSqlRecord buffer in which all the fields are set to \c NULL. (Note that QSqlCursor::primeInsert() is virtual, and can be customized by derived classes. See \l QSqlCursor). Next we -call setValue() for each field that retquires a value. Finally we call +call setValue() for each field that requires a value. Finally we call insert() to insert the record. The insert() call returns the number of rows inserted. @@ -815,7 +815,7 @@ examples provides additional information. \printline \caption From \l sql/overview/table1/main.cpp -Data-Aware tables retquire the \c qdatatable.h and \c qsqlcursor.h header +Data-Aware tables require the \c qdatatable.h and \c qsqlcursor.h header files. We create our application object, call createConnections() and create the cursor. We create the \l QDataTable passing it a pointer to the cursor, and set the autoPopulate flag to TRUE. Next we make our \l @@ -1144,7 +1144,7 @@ leave the loop. When the user edits the status field in the QDataTable they will be presented with a combobox of valid status names taken from the status table. However the status displayed is still the raw statusid. To -display the status name when the field isn't being edited retquires us +display the status name when the field isn't being edited requires us to subclass QDataTable and reimplement the paintField() function. \quotefile sql/overview/table4/main.h @@ -1214,7 +1214,7 @@ this stage. \skipto InvoiceItemCursor \printline InvoiceItemCursor -Whenever we retquire a cursor over the invoiceitem table we can create +Whenever we require a cursor over the invoiceitem table we can create an InvoiceItemCursor instead of a generic QSqlCursor. We still need to show the product name rather than the pricesid. @@ -1260,7 +1260,7 @@ which perform real calculations. The header file, \l sql/overview/subclass4/main.h, remains unchanged from the previous example, but the constructor and calculateField() -function retquire some simple expansion. We'll look at each in turn. +function require some simple expansion. We'll look at each in turn. \quotefile sql/overview/subclass4/main.cpp \skipto InvoiceItem diff --git a/doc/table.doc b/doc/table.doc index cb8f0eba..f6e26a9e 100644 --- a/doc/table.doc +++ b/doc/table.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/threads.doc b/doc/threads.doc index d0619522..9ef527d3 100644 --- a/doc/threads.doc +++ b/doc/threads.doc @@ -17,7 +17,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/tutorial.doc b/doc/tutorial.doc index ad56d271..8bd72186 100644 --- a/doc/tutorial.doc +++ b/doc/tutorial.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -1050,7 +1050,7 @@ loop upon the first change of one of the values. \printline QGridLayout \printline 2x2 -So far we have used the no-assembly-retquired QVBox and QGrid widgets +So far we have used the no-assembly-required QVBox and QGrid widgets for geometry management. Now, however, we want to have a little more control over the layout, and we switch to the more powerful QGridLayout class. QGridLayout isn't a widget; it is a different class that can diff --git a/doc/tutorial2.doc b/doc/tutorial2.doc index 91099788..ad20fef6 100644 --- a/doc/tutorial2.doc +++ b/doc/tutorial2.doc @@ -94,7 +94,7 @@ The chart form's main widget is a QCanvasView which displays the QCanvas on which we draw the pie chart or bar graph. We subclass QCanvasView to obtain some specialised behaviour. Similarly we subclass the QCanvasText class (used to place text items on a canvas) -since we retquire slightly more than the standard class provides. +since we require slightly more than the standard class provides. The project file, \c chart.pro, is used to create the Makefile that is used to build the application. @@ -249,7 +249,7 @@ filter the data using a scripting language. \skipto include \printto const -Our implementation of the operators retquires the inclusion of \c +Our implementation of the operators requires the inclusion of \c qtextstream.h and \c qstringlist.h. \printto Element @@ -432,7 +432,7 @@ toolbar buttons stay in sync and saves duplicating code. When we construct an action we give it a name, an optional icon, a menu text, and an accelerator short-cut key (or 0 if no accelerator is -retquired). We also make it a child of the form (by passing \c this). +required). We also make it a child of the form (by passing \c this). When the user clicks a toolbar button or clicks a menu option the \c activated() signal is emitted. We connect() this signal to the action's slot, in the snippet shown above, to fileNew(). @@ -784,7 +784,7 @@ Qt rather than good (or bad) algorithms for drawing charts. To draw a horizontal bar chart we need the array of scaled values, the total value (so that we can calculate and draw percentages if -retquired) and a count of the number of values. +required) and a count of the number of values. \skipto width \printuntil int y @@ -1130,7 +1130,7 @@ correct number of decimal places. \i The OK button is connected to the accept() slot; we will update the elements vector in this slot. \i The Cancel button is connected to the QDialog reject() slot, and -retquires no further code or action on our part. +requires no further code or action on our part. \endlist \skipto QPixmap diff --git a/doc/unicode.doc b/doc/unicode.doc index bf6f7545..6e300945 100644 --- a/doc/unicode.doc +++ b/doc/unicode.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/winsystem.doc b/doc/winsystem.doc index 7611e4a3..0b305bbd 100644 --- a/doc/winsystem.doc +++ b/doc/winsystem.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -77,7 +77,7 @@ if you have queries.} \section2 Microsoft Visual Studio 2005 Deployment Issues -Executables compiled with Microsoft Visual Studio 2005 retquire +Executables compiled with Microsoft Visual Studio 2005 require a manifest file that points to the C and C++ runtime libraries that Qt and the application itself depend on. The manifest file is automatically generated for you, but it always needs to be located diff --git a/doc/xml-sax-features-walkthrough.doc b/doc/xml-sax-features-walkthrough.doc index bc57a3c0..0b62e9f9 100644 --- a/doc/xml-sax-features-walkthrough.doc +++ b/doc/xml-sax-features-walkthrough.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/xml-sax-walkthrough.doc b/doc/xml-sax-walkthrough.doc index e732a00a..40bec422 100644 --- a/doc/xml-sax-walkthrough.doc +++ b/doc/xml-sax-walkthrough.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: diff --git a/doc/xml.doc b/doc/xml.doc index 30f4d120..733f2b39 100644 --- a/doc/xml.doc +++ b/doc/xml.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -258,7 +258,7 @@ http://xml.org/sax/features/validation (the ability to report validation errors). Whilst SAX2 leaves it to the user to define and implement whatever -features are retquired, support for \e +features are required, support for \e http://xml.org/sax/features/namespace (and thus \e http://xml.org/sax/features/namespace-prefixes) is mandantory. The \l QXmlSimpleReader implementation of \l QXmlReader, @@ -365,7 +365,7 @@ useful if a reader supports special handler classes. The URIs used for features and properties often look like URLs, e.g. \c http://xml.org/sax/features/namespace. This does not mean that the -data retquired is at this address. It is simply a way of defining +data required is at this address. It is simply a way of defining unique names. Anyone can define and use new SAX2 properties for their readers. @@ -624,7 +624,7 @@ the context of namespaces: local part of \e book:title.) \i The \e {namespace URI} ("Uniform Resource Identifier") is a unique identifier for a namespace. It looks like a URL - (e.g. \e http://trolltech.com/fnord/ ) but does not retquire + (e.g. \e http://trolltech.com/fnord/ ) but does not require data to be accessible by the given protocol at the named address. \endlist diff --git a/doc/y2k.doc b/doc/y2k.doc index d57b1335..77f155bf 100644 --- a/doc/y2k.doc +++ b/doc/y2k.doc @@ -16,7 +16,7 @@ ** and the KDE Free Qt Foundation. ** ** Please review the following information to ensure GNU General -** Public Licensing retquirements will be met: +** Public Licensing requirements will be met: ** http://trolltech.com/products/qt/licenses/licensing/opensource/. ** If you are unsure which license is appropriate for your use, please ** review the following information: @@ -40,7 +40,7 @@ \title Year 2000 Compliance Statement -Trolltech defines <i>Year 2000 Compliance</i> as a retquirement that a +Trolltech defines <i>Year 2000 Compliance</i> as a requirement that a product or part of product does not contain errors related to transition from December 31, 1999 to January 1, 2000, or to the existence of February 29, 2000. |