diff options
Diffstat (limited to 'doc')
139 files changed, 335 insertions, 335 deletions
diff --git a/doc/application-walkthrough.doc b/doc/application-walkthrough.doc index e3a5aa6a8..4527eeba3 100644 --- a/doc/application-walkthrough.doc +++ b/doc/application-walkthrough.doc @@ -95,7 +95,7 @@ system caption to "Document 1", and \e show() it. \target close \printline connect -When the application's last window is closed, it should tquit. Both +When the application's last window is closed, it should quit. Both the signal and the slot are predefined members of QApplication. \printline exec @@ -111,7 +111,7 @@ that QApplication returns when it leaves the event loop. \quotefile application/application.cpp -Since the implementation is tquite large (almost 300 lines) we +Since the implementation is quite large (almost 300 lines) we won't list the whole thing. (The source code is included in the examples/application directory.) Before we start with the constructor there are three \c{#include}s worth mentioning: diff --git a/doc/faq.doc b/doc/faq.doc index c187ddbfb..e36d75046 100644 --- a/doc/faq.doc +++ b/doc/faq.doc @@ -122,7 +122,7 @@ Qtopia. You can find a partial list here: <hr width="30%"> \section2 Are there any books about Qt programming? -Yes, there are tquite a few books on Qt, most of them +Yes, there are quite a few books on Qt, most of them available from amazon.com. You can find a partial list at \l http://www.trolltech.com/developer/books.html. diff --git a/doc/html/addressbook-example.html b/doc/html/addressbook-example.html index d9c38d120..aa5da536a 100644 --- a/doc/html/addressbook-example.html +++ b/doc/html/addressbook-example.html @@ -141,7 +141,7 @@ void <a name="f264"></a>ABMainWindow::setupMenuBar() file-><a href="qmenudata.html#insertItem">insertItem</a>( TQPixmap( "fileprint.xpm" ), "Print...", this, SLOT( filePrint() ), CTRL + Key_P ); file-><a href="qmenudata.html#insertSeparator">insertSeparator</a>(); file-><a href="qmenudata.html#insertItem">insertItem</a>( "Close", this, SLOT( closeWindow() ), CTRL + Key_W ); - file-><a href="qmenudata.html#insertItem">insertItem</a>( "Quit", qApp, SLOT( <a href="qapplication.html#tquit">tquit</a>() ), CTRL + Key_Q ); + file-><a href="qmenudata.html#insertItem">insertItem</a>( "Quit", qApp, SLOT( <a href="qapplication.html#quit">quit</a>() ), CTRL + Key_Q ); } void <a name="f265"></a>ABMainWindow::setupFileTools() @@ -647,7 +647,7 @@ int main( int argc, char ** argv ) a.<a href="qapplication.html#setMainWidget">setMainWidget</a>( mw ); <a name="x611"></a> mw-><a href="qwidget.html#show">show</a>(); -<a name="x609"></a><a name="x608"></a> a.<a href="qobject.html#connect">connect</a>( &a, SIGNAL( <a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>() ), &a, SLOT( <a href="qapplication.html#tquit">tquit</a>() ) ); +<a name="x609"></a><a name="x608"></a> a.<a href="qobject.html#connect">connect</a>( &a, SIGNAL( <a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>() ), &a, SLOT( <a href="qapplication.html#quit">quit</a>() ) ); int result = a.<a href="qapplication.html#exec">exec</a>(); delete mw; return result; diff --git a/doc/html/archivesearch-example.html b/doc/html/archivesearch-example.html index 86e653d61..32dba910c 100644 --- a/doc/html/archivesearch-example.html +++ b/doc/html/archivesearch-example.html @@ -165,7 +165,7 @@ int main(int argc, char **argv) ad.show(); <a name="x489"></a><a name="x487"></a> TQObject::<a href="qobject.html#connect">connect</a>( &a, SIGNAL(<a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>()), -<a name="x488"></a> &a, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); +<a name="x488"></a> &a, SLOT(<a href="qapplication.html#quit">quit</a>()) ); <a name="x486"></a> return a.<a href="qapplication.html#exec">exec</a>(); } diff --git a/doc/html/canvas-chart-example.html b/doc/html/canvas-chart-example.html index f702c7656..19df8421b 100644 --- a/doc/html/canvas-chart-example.html +++ b/doc/html/canvas-chart-example.html @@ -372,7 +372,7 @@ const <a href="qstring.html">TQString</a> APP_KEY = "/Chart/"; <a href="qobject.html#connect">connect</a>( optionsSetOptionsAction, SIGNAL( <a href="qaction.html#activated">activated</a>() ), this, SLOT( optionsSetOptions() ) ); - fileQuitAction = new <a href="qaction.html">TQAction</a>( "Quit", "&Quit", CTRL+Key_Q, this, "tquit" ); + fileQuitAction = new <a href="qaction.html">TQAction</a>( "Quit", "&Quit", CTRL+Key_Q, this, "quit" ); <a href="qobject.html#connect">connect</a>( fileQuitAction, SIGNAL( <a href="qaction.html#activated">activated</a>() ), this, SLOT( fileQuit() ) ); diff --git a/doc/html/canvas-example.html b/doc/html/canvas-example.html index 804f4c1ae..dc662e95b 100644 --- a/doc/html/canvas-example.html +++ b/doc/html/canvas-example.html @@ -454,7 +454,7 @@ static TQImage *logoimg; file-><a href="qmenudata.html#insertSeparator">insertSeparator</a>(); file-><a href="qmenudata.html#insertItem">insertItem</a>("&Print...", this, SLOT(print()), CTRL+Key_P); file-><a href="qmenudata.html#insertSeparator">insertSeparator</a>(); - file-><a href="qmenudata.html#insertItem">insertItem</a>("E&xit", qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()), CTRL+Key_Q); + file-><a href="qmenudata.html#insertItem">insertItem</a>("E&xit", qApp, SLOT(<a href="qapplication.html#quit">quit</a>()), CTRL+Key_Q); menu-><a href="qmenudata.html#insertItem">insertItem</a>("&File", file); <a href="qpopupmenu.html">TQPopupMenu</a>* edit = new <a href="qpopupmenu.html">TQPopupMenu</a>( menu ); @@ -922,7 +922,7 @@ int main(int argc, char** argv) else <a name="x2968"></a> m.<a href="qwidget.html#showMaximized">showMaximized</a>(); - TQObject::<a href="qobject.html#connect">connect</a>( qApp, SIGNAL(<a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>()), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + TQObject::<a href="qobject.html#connect">connect</a>( qApp, SIGNAL(<a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>()), qApp, SLOT(<a href="qapplication.html#quit">quit</a>()) ); return app.<a href="qapplication.html#exec">exec</a>(); } diff --git a/doc/html/chart-chartform-cpp.html b/doc/html/chart-chartform-cpp.html index 2adbe2f30..0af8bdcb6 100644 --- a/doc/html/chart-chartform-cpp.html +++ b/doc/html/chart-chartform-cpp.html @@ -160,7 +160,7 @@ const <a href="qstring.html">TQString</a> APP_KEY = "/Chart/"; <a href="qobject.html#connect">connect</a>( optionsSetOptionsAction, SIGNAL( <a href="qaction.html#activated">activated</a>() ), this, SLOT( optionsSetOptions() ) ); - fileQuitAction = new <a href="qaction.html">TQAction</a>( "Quit", "&Quit", CTRL+Key_Q, this, "tquit" ); + fileQuitAction = new <a href="qaction.html">TQAction</a>( "Quit", "&Quit", CTRL+Key_Q, this, "quit" ); <a href="qobject.html#connect">connect</a>( fileQuitAction, SIGNAL( <a href="qaction.html#activated">activated</a>() ), this, SLOT( fileQuit() ) ); diff --git a/doc/html/clientserver-example.html b/doc/html/clientserver-example.html index 97547494e..e43ac9e61 100644 --- a/doc/html/clientserver-example.html +++ b/doc/html/clientserver-example.html @@ -166,12 +166,12 @@ public: <a href="qlabel.html">TQLabel</a> *lb = new <a href="qlabel.html">TQLabel</a>( itext, this ); <a name="x784"></a> lb-><a href="qlabel.html#setAlignment">setAlignment</a>( AlignHCenter ); infoText = new <a href="qtextview.html">TQTextView</a>( this ); - <a href="qpushbutton.html">TQPushButton</a> *tquit = new <a href="qpushbutton.html">TQPushButton</a>( tr("Quit") , this ); + <a href="qpushbutton.html">TQPushButton</a> *quit = new <a href="qpushbutton.html">TQPushButton</a>( tr("Quit") , this ); connect( server, SIGNAL(newConnect(ClientSocket*)), SLOT(newConnect(ClientSocket*)) ); - connect( tquit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, - SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + connect( quit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, + SLOT(<a href="qapplication.html#quit">quit</a>()) ); } ~ServerInfo() @@ -245,11 +245,11 @@ public: inputText = new <a href="qlineedit.html">TQLineEdit</a>( hb ); <a href="qpushbutton.html">TQPushButton</a> *send = new <a href="qpushbutton.html">TQPushButton</a>( tr("Send") , hb ); <a href="qpushbutton.html">TQPushButton</a> *close = new <a href="qpushbutton.html">TQPushButton</a>( tr("Close connection") , this ); - <a href="qpushbutton.html">TQPushButton</a> *tquit = new <a href="qpushbutton.html">TQPushButton</a>( tr("Quit") , this ); + <a href="qpushbutton.html">TQPushButton</a> *quit = new <a href="qpushbutton.html">TQPushButton</a>( tr("Quit") , this ); <a name="x792"></a> connect( send, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), SLOT(sendToServer()) ); connect( close, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), SLOT(closeConnection()) ); - connect( tquit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + connect( quit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#quit">quit</a>()) ); // create the socket and connect various of its signals socket = new <a href="qsocket.html">TQSocket</a>( this ); diff --git a/doc/html/customlayout-example.html b/doc/html/customlayout-example.html index 5c26c5f1c..30fb9f1ff 100644 --- a/doc/html/customlayout-example.html +++ b/doc/html/customlayout-example.html @@ -778,7 +778,7 @@ int main( int argc, char **argv ) b1-><a href="qlayout.html#add">add</a>( new <a href="qpushbutton.html">TQPushButton</a>( "More text", f ) ); b1-><a href="qlayout.html#add">add</a>( new <a href="qpushbutton.html">TQPushButton</a>( "Even longer button text", f ) ); <a href="qpushbutton.html">TQPushButton</a>* qb = new <a href="qpushbutton.html">TQPushButton</a>( "Quit", f ); - a.<a href="qobject.html#connect">connect</a>( qb, SIGNAL( <a href="qbutton.html#clicked">clicked</a>() ), SLOT( tquit() ) ); + a.<a href="qobject.html#connect">connect</a>( qb, SIGNAL( <a href="qbutton.html#clicked">clicked</a>() ), SLOT( quit() ) ); b1-><a href="qlayout.html#add">add</a>( qb ); <a href="qwidget.html">TQWidget</a> *wid = new <a href="qwidget.html">TQWidget</a>( f ); diff --git a/doc/html/designer-manual-2.html b/doc/html/designer-manual-2.html index c8d3c4889..1e9c4869f 100644 --- a/doc/html/designer-manual-2.html +++ b/doc/html/designer-manual-2.html @@ -108,7 +108,7 @@ body { background: #ffffff; color: black; } </ul><p>We will change a few properties for each of the push buttons in the <em>Property Editor</em> window.</p> <ul><li><p>Click the left-most push button, and change its name to "clearPushButton", and its text to "&Clear".</p> <li><p>Click the middle push button and change its name to "calculatePushButton", its text to "Calculate", and its default property to "True".</p> -<li><p>Click the right-most push button, change its name to "tquitPushButton", and change its text to "&Quit".</p> +<li><p>Click the right-most push button, change its name to "quitPushButton", and change its text to "&Quit".</p> </ul><p align="center"><img align="middle" src="qs-pushbutt.png" width="428" height="232"> </p> <h5><a name="3-1-4"></a>Adding Spacers</h5> @@ -179,9 +179,9 @@ body { background: #ffffff; color: black; } <li><p>Select clearPushButton for the Sender, clicked() for the Signal, numberLineEdit for the Receiver, and setFocus() for the Slot.</p> </ul><p align="center"><img align="middle" src="qs-editconn1.png" width="608" height="391"> </p> -<p>We also need to connect the tquit button to the form:</p> +<p>We also need to connect the quit button to the form:</p> <ul><li><p>Click <b>New</b>.</p> -<li><p>Select tquitPushButton for Sender, clicked() for Signal, ConversionForm for Receiver, and close() for Slot.</p> +<li><p>Select quitPushButton for Sender, clicked() for Signal, ConversionForm for Receiver, and close() for Slot.</p> </ul><p>We want to connect the calculate button and the other widgets, but the slot we want to use is not listed in the combobox. We will need to create a new slot so that we can select it from the list to complete our connections.</p> <ul><li><p>Click <b>New</b>.</p> <li><p>Select calculatePushButton for the Sender, clicked() for the Signal, and ConversionForm for the Receiver.</p> diff --git a/doc/html/designer-manual-3.html b/doc/html/designer-manual-3.html index 46fdd66ff..4d584665d 100644 --- a/doc/html/designer-manual-3.html +++ b/doc/html/designer-manual-3.html @@ -126,7 +126,7 @@ 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 tquite 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 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> </blockquote> <h4><a name="4-3"></a>Adding Custom Actions</h4> @@ -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 tquite 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 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> <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> @@ -474,7 +474,7 @@ body { background: #ffffff; color: black; } </pre> <p>When <em>TQt Designer</em> generates a <tt>main.cpp</tt> file it includes this line:</p> <pre> - a.connect( &a, SIGNAL( lastWindowClosed() ), &a, SLOT( tquit() ) ); + a.connect( &a, SIGNAL( lastWindowClosed() ), &a, SLOT( quit() ) ); </pre> <p>If we left this code as-is, the user could by-pass our own termination code by clicking the main window's close (X) button. Since we want to give the user the option to save any unsaved changes we need to ensure that we intercept any attempt to close the application. To achieve this we delete the connection and add a new slot, <tt>closeEvent()</tt> which will intercept attempts to close the application and call our <tt>fileExit()</tt> function.</p> <p>Click <tt>main.cpp</tt> in the Project Overview window. The file will appear in an editing window. Delete the connect line.</p> diff --git a/doc/html/designer-manual-4.html b/doc/html/designer-manual-4.html index fd642a9da..17b27fcfb 100644 --- a/doc/html/designer-manual-4.html +++ b/doc/html/designer-manual-4.html @@ -201,7 +201,7 @@ body { background: #ffffff; color: black; } } } </pre> - <p>The code for this function is tquite long, but it isn't difficult. We start by setting a default color to white. If there are any colors in the <tt>m_colors</tt> map we set the default color to be the current color showing in the current view. We then invoke TQt's static <a href="qcolordialog.html#getColor">getColor()</a> dialog, passing it the default color. (If the user cancels an invalid color is returned.)</p> + <p>The code for this function is quite long, but it isn't difficult. We start by setting a default color to white. If there are any colors in the <tt>m_colors</tt> map we set the default color to be the current color showing in the current view. We then invoke TQt's static <a href="qcolordialog.html#getColor">getColor()</a> dialog, passing it the default color. (If the user cancels an invalid color is returned.)</p> <p>If the user chose a color we want to show their chosen color in our custom dialog, so we create a pixmap and fill it with their chosen color. We create an instance of our ColorNameForm as a modal dialog (third argument is TRUE). We then call its <tt>setColors()</tt> function to set the colors in the <tt>m_colors</tt> map (so that the <tt>validate()</tt> function will work correctly). We set its colorLabel's pixmap to the pixmap we've just created, i.e. to a rectangle in the user's chosen color.</p> <p>We execute (<tt>exec()</tt>) the dialog. If the user clicks OK (and the color name they've entered is valid), the call will return a true value. In this case we retrieve the name they've entered from the line edit and create a new entry in the <tt>m_colors</tt> map using the name the user has given and the color they chose.</p> <p>At this point we could simply mark the views "dirty" and call repopulate. Instead we'll add the new color to each view directly and save the overhead of a full update (which might be considerable if we have thousands of colors).</p> diff --git a/doc/html/designer-manual-5.html b/doc/html/designer-manual-5.html index 80cbf8da8..61b38dff4 100644 --- a/doc/html/designer-manual-5.html +++ b/doc/html/designer-manual-5.html @@ -66,7 +66,7 @@ body { background: #ffffff; color: black; } <p align="center"><img align="middle" src="designer1.jpg"> </p> <p><em>TQt Designer</em> reads and writes <tt>.ui</tt> files, e.g. <tt>form.ui</tt>. The user interface compiler, <tt>uic</tt>, creates both a header file, e.g. <tt>form.h</tt>, and an implementation file, e.g. <tt>form.cpp</tt>, from the <tt>.ui</tt> file. The application code in <tt>main.cpp</tt> <tt>#include</tt>s <tt>form.h</tt>. Typically <tt>main.cpp</tt> is used to instantiate the TQApplication object and start off the event loop.</p> -<p>While this approach is simple, it isn't sufficient for more complex dialogs. Complex dialogs tend to have tquite a lot of logic attached to the form's widgets, more logic than can usually be expressed with predefined signals and slots. One way of handling this extra logic is to write a controller class in the application code that adds functionality to the form. This is possible because <tt>uic</tt> generated classes expose a form's controls and their signals to the public space. The big disadvantage of this method is that it's not exactly TQt-style. If you were not using <em>TQt Designer</em>, you would almost always add the logic to the form itself, where it belongs.</p> +<p>While this approach is simple, it isn't sufficient for more complex dialogs. Complex dialogs tend to have quite a lot of logic attached to the form's widgets, more logic than can usually be expressed with predefined signals and slots. One way of handling this extra logic is to write a controller class in the application code that adds functionality to the form. This is possible because <tt>uic</tt> generated classes expose a form's controls and their signals to the public space. The big disadvantage of this method is that it's not exactly TQt-style. If you were not using <em>TQt Designer</em>, you would almost always add the logic to the form itself, where it belongs.</p> <p>This is why the capability of adding custom slots and member variables to a form was added to <em>TQt Designer</em> early on. The big additional benefit with this approach is that you can use <em>TQt Designer</em> to connect signals to those custom slots, in the same elegant graphical way that is used to connect signals to predefined slots. The <tt>uic</tt> then adds an empty stub for each custom slot to the generated <tt>form.cpp</tt> implementation file.</p> <p>The big question now is how to add custom implementation code to those custom slots. Adding code to the generated <tt>form.cpp</tt> is not an option, as this file gets recreated by the <tt>uic</tt> whenever the form changes -- and we don't want a combination of generated and handwritten code. There are two possible solutions, which we'll cover next.</p> <h4><a name="3-1"></a>The subclassing approach</h4> diff --git a/doc/html/designer-manual-6.html b/doc/html/designer-manual-6.html index a1997e542..9c9845df8 100644 --- a/doc/html/designer-manual-6.html +++ b/doc/html/designer-manual-6.html @@ -176,7 +176,7 @@ 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> <h4><a name="2-2"></a>Creating main.cpp</h4> -<p>The<!-- index main.cpp --> <tt>main.cpp</tt> is tquite 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> +<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>> #include "mainform.h" @@ -194,7 +194,7 @@ INCLUDEPATH += $(QTDIR)/tools/designer/uilib <p>We create a new instance of our MainForm class, set it to be the main widget, show it and enter the event loop in the <tt>app.exec()</tt> call.</p> <h4><a name="2-3"></a>Creating the Main Form</h4> <h5><a name="2-3-1"></a>Designing the Form</h5> -<ol type=1><li><p>Open the<!-- index receiver.pro --> <tt>receiver.pro</tt> project file in <em>TQt Designer</em>. We'll create a dialog as our main window which we'll use to invoke the dynamic dialog. Press <b>Ctrl+N</b> to launch the <em>New File</em> dialog and click <b>OK</b> to get the default which is a dialog. Change the dialog's name to 'MainForm' and its caption to 'Main Form'. Add two buttons, one called 'creditPushButton' with the text '&Credit Dialog', and the other called 'tquitPushButton' with the text '&Quit'. (For each button click the <b>Push Button</b> toolbar button, then click the form. Change the properties in the property window to those we've just described.)</p> +<ol type=1><li><p>Open the<!-- index receiver.pro --> <tt>receiver.pro</tt> project file in <em>TQt Designer</em>. We'll create a dialog as our main window which we'll use to invoke the dynamic dialog. Press <b>Ctrl+N</b> to launch the <em>New File</em> dialog and click <b>OK</b> to get the default which is a dialog. Change the dialog's name to 'MainForm' and its caption to 'Main Form'. Add two buttons, one called 'creditPushButton' with the text '&Credit Dialog', and the other called 'quitPushButton' with the text '&Quit'. (For each button click the <b>Push Button</b> toolbar button, then click the form. Change the properties in the property window to those we've just described.)</p> <li><p>We will now add a couple of labels so that we can show the settings the user chose in the dynamic dialog. Click the <b>Text Label</b> toolbar button, then click the form below the Credit Dialog button. Change the label's <em>text</em> to 'Credit Rating'. Add another text label below the Quit button. Change its <em>name</em> to 'ratingTextLabel' and its <em>text</em> to 'Unrated'.</p> <li><p>We'll now lay out the widgets. Click the form then press <b>Ctrl+G</b> (lay out in a grid).</p> <li><!-- index Signals and Slots!Connecting to Close a Dialog --><p>We'll now handle the signals and slots connections. Invoke the <em>View and Edit Connections</em> dialog and connect the credit dialog button's clicked() signal to a new creditDialog() custom slot (which is created by clicking the <b>Edit Slots...</b> button). Now connect the Quit button's<!-- index clicked() --> <tt>clicked()</tt> signal to the dialog's<!-- index accept() --> <tt>accept()</tt> function.</p> diff --git a/doc/html/extension-dialog-example.html b/doc/html/extension-dialog-example.html index 323ea73c1..5951601ca 100644 --- a/doc/html/extension-dialog-example.html +++ b/doc/html/extension-dialog-example.html @@ -100,7 +100,7 @@ void MainForm::optionsDlg() } -void MainForm::tquit() +void MainForm::quit() { <a name="x2865"></a> TQApplication::<a href="qapplication.html#exit">exit</a>( 0 ); } @@ -151,7 +151,7 @@ int main( int argc, char ** argv ) <a href="qapplication.html">TQApplication</a> a( argc, argv ); MainForm *w = new MainForm; w->show(); -<a name="x2868"></a><a name="x2867"></a> a.<a href="qobject.html#connect">connect</a>( &a, SIGNAL( <a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>() ), w, SLOT( tquit() ) ); +<a name="x2868"></a><a name="x2867"></a> a.<a href="qobject.html#connect">connect</a>( &a, SIGNAL( <a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>() ), w, SLOT( quit() ) ); return a.<a href="qapplication.html#exec">exec</a>(); } </pre> diff --git a/doc/html/faq.html b/doc/html/faq.html index 5e149419a..d49d39850 100644 --- a/doc/html/faq.html +++ b/doc/html/faq.html @@ -243,7 +243,7 @@ TQtopia. You can find a partial list here: <p> <hr width="30%"> <h3> Are there any books about TQt programming? </h3> -<a name="1-9"></a><p> Yes, there are tquite a few books on TQt, most of them +<a name="1-9"></a><p> Yes, there are quite a few books on TQt, most of them available from amazon.com. You can find a partial list at <a href="http://www.trolltech.com/developer/books.html">http://www.trolltech.com/developer/books.html</a>. <p> The official TQt book is diff --git a/doc/html/functions.html b/doc/html/functions.html index bbc257df5..60603f000 100644 --- a/doc/html/functions.html +++ b/doc/html/functions.html @@ -2129,8 +2129,8 @@ qAddPostRoutine: <a href="qstyle.html#querySubControl">TQStyle</a><li>querySubControlMetrics: <a href="qstyle.html#querySubControlMetrics">TQStyle</a><li>querySubObject: <a href="qaxbase.html#querySubObject">TQAxBase</a> <a href="qaxbase.html#querySubObject">TQAxObject</a> <a href="qaxbase.html#querySubObject">TQAxWidget</a><li>question: - <a href="qmessagebox.html#question">TQMessageBox</a><li>tquit: - <a href="qapplication.html#tquit">TQApplication</a><li>qwsDecoration: + <a href="qmessagebox.html#question">TQMessageBox</a><li>quit: + <a href="qapplication.html#quit">TQApplication</a><li>qwsDecoration: <a href="qapplication.html#qwsDecoration">TQApplication</a><li>qwsEvent: <a href="qwidget.html#qwsEvent">TQWidget</a><li>qwsEventFilter: <a href="qapplication.html#qwsEventFilter">TQApplication</a><li>qwsRenderToDisk: diff --git a/doc/html/geometry.html b/doc/html/geometry.html index 8c26de976..027a59492 100644 --- a/doc/html/geometry.html +++ b/doc/html/geometry.html @@ -66,7 +66,7 @@ will complain to you. TQt can do is to send certain hints to the window manager. The window manager, a separate process, may either obey, ignore or misunderstand them. Due to the partially unclear Inter-Client Communication -Conventions Manual (ICCCM), window placement is handled tquite +Conventions Manual (ICCCM), window placement is handled quite differently in existing window managers. <p> X11 provides no standard or easy way to get the frame geometry once the window is decorated. TQt solves this problem with nifty heuristics diff --git a/doc/html/guibooks.html b/doc/html/guibooks.html index 5319711e8..b925bcdd7 100644 --- a/doc/html/guibooks.html +++ b/doc/html/guibooks.html @@ -67,7 +67,7 @@ Doing what it tells you to <em>do</em> helps, too. OS 8 addendum.</a> <p> <b>The Microsoft Windows User Experience</b>, ISBN 1-55615-679-0, is Microsoft's look and feel Bible. Indispensable for everyone who -has customers that worship Microsoft, and it's tquite good, too. +has customers that worship Microsoft, and it's quite good, too. <a href="http://www.amazon.com/exec/obidos/ASIN/0735605661/trolltech/t">(Read more or buy it.)</a> <p> Microsoft's guidelines are often available on the web, but have occasionally been hidden in an impenetrable maze of javascript. diff --git a/doc/html/hello-example.html b/doc/html/hello-example.html index 416f8e638..31f338144 100644 --- a/doc/html/hello-example.html +++ b/doc/html/hello-example.html @@ -215,7 +215,7 @@ int main( int argc, char **argv ) #ifndef QT_NO_WIDGET_TOPEXTRA // for TQt/Embedded minimal build h.<a href="qwidget.html#setCaption">setCaption</a>( "TQt says hello" ); #endif - TQObject::<a href="qobject.html#connect">connect</a>( &h, SIGNAL(clicked()), &a, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + TQObject::<a href="qobject.html#connect">connect</a>( &h, SIGNAL(clicked()), &a, SLOT(<a href="qapplication.html#quit">quit</a>()) ); <a name="x1650"></a> h.<a href="qwidget.html#setFont">setFont</a>( TQFont("times",32,TQFont::Bold) ); // default font <a name="x1648"></a> h.<a href="qwidget.html#setBackgroundColor">setBackgroundColor</a>( TQt::white ); // default bg color a.<a href="qapplication.html#setMainWidget">setMainWidget</a>( &h ); diff --git a/doc/html/helpviewer-example.html b/doc/html/helpviewer-example.html index c0b4ad5f5..005739c72 100644 --- a/doc/html/helpviewer-example.html +++ b/doc/html/helpviewer-example.html @@ -463,7 +463,7 @@ int main( int argc, char ** argv ) <a name="x1045"></a> help-><a href="qwidget.html#showMaximized">showMaximized</a>(); <a name="x1039"></a> TQObject::<a href="qobject.html#connect">connect</a>( &a, SIGNAL(<a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>()), - &a, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + &a, SLOT(<a href="qapplication.html#quit">quit</a>()) ); return a.<a href="qapplication.html#exec">exec</a>(); } diff --git a/doc/html/httpd-example.html b/doc/html/httpd-example.html index fbd007f35..1c9bb8c17 100644 --- a/doc/html/httpd-example.html +++ b/doc/html/httpd-example.html @@ -140,12 +140,12 @@ public: <a href="qlabel.html">TQLabel</a> *lb = new <a href="qlabel.html">TQLabel</a>( itext, this ); lb-><a href="qlabel.html#setAlignment">setAlignment</a>( AlignHCenter ); infoText = new <a href="qtextview.html">TQTextView</a>( this ); - <a href="qpushbutton.html">TQPushButton</a> *tquit = new <a href="qpushbutton.html">TQPushButton</a>( "tquit" , this ); + <a href="qpushbutton.html">TQPushButton</a> *quit = new <a href="qpushbutton.html">TQPushButton</a>( "quit" , this ); connect( httpd, SIGNAL(newConnect()), SLOT(newConnect()) ); connect( httpd, SIGNAL(endConnect()), SLOT(endConnect()) ); connect( httpd, SIGNAL(wroteToClient()), SLOT(wroteToClient()) ); -<a name="x724"></a> connect( tquit, SIGNAL(<a href="qbutton.html#pressed">pressed</a>()), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); +<a name="x724"></a> connect( quit, SIGNAL(<a href="qbutton.html#pressed">pressed</a>()), qApp, SLOT(<a href="qapplication.html#quit">quit</a>()) ); } ~HttpInfo() diff --git a/doc/html/i18n-example.html b/doc/html/i18n-example.html index eacdd9d88..b4f469e8f 100644 --- a/doc/html/i18n-example.html +++ b/doc/html/i18n-example.html @@ -112,7 +112,7 @@ private: <a href="qmainwindow.html#setCentralWidget">setCentralWidget</a>(central); <a href="qpopupmenu.html">TQPopupMenu</a>* file = new <a href="qpopupmenu.html">TQPopupMenu</a>(this); - file-><a href="qmenudata.html#insertItem">insertItem</a>( <a href="qobject.html#tr">tr</a>("E&xit"), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()), + file-><a href="qmenudata.html#insertItem">insertItem</a>( <a href="qobject.html#tr">tr</a>("E&xit"), qApp, SLOT(<a href="qapplication.html#quit">quit</a>()), <a name="x1921"></a> TQAccel::<a href="qaccel.html#stringToKey">stringToKey</a>(<a href="qobject.html#tr">tr</a>("Ctrl+Q")) ); <a href="qmainwindow.html#menuBar">menuBar</a>()->insertItem( <a href="qobject.html#tr">tr</a>("&File"), file ); @@ -293,7 +293,7 @@ int main( int argc, char** argv ) MyWidget* w = showLang((const char*)qm[i]); if( w == 0 ) exit( 0 ); - TQObject::<a href="qobject.html#connect">connect</a>(w, SIGNAL(closed()), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>())); + TQObject::<a href="qobject.html#connect">connect</a>(w, SIGNAL(closed()), qApp, SLOT(<a href="qapplication.html#quit">quit</a>())); <a name="x1953"></a> w-><a href="qwidget.html#setGeometry">setGeometry</a>(x,y,197,356); w-><a href="qwidget.html#show">show</a>(); if ( tight ) { diff --git a/doc/html/i18n.html b/doc/html/i18n.html index 51772b7f0..6f81c3348 100644 --- a/doc/html/i18n.html +++ b/doc/html/i18n.html @@ -263,7 +263,7 @@ your application, translators won't be able to override it. The correct idiom is <p> <pre> <a href="qpopupmenu.html">TQPopupMenu</a> *file = new <a href="qpopupmenu.html">TQPopupMenu</a>( this ); - file-><a href="qmenudata.html#insertItem">insertItem</a>( tr("&Quit"), this, SLOT(tquit()), + file-><a href="qmenudata.html#insertItem">insertItem</a>( tr("&Quit"), this, SLOT(quit()), TQKeySequence(tr("Ctrl+Q", "File|Quit")) ); </pre> diff --git a/doc/html/index b/doc/html/index index 4f57133a3..8cb7ae863 100644 --- a/doc/html/index +++ b/doc/html/index @@ -287,7 +287,7 @@ "QApplication::polish" qapplication.html#polish "QApplication::postEvent" qapplication.html#postEvent "QApplication::processEvents" qapplication.html#processEvents -"QApplication::tquit" qapplication.html#tquit +"QApplication::quit" qapplication.html#quit "QApplication::qwsDecoration" qapplication.html#qwsDecoration "QApplication::qwsEventFilter" qapplication.html#qwsEventFilter "QApplication::qwsSetCustomColors" qapplication.html#qwsSetCustomColors diff --git a/doc/html/layout-example.html b/doc/html/layout-example.html index 93a92b664..bff159fab 100644 --- a/doc/html/layout-example.html +++ b/doc/html/layout-example.html @@ -76,7 +76,7 @@ public: <a name="x540"></a> menubar-><a href="qmenubar.html#setSeparator">setSeparator</a>( TQMenuBar::InWindowsStyle ); <a href="qpopupmenu.html">TQPopupMenu</a>* popup; popup = new <a href="qpopupmenu.html">TQPopupMenu</a>( this ); - popup-><a href="qmenudata.html#insertItem">insertItem</a>( "&Quit", qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + popup-><a href="qmenudata.html#insertItem">insertItem</a>( "&Quit", qApp, SLOT(<a href="qapplication.html#quit">quit</a>()) ); menubar-><a href="qmenudata.html#insertItem">insertItem</a>( "&File", popup ); // ...and tell the layout about it. diff --git a/doc/html/linguist-manual-3.html b/doc/html/linguist-manual-3.html index 3dee0a922..1a9d36a52 100644 --- a/doc/html/linguist-manual-3.html +++ b/doc/html/linguist-manual-3.html @@ -39,7 +39,7 @@ body { background: #ffffff; color: black; } <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>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 tquit.</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> <!-- index Contexts!for Translation --><p>This appears at the left hand side of the main window by default. The first column, 'Done', identifies whether or not the translations for the context have been done. A tick indicates that all the translations have been done and are valid. A question mark indicates that one or more translations have not been done or have failed validation. The second column, 'Context' is the name of the context in which the translation phrases appear. The third column, 'Items' shows two numbers, the first is the number of translations that have been done, and the second is the number of phrases that are in the context; if the numbers are equal then all the translations have been done. Note that a greyed out tick indicates an obsolete translation, i.e. a phrase that was translated in a previous version of the application but which does not occur in the new version.</p> diff --git a/doc/html/linguist-manual-4.html b/doc/html/linguist-manual-4.html index 84814282d..b31088a13 100644 --- a/doc/html/linguist-manual-4.html +++ b/doc/html/linguist-manual-4.html @@ -102,7 +102,7 @@ body { background: #ffffff; color: black; } rbh = new TQRadioButton( tr("Enabled", "Hue frame"), this ); </pre> <!-- index Ctrl Key --><p>Ctrl key accelerators are also translatable:</p> -<pre> file-><a href="qmenudata.html#insertItem">insertItem</a>( <a href="qobject.html#tr">tr</a>("E&xit"), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()), +<pre> file-><a href="qmenudata.html#insertItem">insertItem</a>( <a href="qobject.html#tr">tr</a>("E&xit"), qApp, SLOT(<a href="qapplication.html#quit">quit</a>()), <a href="qobject.html#tr">tr</a>("Ctrl+Q", "Quit") ); </pre> <p>It is strongly recommended that the two argument form of <tt>tr()</tt> is used for Ctrl key accelerators. The second argument is the only clue the translator has as to the function performed by the accelerator.</p> @@ -336,7 +336,7 @@ TRANSLATIONS = tt2_fr.ts \ <pre> ArrowPad *ap = new ArrowPad( this, "arrow pad" ); </pre> <p>We also call <tt>MainWindow::tr()</tt> twice, once for the menu item and once for the accelerator.</p> -<!-- index Ctrl Key --><!-- index Alt Key --><pre> file-><a href="qmenudata.html#insertItem">insertItem</a>( <a href="qobject.html#tr">tr</a>("E&xit"), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()), +<!-- index Ctrl Key --><!-- index Alt Key --><pre> file-><a href="qmenudata.html#insertItem">insertItem</a>( <a href="qobject.html#tr">tr</a>("E&xit"), qApp, SLOT(<a href="qapplication.html#quit">quit</a>()), <a href="qobject.html#tr">tr</a>("Ctrl+Q", "Quit") ); </pre> <p>Note the use of <tt>tr()</tt> to support different keys in other languages. "Ctrl+Q" is a good choice for Quit in English, but a Dutch translator might want to use "Ctrl+A" (for Afsluiten) and a German translator "Strg+E" (for Beenden). When using <tt>tr()</tt> for Ctrl key accelerators, the two argument form should be used with the second argument describing the function that the accelerator performs.</p> @@ -452,7 +452,7 @@ TRANSLATIONS = tt3_pt.ts <pre> <a href="qwidget.html#setCaption">setCaption</a>( <a href="qobject.html#tr">tr</a>("Troll Print 1.0") ); </pre> <p>We must translate the window's caption.</p> -<pre> file-><a href="qmenudata.html#insertItem">insertItem</a>( <a href="qobject.html#tr">tr</a>("E&xit"), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()), +<pre> file-><a href="qmenudata.html#insertItem">insertItem</a>( <a href="qobject.html#tr">tr</a>("E&xit"), qApp, SLOT(<a href="qapplication.html#quit">quit</a>()), <a href="qobject.html#tr">tr</a>("Ctrl+Q", "Quit") ); <a href="qpopupmenu.html">TQPopupMenu</a> *help = new <a href="qpopupmenu.html">TQPopupMenu</a>( this ); help-><a href="qmenudata.html#insertItem">insertItem</a>( <a href="qobject.html#tr">tr</a>("&About"), this, SLOT(about()), Key_F1 ); @@ -489,7 +489,7 @@ TRANSLATIONS = tt3_pt.ts <!-- index lupdate --><!-- index tt3_pt.ts --><p>Now run <a href="linguist-manual-2.html#2">lupdate</a> and open <tt>tt3_pt.ts</tt> with <em>TQt Linguist</em>. You should now see two changes.</p> <p>First, the translation source file now contains <em>three</em> "Enabled", "Disabled" pairs. The first pair is marked "(obs.)" signifying that they are obsolete. This is because these texts appeared in <tt>tr()</tt> calls that have been replaced by new calls with two arguments. The second pair has "two-sided" as their comment, and the third pair has "colors" as their comment. The comments are shown in the <em>Source text and comments</em> area in <em>TQt Linguist</em>.</p> <p>Second, the translation text "Ativado" and "Desativado" have been automatically used as translations for the new "Enabled" and "Disabled" texts, again to minimize the translator's work. Of course in this case these are not correct for the second occurrence of each word, but they provide a good starting point.</p> -<p>Change the second "Ativado" into "Ativadas" and the second "Desativado" into "Desativadas", then save and tquit. Run <a href="linguist-manual-2.html#3">lrelease</a> to obtain an up-to-date binary <tt>tt3_pt.qm</tt> file, and run Troll Print (or rather Troll Imprimir).</p> +<p>Change the second "Ativado" into "Ativadas" and the second "Desativado" into "Desativadas", then save and quit. Run <a href="linguist-manual-2.html#3">lrelease</a> to obtain an up-to-date binary <tt>tt3_pt.qm</tt> file, and run Troll Print (or rather Troll Imprimir).</p> <p align="center"><img align="middle" src="tt3_10_pt_good.png" width="208" height="177"> </p> <blockquote><p align="center"><em>Tutorial 3 Screenshot, "Troll Imprimir 1.0", (Good) Portuguese version</em></p></blockquote> @@ -537,7 +537,7 @@ TRANSLATIONS = tt3_pt.ts <li><p>Two-sided - unmarked, i.e. untranslated.</p> </ul></ul><p>Notice that <a href="linguist-manual-2.html#2">lupdate</a> works hard behind the scenes to make revisions easier, and it's pretty smart with numbers.</p> <p>Go over the translations in <tt>MainWindow</tt> and mark these as "done". Translate "<b>TROLL PRINT</b>" as "<b>TROLL IMPRIMIR</b>". When you're translating "Two-sided", press the <em>Guess Again</em> button to translate "Two-sided", but change the "2" into "Dois".</p> -<p>Save and tquit, then run <a href="linguist-manual-2.html#3">lrelease</a>. The Portuguese version should look like this:</p> +<p>Save and quit, then run <a href="linguist-manual-2.html#3">lrelease</a>. The Portuguese version should look like this:</p> <p align="center"><img align="middle" src="tt3_11_pt.png" width="198" height="187"> </p> <blockquote><p align="center"><em>Tutorial 3 Screenshot, "Troll Imprimir 1.1", Portuguese version</em></p></blockquote> diff --git a/doc/html/mdi-example.html b/doc/html/mdi-example.html index 58f68c775..d816deb81 100644 --- a/doc/html/mdi-example.html +++ b/doc/html/mdi-example.html @@ -582,7 +582,7 @@ int main( int argc, char ** argv ) { a.<a href="qapplication.html#setMainWidget">setMainWidget</a>(mw); mw-><a href="qwidget.html#setCaption">setCaption</a>( "TQt Example - Multiple Documents Interface (MDI)" ); mw-><a href="qwidget.html#show">show</a>(); -<a name="x2097"></a><a name="x2096"></a> a.<a href="qobject.html#connect">connect</a>( &a, SIGNAL(<a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>()), &a, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); +<a name="x2097"></a><a name="x2096"></a> a.<a href="qobject.html#connect">connect</a>( &a, SIGNAL(<a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>()), &a, SLOT(<a href="qapplication.html#quit">quit</a>()) ); int res = a.<a href="qapplication.html#exec">exec</a>(); return res; } diff --git a/doc/html/menu-example.html b/doc/html/menu-example.html index 246e72ff9..d734a8531 100644 --- a/doc/html/menu-example.html +++ b/doc/html/menu-example.html @@ -242,7 +242,7 @@ private: file-><a href="qmenudata.html#insertSeparator">insertSeparator</a>(); file-><a href="qmenudata.html#insertItem">insertItem</a>( "&Print", print, CTRL+Key_P ); file-><a href="qmenudata.html#insertSeparator">insertSeparator</a>(); - file-><a href="qmenudata.html#insertItem">insertItem</a>( "E&xit", qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()), CTRL+Key_Q ); + file-><a href="qmenudata.html#insertItem">insertItem</a>( "E&xit", qApp, SLOT(<a href="qapplication.html#quit">quit</a>()), CTRL+Key_Q ); <a href="qpopupmenu.html">TQPopupMenu</a> *edit = new <a href="qpopupmenu.html">TQPopupMenu</a>( this ); <a href="qapplication.html#Q_CHECK_PTR">Q_CHECK_PTR</a>( edit ); diff --git a/doc/html/motif-customwidget-example.html b/doc/html/motif-customwidget-example.html index fe752f507..6e02b4f81 100644 --- a/doc/html/motif-customwidget-example.html +++ b/doc/html/motif-customwidget-example.html @@ -97,7 +97,7 @@ int main( int argc, char **argv ) : <a href="qmainwindow.html">TQMainWindow</a>( 0, "mainwindow" ) { <a href="qpopupmenu.html">TQPopupMenu</a> *filemenu = new <a href="qpopupmenu.html">TQPopupMenu</a>( this ); - filemenu-><a href="qmenudata.html#insertItem">insertItem</a>( <a href="qobject.html#tr">tr</a>("&Quit"), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + filemenu-><a href="qmenudata.html#insertItem">insertItem</a>( <a href="qobject.html#tr">tr</a>("&Quit"), qApp, SLOT(<a href="qapplication.html#quit">quit</a>()) ); <a href="qmainwindow.html#menuBar">menuBar</a>()->insertItem( <a href="qobject.html#tr">tr</a>("&File"), filemenu ); <a href="qmainwindow.html#statusBar">statusBar</a>()->message( <a href="qobject.html#tr">tr</a>("This is a TQMainWindow with an XmText widget.") ); diff --git a/doc/html/motif-dialog-example.html b/doc/html/motif-dialog-example.html index 6d4d6dac5..b30ffda91 100644 --- a/doc/html/motif-dialog-example.html +++ b/doc/html/motif-dialog-example.html @@ -106,7 +106,7 @@ static void qtDialogCallback( Widget, XtPointer client_data, XtPointer ) mw->showTQtDialog(); } -static void tquitCallback( Widget, XtPointer client_data, XtPointer ) +static void quitCallback( Widget, XtPointer client_data, XtPointer ) { MainWindow *mw = (MainWindow *) client_data; <a name="x2708"></a> mw-><a href="qwidget.html#close">close</a>(); @@ -140,7 +140,7 @@ static void tquitCallback( Widget, XtPointer client_data, XtPointer ) xmPushButtonGadgetClass, filemenu, XmNmnemonic, 'x', NULL ); - XtAddCallback( item, XmNactivateCallback, tquitCallback, this ); + XtAddCallback( item, XmNactivateCallback, quitCallback, this ); XmString str = XmStringCreateLocalized( "File" ); item = XtVaCreateManagedWidget( "File", diff --git a/doc/html/motif-walkthrough-10.html b/doc/html/motif-walkthrough-10.html index 0d09bc569..5baecdf87 100644 --- a/doc/html/motif-walkthrough-10.html +++ b/doc/html/motif-walkthrough-10.html @@ -35,7 +35,7 @@ body { background: #ffffff; color: black; } [ <a href="motif-walkthrough-9.html">Previous: Replacing the Print Dialog</a> ] [ <a href="motif-walkthrough.html">Home</a> ] -<p> We have not tquite finished with the migration to TQt, even though our +<p> We have not quite finished with the migration to TQt, even though our project does not use <a href="motif-extension.html#Motif">Motif</a> any more. TQt provides many useful features that we can begin using immediately. Some of the most interesting ones are presented below as a guide for where to start extending your diff --git a/doc/html/motif-walkthrough-6.html b/doc/html/motif-walkthrough-6.html index 802f205d5..ec9ce6a47 100644 --- a/doc/html/motif-walkthrough-6.html +++ b/doc/html/motif-walkthrough-6.html @@ -69,7 +69,7 @@ existing callback functions found in <tt>todo.cpp</tt> and <tt>actions.cpp</tt>. <tr bgcolor="#f0f0f0"> <td valign="top">Save <td valign="top"><tt>MainWindow::fileSave()</tt> <td valign="top">calls the <tt>SaveIt()</tt> callback <tr bgcolor="#d0d0d0"> <td valign="top">Save As <td valign="top"><tt>MainWindow::fileSaveAs()</tt> <td valign="top">calls the <tt>Save()</tt> callback <tr bgcolor="#f0f0f0"> <td valign="top">Print <td valign="top"><tt>MainWindow::filePrint()</tt> <td valign="top">calls the <tt>ShowPrintDialog()</tt> callback -<tr bgcolor="#d0d0d0"> <td valign="top">Exit <td valign="top"><tt>MainWindow::fileExit()</tt> <td valign="top">calls <a href="qapplication.html#tquit">TQApplication::tquit</a>() +<tr bgcolor="#d0d0d0"> <td valign="top">Exit <td valign="top"><tt>MainWindow::fileExit()</tt> <td valign="top">calls <a href="qapplication.html#quit">TQApplication::quit</a>() <tr bgcolor="#a2c511"> <th valign="top" colspan="3" rowspan="1"> Selected menu <tr bgcolor="#f0f0f0"> <td valign="top">Properties <td valign="top"><tt>MainWindow::selProperties()</tt> <td valign="top">calls the <tt>EditPage()</tt> callback <tr bgcolor="#d0d0d0"> <td valign="top">New <td valign="top"><tt>MainWindow::selNewPage()</tt> <td valign="top">calls the <tt>NewPage()</tt> callback diff --git a/doc/html/movies-example.html b/doc/html/movies-example.html index d2b292bcf..d607e6ac2 100644 --- a/doc/html/movies-example.html +++ b/doc/html/movies-example.html @@ -266,7 +266,7 @@ public: public slots: void startMovie(const <a href="qstring.html">TQString</a>& filename); // TQDialog's method - normally closes the file dialog. - // We want it left open, and we want Cancel to tquit everything. + // We want it left open, and we want Cancel to quit everything. void done( int r ); }; @@ -292,7 +292,7 @@ void <a name="f259"></a>MovieStarter::startMovie(const <a href="qstring.html">TQ <a name="x495"></a>void MovieStarter::<a href="qdialog.html#done">done</a>( int r ) { if (r != Accepted) - qApp-><a href="qapplication.html#tquit">tquit</a>(); // end on Cancel + qApp-><a href="qapplication.html#quit">quit</a>(); // end on Cancel <a href="qdialog.html#setResult">setResult</a>( r ); // And don't hide. @@ -317,7 +317,7 @@ int main(int argc, char **argv) (void)new MovieScreen(argv[arg], TQMovie(argv[arg]), 0, 0, TQt::WDestructiveClose); } - TQObject::<a href="qobject.html#connect">connect</a>(qApp, SIGNAL(<a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>()), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>())); + TQObject::<a href="qobject.html#connect">connect</a>(qApp, SIGNAL(<a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>()), qApp, SLOT(<a href="qapplication.html#quit">quit</a>())); } else { // "GUI" mode - open a chooser for movies // diff --git a/doc/html/network.html b/doc/html/network.html index 1ee0b25d4..833a5693e 100644 --- a/doc/html/network.html +++ b/doc/html/network.html @@ -75,7 +75,7 @@ This could be, for example, a protocol which can read pictures from a digital camera using a serial connection. <p> <h2> Working Network Protocol independently with <a href="qurloperator.html">TQUrlOperator</a> and <a href="qnetworkoperation.html">TQNetworkOperation</a> </h2> -<a name="2"></a><p> It is tquite easy to just use existing network protocol implementations +<a name="2"></a><p> It is quite easy to just use existing network protocol implementations and operate on URLs. For example, downloading a file from an FTP server to the local filesystem can be done with following code: <p> <pre> diff --git a/doc/html/networkprotocol-example.html b/doc/html/networkprotocol-example.html index ef15570d5..97473a376 100644 --- a/doc/html/networkprotocol-example.html +++ b/doc/html/networkprotocol-example.html @@ -199,7 +199,7 @@ void <a name="f289"></a>Nntp::close() { // close the command socket if ( commandSocket-><a href="qiodevice.html#isOpen">isOpen</a>() ) { - commandSocket-><a href="qsocket.html#writeBlock">writeBlock</a>( "tquit\r\n", strlen( "tquit\r\n" ) ); + commandSocket-><a href="qsocket.html#writeBlock">writeBlock</a>( "quit\r\n", strlen( "quit\r\n" ) ); <a name="x679"></a> commandSocket-><a href="qsocket.html#close">close</a>(); } } diff --git a/doc/html/picture-example.html b/doc/html/picture-example.html index 8523e1881..b851d4cb2 100644 --- a/doc/html/picture-example.html +++ b/doc/html/picture-example.html @@ -132,7 +132,7 @@ void PictureDisplay::<a href="qwidget.html#paintEvent">paintEvent</a>( <a href=" pict-><a href="qpicture.html#load">load</a>( name ); <a href="qwidget.html#update">update</a>(); break; - case 'q': // tquit + case 'q': // quit <a name="x106"></a> TQApplication::<a href="qapplication.html#exit">exit</a>(); break; } diff --git a/doc/html/process-example.html b/doc/html/process-example.html index 839f185b3..565eab304 100644 --- a/doc/html/process-example.html +++ b/doc/html/process-example.html @@ -74,16 +74,16 @@ public slots: private: <a href="qprocess.html">TQProcess</a> *proc; <a href="qtextview.html">TQTextView</a> *output; - <a href="qpushbutton.html">TQPushButton</a> *tquitButton; + <a href="qpushbutton.html">TQPushButton</a> *quitButton; }; <a name="f204"></a>UicManager::UicManager() { // Layout output = new <a href="qtextview.html">TQTextView</a>( this ); - tquitButton = new <a href="qpushbutton.html">TQPushButton</a>( <a href="qobject.html#tr">tr</a>("Quit"), this ); - <a href="qobject.html#connect">connect</a>( tquitButton, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), - qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + quitButton = new <a href="qpushbutton.html">TQPushButton</a>( <a href="qobject.html#tr">tr</a>("Quit"), this ); + <a href="qobject.html#connect">connect</a>( quitButton, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), + qApp, SLOT(<a href="qapplication.html#quit">quit</a>()) ); <a href="qwidget.html#resize">resize</a>( 500, 500 ); // TQProcess related code diff --git a/doc/html/progress-example.html b/doc/html/progress-example.html index 83a14b80b..e20a0aba9 100644 --- a/doc/html/progress-example.html +++ b/doc/html/progress-example.html @@ -192,7 +192,7 @@ public: file-><a href="qmenudata.html#insertItem">insertItem</a>( drawItemText(i), i ); <a name="x67"></a> connect( menubar, SIGNAL(<a href="qmenubar.html#activated">activated</a>(int)), this, SLOT(doMenuItem(int)) ); <a name="x69"></a> file-><a href="qmenudata.html#insertSeparator">insertSeparator</a>(); - file-><a href="qmenudata.html#insertItem">insertItem</a>( "Quit", qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + file-><a href="qmenudata.html#insertItem">insertItem</a>( "Quit", qApp, SLOT(<a href="qapplication.html#quit">quit</a>()) ); options = new <a href="qpopupmenu.html">TQPopupMenu</a>(); <a href="qapplication.html#Q_CHECK_PTR">Q_CHECK_PTR</a>( options ); diff --git a/doc/html/qaccel.html b/doc/html/qaccel.html index b7c1dd7f6..e7e725a89 100644 --- a/doc/html/qaccel.html +++ b/doc/html/qaccel.html @@ -180,7 +180,7 @@ Removes all accelerator items. </h3> Connects the accelerator item <em>id</em> to the slot <em>member</em> of <em>receiver</em>. <p> <pre> - a->connectItem( 201, mainView, SLOT(tquit()) ); + a->connectItem( 201, mainView, SLOT(quit()) ); </pre> <p> Of course, you can also send a signal as <em>member</em>. @@ -221,8 +221,8 @@ negative identifier less than -1. <p> <pre> TQAccel *a = new TQAccel( myWindow ); // create accels for myWindow a-><a href="#insertItem">insertItem</a>( CTRL + Key_P, 200 ); // Ctrl+P, e.g. to print document - a-><a href="#insertItem">insertItem</a>( ALT + Key_X, 201 ); // Alt+X, e.g. to tquit - a-><a href="#insertItem">insertItem</a>( UNICODE_ACCEL + 'q', 202 ); // Unicode 'q', e.g. to tquit + a-><a href="#insertItem">insertItem</a>( ALT + Key_X, 201 ); // Alt+X, e.g. to quit + a-><a href="#insertItem">insertItem</a>( UNICODE_ACCEL + 'q', 202 ); // Unicode 'q', e.g. to quit a-><a href="#insertItem">insertItem</a>( <a href="qt.html#Key-enum">Key_D</a> ); // gets a unique negative id < -1 a-><a href="#insertItem">insertItem</a>( CTRL + SHIFT + Key_P ); // gets a unique negative id < -1 </pre> diff --git a/doc/html/qaction-application-example.html b/doc/html/qaction-application-example.html index c166a8d9a..2709e8633 100644 --- a/doc/html/qaction-application-example.html +++ b/doc/html/qaction-application-example.html @@ -188,7 +188,7 @@ private: SLOT( <a href="qwidget.html#close">close</a>() ) ); fileQuitAction = new <a href="qaction.html">TQAction</a>( "Quit", "&Quit", CTRL+Key_Q, this, - "tquit" ); + "quit" ); <a name="x1127"></a> <a href="qobject.html#connect">connect</a>( fileQuitAction, SIGNAL( <a href="qaction.html#activated">activated</a>() ) , qApp, SLOT( <a href="qapplication.html#closeAllWindows">closeAllWindows</a>() ) ); @@ -421,7 +421,7 @@ int main( int argc, char ** argv ) { ApplicationWindow * mw = new ApplicationWindow(); mw-><a href="qwidget.html#setCaption">setCaption</a>( "Document 1" ); <a name="x1178"></a> mw-><a href="qwidget.html#show">show</a>(); -<a name="x1179"></a> a.<a href="qobject.html#connect">connect</a>( &a, SIGNAL(<a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>()), &a, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); +<a name="x1179"></a> a.<a href="qobject.html#connect">connect</a>( &a, SIGNAL(<a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>()), &a, SLOT(<a href="qapplication.html#quit">quit</a>()) ); return a.<a href="qapplication.html#exec">exec</a>(); } </pre> diff --git a/doc/html/qapplication-h.html b/doc/html/qapplication-h.html index a822ad049..7b26e42f3 100644 --- a/doc/html/qapplication-h.html +++ b/doc/html/qapplication-h.html @@ -329,7 +329,7 @@ signals: void guiThreadAwake(); public slots: - void tquit(); + void quit(); void closeAllWindows(); void aboutTQt(); @@ -373,8 +373,8 @@ private: int app_argc; char **app_argv; - bool tquit_now; - int tquit_code; + bool quit_now; + int quit_code; static TQStyle *app_style; static int app_cspec; #ifndef QT_NO_PALETTE diff --git a/doc/html/qapplication-members.html b/doc/html/qapplication-members.html index 1b2eadbdc..fb47490bc 100644 --- a/doc/html/qapplication-members.html +++ b/doc/html/qapplication-members.html @@ -123,7 +123,7 @@ body { background: #ffffff; color: black; } <li><a href="qapplication.html#processOneEvent">processOneEvent</a>() <li><a href="qobject.html#property">property</a>() <li><a href="qobject.html#queryList">queryList</a>() -<li><a href="qapplication.html#tquit">tquit</a>() +<li><a href="qapplication.html#quit">quit</a>() <li><a href="qapplication.html#qwsDecoration">qwsDecoration</a>() <li><a href="qapplication.html#qwsEventFilter">qwsEventFilter</a>() <li><a href="qapplication.html#qwsSetCustomColors">qwsSetCustomColors</a>() diff --git a/doc/html/qapplication.html b/doc/html/qapplication.html index cfdfa0980..353c3ee37 100644 --- a/doc/html/qapplication.html +++ b/doc/html/qapplication.html @@ -92,7 +92,7 @@ flow and main settings. </ul> <h2>Public Slots</h2> <ul> -<li class=fn>void <a href="#tquit"><b>tquit</b></a> ()</li> +<li class=fn>void <a href="#quit"><b>quit</b></a> ()</li> <li class=fn>void <a href="#closeAllWindows"><b>closeAllWindows</b></a> ()</li> <li class=fn>void <a href="#aboutTQt"><b>aboutTQt</b></a> ()</li> </ul> @@ -270,7 +270,7 @@ any overrides after.) <a href="#enter_loop">enter_loop</a>(), <a href="#exit_loop">exit_loop</a>(), <a href="#exit">exit</a>(), -<a href="#tquit">tquit</a>(). +<a href="#quit">quit</a>(). <a href="#sendEvent">sendEvent</a>(), <a href="#postEvent">postEvent</a>(), <a href="#sendPostedEvents">sendPostedEvents</a>(), @@ -530,14 +530,14 @@ See the examples/menu/menu.cpp example. <h3 class=fn>void <a name="aboutToQuit"></a>TQApplication::aboutToQuit ()<tt> [signal]</tt> </h3> -<p> This signal is emitted when the application is about to tquit the +<p> This signal is emitted when the application is about to quit the main event loop, e.g. when the event loop level drops to zero. -This may happen either after a call to <a href="#tquit">tquit</a>() from inside the +This may happen either after a call to <a href="#quit">quit</a>() from inside the application or when the users shuts down the entire desktop session. <p> The signal is particularly useful if your application has to do some last-second cleanup. Note that no user interaction is possible in this state. -<p> <p>See also <a href="#tquit">tquit</a>(). +<p> <p>See also <a href="#quit">quit</a>(). <h3 class=fn><a href="qwidget.html">TQWidget</a> * <a name="activeModalWidget"></a>TQApplication::activeModalWidget ()<tt> [static]</tt> </h3> @@ -698,13 +698,13 @@ entry in the file menu as shown in the following code example: <a href="qpopupmenu.html">TQPopupMenu</a>* file = new <a href="qpopupmenu.html">TQPopupMenu</a>( this ); file-><a href="qmenudata.html#insertItem">insertItem</a>( "&Quit", qApp, SLOT(<a href="#closeAllWindows">closeAllWindows</a>()), CTRL+Key_Q ); - // when the last window is closed, the application should tquit - <a href="qobject.html#connect">connect</a>( qApp, SIGNAL( <a href="#lastWindowClosed">lastWindowClosed</a>() ), qApp, SLOT( <a href="#tquit">tquit</a>() ) ); + // when the last window is closed, the application should quit + <a href="qobject.html#connect">connect</a>( qApp, SIGNAL( <a href="#lastWindowClosed">lastWindowClosed</a>() ), qApp, SLOT( <a href="#quit">quit</a>() ) ); </pre> <p> The windows are closed in random order, until one window does not accept the close event. -<p> <p>See also <a href="qwidget.html#close">TQWidget::close</a>(), <a href="qwidget.html#closeEvent">TQWidget::closeEvent</a>(), <a href="#lastWindowClosed">lastWindowClosed</a>(), <a href="#tquit">tquit</a>(), <a href="#topLevelWidgets">topLevelWidgets</a>(), and <a href="qwidget.html#isTopLevel-prop">TQWidget::isTopLevel</a>. +<p> <p>See also <a href="qwidget.html#close">TQWidget::close</a>(), <a href="qwidget.html#closeEvent">TQWidget::closeEvent</a>(), <a href="#lastWindowClosed">lastWindowClosed</a>(), <a href="#quit">quit</a>(), <a href="#topLevelWidgets">topLevelWidgets</a>(), and <a href="qwidget.html#isTopLevel-prop">TQWidget::isTopLevel</a>. <p> <p>Examples: <a href="qaction-application-example.html#x1127">action/application.cpp</a>, <a href="simple-application-example.html#x1544">application/application.cpp</a>, <a href="helpviewer-example.html#x980">helpviewer/helpwindow.cpp</a>, <a href="mdi-example.html#x2020">mdi/application.cpp</a>, and <a href="qwerty-example.html#x358">qwerty/qwerty.cpp</a>. @@ -803,7 +803,7 @@ it before you create the TQApplication object. </h3> Enters the main event loop and waits until <a href="#exit">exit</a>() is called or the main widget is destroyed, and returns the value that was set to -exit() (which is 0 if exit() is called via <a href="#tquit">tquit</a>()). +exit() (which is 0 if exit() is called via <a href="#quit">quit</a>()). <p> It is necessary to call this function to start event handling. The main event loop receives events from the window system and dispatches these to the application widgets. @@ -815,7 +815,7 @@ exec() to start a local event loop. special function whenever there are no pending events, use a <a href="qtimer.html">TQTimer</a> with 0 timeout. More advanced idle processing schemes can be achieved using <a href="#processEvents">processEvents</a>(). -<p> <p>See also <a href="#tquit">tquit</a>(), <a href="#exit">exit</a>(), <a href="#processEvents">processEvents</a>(), and <a href="#setMainWidget">setMainWidget</a>(). +<p> <p>See also <a href="#quit">quit</a>(), <a href="#exit">exit</a>(), <a href="#processEvents">processEvents</a>(), and <a href="#setMainWidget">setMainWidget</a>(). <p>Examples: <a href="helpsystem-example.html#x2700">helpsystem/main.cpp</a>, <a href="qdialog.html#x2132">life/main.cpp</a>, <a href="archivesearch-example.html#x486">network/archivesearch/main.cpp</a>, <a href="ftpclient-example.html#x777">network/ftpclient/main.cpp</a>, <a href="qaxserver-example-opengl.html#x2731">opengl/main.cpp</a>, <a href="tutorial1-01.html#x2283">t1/main.cpp</a>, and <a href="tutorial1-04.html#x2303">t4/main.cpp</a>. <h3 class=fn>void <a name="exit"></a>TQApplication::exit ( int retcode = 0 )<tt> [static]</tt> @@ -829,7 +829,7 @@ value indicates an error. <p> Note that unlike the C library function of the same name, this function <em>does</em> return to the caller -- it is event processing that stops. -<p> <p>See also <a href="#tquit">tquit</a>() and <a href="#exec">exec</a>(). +<p> <p>See also <a href="#quit">quit</a>() and <a href="#exec">exec</a>(). <p>Examples: <a href="canvas-chart-example.html#x2875">chart/chartform.cpp</a>, <a href="extension-dialog-example.html#x2865">extension/mainform.ui.h</a>, and <a href="picture-example.html#x106">picture/picture.cpp</a>. <h3 class=fn>void <a name="exit_loop"></a>TQApplication::exit_loop () @@ -945,7 +945,7 @@ Returns TRUE if <em>effect</em> is enabled; otherwise returns FALSE. <p> This signal is emitted when the user has closed the last top level window. <p> The signal is very useful when your application has many top level -widgets but no main widget. You can then connect it to the <a href="#tquit">tquit</a>() +widgets but no main widget. You can then connect it to the <a href="#quit">quit</a>() slot. <p> For convenience, this signal is <em>not</em> emitted for transient top level widgets such as popup menus and dialogs. @@ -1116,17 +1116,17 @@ event processing must be grafted onto existing program loops. problems. <p> <p>See also <a href="#processEvents">processEvents</a>(), <a href="#exec">exec</a>(), and <a href="qtimer.html">TQTimer</a>. -<h3 class=fn>void <a name="tquit"></a>TQApplication::tquit ()<tt> [slot]</tt> +<h3 class=fn>void <a name="quit"></a>TQApplication::quit ()<tt> [slot]</tt> </h3> Tells the application to exit with return code 0 (success). Equivalent to calling <a href="#exit">TQApplication::exit</a>( 0 ). -<p> It's common to connect the <a href="#lastWindowClosed">lastWindowClosed</a>() signal to <a href="#tquit">tquit</a>(), and +<p> It's common to connect the <a href="#lastWindowClosed">lastWindowClosed</a>() signal to <a href="#quit">quit</a>(), and you also often connect e.g. <a href="qbutton.html#clicked">TQButton::clicked</a>() or signals in <a href="qaction.html">TQAction</a>, <a href="qpopupmenu.html">TQPopupMenu</a> or <a href="qmenubar.html">TQMenuBar</a> to it. <p> Example: <pre> - <a href="qpushbutton.html">TQPushButton</a> *tquitButton = new <a href="qpushbutton.html">TQPushButton</a>( "Quit" ); - <a href="qobject.html#connect">connect</a>( tquitButton, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="#tquit">tquit</a>()) ); + <a href="qpushbutton.html">TQPushButton</a> *quitButton = new <a href="qpushbutton.html">TQPushButton</a>( "Quit" ); + <a href="qobject.html#connect">connect</a>( quitButton, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="#quit">quit</a>()) ); </pre> <p> <p>See also <a href="#exit">exit</a>(), <a href="#aboutToQuit">aboutToQuit</a>(), <a href="#lastWindowClosed">lastWindowClosed</a>(), and <a href="qaction.html">TQAction</a>. @@ -1468,12 +1468,12 @@ TQApplication does <em>not</em> take ownership of the <em>mainWidget</em>, so if you create your main widget on the heap you must delete it yourself. <p> You need not have a main widget; connecting <a href="#lastWindowClosed">lastWindowClosed</a>() to -<a href="#tquit">tquit</a>() is an alternative. +<a href="#quit">quit</a>() is an alternative. <p> For X11, this function also resizes and moves the main widget according to the <em>-geometry</em> command-line option, so you should set the default geometry (using <a href="qwidget.html#setGeometry">TQWidget::setGeometry</a>()) before calling <a href="#setMainWidget">setMainWidget</a>(). -<p> <p>See also <a href="#mainWidget">mainWidget</a>(), <a href="#exec">exec</a>(), and <a href="#tquit">tquit</a>(). +<p> <p>See also <a href="#mainWidget">mainWidget</a>(), <a href="#exec">exec</a>(), and <a href="#quit">quit</a>(). <p>Examples: <a href="tutorial2-04.html#x2560">chart/main.cpp</a>, <a href="helpsystem-example.html#x2701">helpsystem/main.cpp</a>, <a href="qdialog.html#x2133">life/main.cpp</a>, <a href="ftpclient-example.html#x779">network/ftpclient/main.cpp</a>, <a href="qaxserver-example-opengl.html#x2733">opengl/main.cpp</a>, <a href="tutorial1-01.html#x2284">t1/main.cpp</a>, and <a href="tutorial1-04.html#x2305">t4/main.cpp</a>. <h3 class=fn>void <a name="setOverrideCursor"></a>TQApplication::setOverrideCursor ( const <a href="qcursor.html">TQCursor</a> & cursor, bool replace = FALSE )<tt> [static]</tt> diff --git a/doc/html/qcdestyle.html b/doc/html/qcdestyle.html index 66fddb1b7..936ff8dd4 100644 --- a/doc/html/qcdestyle.html +++ b/doc/html/qcdestyle.html @@ -50,7 +50,7 @@ The TQCDEStyle class provides a CDE look and feel. versions of the Common Desktop Environment (CDE). The main differences are thinner frames and more modern radio buttons and checkboxes. Together with a dark background and a bright -text/foreground color, the style looks tquite attractive (at least +text/foreground color, the style looks quite attractive (at least for Motif fans). <p> Note that the functions provided by TQCDEStyle are reimplementations of <a href="qstyle.html">TQStyle</a> functions; see TQStyle for their diff --git a/doc/html/qcloseevent.html b/doc/html/qcloseevent.html index 9849d37a0..1674e60b0 100644 --- a/doc/html/qcloseevent.html +++ b/doc/html/qcloseevent.html @@ -81,7 +81,7 @@ independent top-level windows in a multi-window application. agreed to close the widget; call <a href="#accept">accept</a>() to agree to close the widget and call <a href="#ignore">ignore</a>() if the receiver of this event does not want the widget to be closed. -<p> <p>See also <a href="qwidget.html#close">TQWidget::close</a>(), <a href="qwidget.html#hide">TQWidget::hide</a>(), <a href="qobject.html#destroyed">TQObject::destroyed</a>(), <a href="qapplication.html#setMainWidget">TQApplication::setMainWidget</a>(), <a href="qapplication.html#lastWindowClosed">TQApplication::lastWindowClosed</a>(), <a href="qapplication.html#exec">TQApplication::exec</a>(), <a href="qapplication.html#tquit">TQApplication::tquit</a>(), and <a href="events.html">Event Classes</a>. +<p> <p>See also <a href="qwidget.html#close">TQWidget::close</a>(), <a href="qwidget.html#hide">TQWidget::hide</a>(), <a href="qobject.html#destroyed">TQObject::destroyed</a>(), <a href="qapplication.html#setMainWidget">TQApplication::setMainWidget</a>(), <a href="qapplication.html#lastWindowClosed">TQApplication::lastWindowClosed</a>(), <a href="qapplication.html#exec">TQApplication::exec</a>(), <a href="qapplication.html#quit">TQApplication::quit</a>(), and <a href="events.html">Event Classes</a>. <hr><h2>Member Function Documentation</h2> <h3 class=fn><a name="TQCloseEvent"></a>TQCloseEvent::TQCloseEvent () diff --git a/doc/html/qcolorgroup.html b/doc/html/qcolorgroup.html index 07cf10e33..76b466c9d 100644 --- a/doc/html/qcolorgroup.html +++ b/doc/html/qcolorgroup.html @@ -156,7 +156,7 @@ By default, the link color is <tt>TQt::blue</tt>. By default, the linkvisited color is <tt>TQt::magenta</tt>. <li><tt>TQColorGroup::NColorRoles</tt> - Internal. </ul><p> Note that text colors can be used for things other than just -words; text colors are <em>usually</em> used for text, but it's tquite +words; text colors are <em>usually</em> used for text, but it's quite common to use the text color roles for lines, icons, etc. <p> This image shows most of the color roles in use: <center><img src="palette.png" alt="Color Roles"></center> diff --git a/doc/html/qdatapump.html b/doc/html/qdatapump.html index 15213161e..d2fa45d49 100644 --- a/doc/html/qdatapump.html +++ b/doc/html/qdatapump.html @@ -52,7 +52,7 @@ sink. One very useful way to do this is interleaved with other event processing. TQDataPump provides this - create a pipe between a source and a sink, and data will be moved during subsequent event processing. <p> Note that each source can only provide data to one sink and each sink -can only receive data from one source (although it is tquite possible +can only receive data from one source (although it is quite possible to write a multiplexing sink that is multiple sources). <hr><h2>Member Function Documentation</h2> diff --git a/doc/html/qdialog.html b/doc/html/qdialog.html index c23d826e0..01945715a 100644 --- a/doc/html/qdialog.html +++ b/doc/html/qdialog.html @@ -242,7 +242,7 @@ and exec() to return <em>r</em>. main widget, the application terminates. If the dialog is the last window closed, the <a href="qapplication.html#lastWindowClosed">TQApplication::lastWindowClosed</a>() signal is emitted. -<p> <p>See also <a href="#accept">accept</a>(), <a href="#reject">reject</a>(), <a href="qapplication.html#mainWidget">TQApplication::mainWidget</a>(), and <a href="qapplication.html#tquit">TQApplication::tquit</a>(). +<p> <p>See also <a href="#accept">accept</a>(), <a href="#reject">reject</a>(), <a href="qapplication.html#mainWidget">TQApplication::mainWidget</a>(), and <a href="qapplication.html#quit">TQApplication::quit</a>(). <h3 class=fn>int <a name="exec"></a>TQDialog::exec ()<tt> [slot]</tt> </h3> diff --git a/doc/html/qevent-h.html b/doc/html/qevent-h.html index af9526587..b700cf3da 100644 --- a/doc/html/qevent-h.html +++ b/doc/html/qevent-h.html @@ -119,7 +119,7 @@ public: Show = 17, // widget is shown Hide = 18, // widget is hidden Close = 19, // request to close widget - Quit = 20, // request to tquit application + Quit = 20, // request to quit application Reparent = 21, // widget has been reparented ShowMinimized = 22, // widget is shown minimized ShowNormal = 23, // widget is shown normal diff --git a/doc/html/qeventloop.html b/doc/html/qeventloop.html index 46e06c13e..1204d0ca9 100644 --- a/doc/html/qeventloop.html +++ b/doc/html/qeventloop.html @@ -165,7 +165,7 @@ exec() to start a local event loop. special function whenever there are no pending events, use a <a href="qtimer.html">TQTimer</a> with 0 timeout. More advanced idle processing schemes can be achieved using <a href="#processEvents">processEvents</a>(). -<p> <p>See also <a href="qapplication.html#tquit">TQApplication::tquit</a>(), <a href="#exit">exit</a>(), and <a href="#processEvents">processEvents</a>(). +<p> <p>See also <a href="qapplication.html#quit">TQApplication::quit</a>(), <a href="#exit">exit</a>(), and <a href="#processEvents">processEvents</a>(). <h3 class=fn>void <a name="exit"></a>TQEventLoop::exit ( int retcode = 0 )<tt> [virtual]</tt> </h3> @@ -177,7 +177,7 @@ value indicates an error. <p> Note that unlike the C library function of the same name, this function <em>does</em> return to the caller -- it is event processing that stops. -<p> <p>See also <a href="qapplication.html#tquit">TQApplication::tquit</a>() and <a href="#exec">exec</a>(). +<p> <p>See also <a href="qapplication.html#quit">TQApplication::quit</a>() and <a href="#exec">exec</a>(). <h3 class=fn>void <a name="exitLoop"></a>TQEventLoop::exitLoop ()<tt> [virtual]</tt> </h3> diff --git a/doc/html/qfont.html b/doc/html/qfont.html index 1978f6d65..c410d5c95 100644 --- a/doc/html/qfont.html +++ b/doc/html/qfont.html @@ -312,7 +312,7 @@ state/India. <li><tt>TQFont::Sinhala</tt> - is used for Sri Lanka's majority language Sinhala and is also employed to write Pali, Sanskrit, and Tamil. <li><tt>TQFont::Thai</tt> - is used to write Thai and other Southeast Asian languages. -<li><tt>TQFont::Lao</tt> - is a language and script tquite similar to Thai. +<li><tt>TQFont::Lao</tt> - is a language and script quite similar to Thai. <li><tt>TQFont::Tibetan</tt> - is the script used to write Tibetan in several countries like Tibet, the bordering Indian regions and Nepal. It is also used in the Buddist philosophy and diff --git a/doc/html/qglcontext.html b/doc/html/qglcontext.html index aa1ec72e5..8f0ab6bf8 100644 --- a/doc/html/qglcontext.html +++ b/doc/html/qglcontext.html @@ -135,7 +135,7 @@ visual. On other platforms it may work differently. <p> <strong>Mac only</strong>: This virtual function tries to find a 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 tquite +<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. <p> <p>See also <a href="#chooseContext">chooseContext</a>(). @@ -155,7 +155,7 @@ Windows-specific types in our header files. <strong>X11 only</strong>: This virtual function tries to find a 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 tquite +<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. <p> <p>See also <a href="#chooseContext">chooseContext</a>(). diff --git a/doc/html/qhebrewcodec.html b/doc/html/qhebrewcodec.html index 2c5b94982..f3b9b7558 100644 --- a/doc/html/qhebrewcodec.html +++ b/doc/html/qhebrewcodec.html @@ -69,7 +69,7 @@ a newline character ('\n'). Note that these newline characters change the reordering behaviour of the algorithm, since the bidi reordering only takes place within one line of text, whereas line breaks are determined in visual order. -<p> Visually ordered Hebrew is still used tquite often in some places, +<p> Visually ordered Hebrew is still used quite often in some places, mainly in email communication (since most email programs still don't understand logically ordered Hebrew) and on web pages. The use on web pages is rapidly decreasing, due to the availability of diff --git a/doc/html/qlistbox.html b/doc/html/qlistbox.html index c19964336..7b4ff52fd 100644 --- a/doc/html/qlistbox.html +++ b/doc/html/qlistbox.html @@ -252,7 +252,7 @@ can get keyboard focus by tabbing, clicking and through the use of the mouse wheel. <p> New items can be inserted using <a href="#insertItem">insertItem</a>(), <a href="#insertStrList">insertStrList</a>() or <a href="#insertStringList">insertStringList</a>(). <a href="#inSort">inSort</a>() is obsolete because this method is -tquite inefficient. It's preferable to insert the items normally +quite inefficient. It's preferable to insert the items normally and call <a href="#sort">sort</a>() afterwards, or to insert a sorted <a href="qstringlist.html">TQStringList</a>(). <p> By default, vertical and horizontal scroll bars are added and removed as necessary. <a href="qscrollview.html#setHScrollBarMode">setHScrollBarMode</a>() and <a href="qscrollview.html#setVScrollBarMode">setVScrollBarMode</a>() @@ -532,7 +532,7 @@ item. The argument is a pointer to the new current item. <h3 class=fn>int <a name="inSort"></a>TQListBox::inSort ( const <a href="qlistboxitem.html">TQListBoxItem</a> * lbi ) </h3> <b>This function is obsolete.</b> It is provided to keep old source working. We strongly advise against using it in new code. -<p> Using this method is tquite inefficient. We suggest to use <a href="#insertItem">insertItem</a>() +<p> Using this method is quite inefficient. We suggest to use <a href="#insertItem">insertItem</a>() for inserting and <a href="#sort">sort</a>() afterwards. <p> Inserts <em>lbi</em> at its sorted position in the list box and returns the position. @@ -545,7 +545,7 @@ lexicographically less than any string. </h3> <b>This function is obsolete.</b> It is provided to keep old source working. We strongly advise against using it in new code. <p> This is an overloaded member function, provided for convenience. It behaves essentially like the above function. -<p> Using this method is tquite inefficient. We suggest to use <a href="#insertItem">insertItem</a>() +<p> Using this method is quite inefficient. We suggest to use <a href="#insertItem">insertItem</a>() for inserting and <a href="#sort">sort</a>() afterwards. <p> Inserts a new item of <em>text</em> at its sorted position in the list box and returns the position. diff --git a/doc/html/qmag-example.html b/doc/html/qmag-example.html index 978475e75..2a6e5b034 100644 --- a/doc/html/qmag-example.html +++ b/doc/html/qmag-example.html @@ -34,7 +34,7 @@ body { background: #ffffff; color: black; } <p> This is a simple magnifier-type program. It shows how one can do -some tquite low-level operations in a portable way using TQt. +some quite low-level operations in a portable way using TQt. <p> Run it, click in the magnifier window, then click where you want to magnify or drag out a rectangle. Two combo boxes let you select amplification and refresh frequency, a text label tells you the color @@ -94,7 +94,7 @@ private: <a href="qcombobox.html">TQComboBox</a> *refresh; <a href="qpushbutton.html">TQPushButton</a> *saveButton; <a href="qpushbutton.html">TQPushButton</a> *multiSaveButton; - <a href="qpushbutton.html">TQPushButton</a> *tquitButton; + <a href="qpushbutton.html">TQPushButton</a> *quitButton; <a href="qpixmap.html">TQPixmap</a> pm; // pixmap, magnified <a href="qpixmap.html">TQPixmap</a> p; // pixmap <a href="qimage.html">TQImage</a> image; // image of pixmap (for RGB) @@ -171,12 +171,12 @@ static const int timer[] = { <a name="x1798"></a> multiSaveButton-><a href="qwidget.html#setGeometry">setGeometry</a>( saveButton-><a href="qwidget.html#geometry">geometry</a>().right() + 2, 2, 10+multiSaveButton-><a href="qwidget.html#fontMetrics">fontMetrics</a>().width("MultiSave"), 20 ); - tquitButton = new <a href="qpushbutton.html">TQPushButton</a>( this ); - <a href="qapplication.html#Q_CHECK_PTR">Q_CHECK_PTR</a>(tquitButton); - <a href="qobject.html#connect">connect</a>( tquitButton, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); - tquitButton-><a href="qbutton.html#setText">setText</a>( "Quit" ); - tquitButton-><a href="qwidget.html#setGeometry">setGeometry</a>( multiSaveButton-><a href="qwidget.html#geometry">geometry</a>().right() + 2, 2, - 10+tquitButton-><a href="qwidget.html#fontMetrics">fontMetrics</a>().width("Quit"), 20 ); + quitButton = new <a href="qpushbutton.html">TQPushButton</a>( this ); + <a href="qapplication.html#Q_CHECK_PTR">Q_CHECK_PTR</a>(quitButton); + <a href="qobject.html#connect">connect</a>( quitButton, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#quit">quit</a>()) ); + quitButton-><a href="qbutton.html#setText">setText</a>( "Quit" ); + quitButton-><a href="qwidget.html#setGeometry">setGeometry</a>( multiSaveButton-><a href="qwidget.html#geometry">geometry</a>().right() + 2, 2, + 10+quitButton-><a href="qwidget.html#fontMetrics">fontMetrics</a>().width("Quit"), 20 ); #else zoom = 0; multiSaveButton = 0; @@ -195,8 +195,8 @@ static const int timer[] = { <a name="x1799"></a> yoffset = zoom-><a href="qwidget.html#height">height</a>() // top buttons + 4 // space around top buttons + rgb-><a href="qwidget.html#height">height</a>(); // color-value text height -<a name="x1804"></a> <a href="qwidget.html#setMinimumSize">setMinimumSize</a>( tquitButton-><a href="qwidget.html#pos">pos</a>().x(), yoffset+20 ); - <a href="qwidget.html#resize">resize</a>( tquitButton-><a href="qwidget.html#geometry">geometry</a>().topRight().x() + 2, yoffset+60 ); +<a name="x1804"></a> <a href="qwidget.html#setMinimumSize">setMinimumSize</a>( quitButton-><a href="qwidget.html#pos">pos</a>().x(), yoffset+20 ); + <a href="qwidget.html#resize">resize</a>( quitButton-><a href="qwidget.html#geometry">geometry</a>().topRight().x() + 2, yoffset+60 ); #else yoffset = 0; <a href="qwidget.html#resize">resize</a>(350,350); diff --git a/doc/html/qmake-manual-5.html b/doc/html/qmake-manual-5.html index af2e921d1..e19123409 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 tquite 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 retquired. <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-8.html b/doc/html/qmake-manual-8.html index 19e875d4d..e21c9779a 100644 --- a/doc/html/qmake-manual-8.html +++ b/doc/html/qmake-manual-8.html @@ -648,7 +648,7 @@ QMAKE_VERS = $$[QMAKE_VERSION] <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> </ul><p>Note: the QMAKESPEC path will automatically be added to the <a href="qmake-manual-8.html#INCLUDEPATH">INCLUDEPATH</a> system variable.</p> <a name="INSTALLS"></a><h4><a name="7-2"></a>INSTALLS</h4> -<p>It is common on UNIX to be able to install from the same utility as you build with (e.g make install). For this <em>qmake</em> has introduce the concept of an install set. The notation for this is tquite simple, first you fill in an "object" in qmake for example:</p> +<p>It is common on UNIX to be able to install from the same utility as you build with (e.g make install). For this <em>qmake</em> has introduce the concept of an install set. The notation for this is quite simple, first you fill in an "object" in qmake for example:</p> <pre> documentation.path = /usr/local/program/doc documentation.files = docs/* @@ -698,7 +698,7 @@ QMAKE_VERS = $$[QMAKE_VERSION] <li><p>QMAKE_EXT_H - Changes interpretation all files with these suffixes to be C header files.</p> </ul><a name="Customizing"></a><h4><a name="7-6"></a>Customizing Makefile Output</h4> <p>qmake often tries to be all things to all build tools, this is often less than ideal when you really need to run special platform dependent commands. This can be achieved with specific instructions to the different qmake backends (currently this is only supported by the UNIX <a href="qmake-manual-8.html#MAKEFILE_GENERATOR">generator</a>).</p> -<p>The interfaces to customizing the Makefile are done through "objects" as in other places in qmake. The notation for this is tquite simple, first you fill in an "object" in qmake for example:</p> +<p>The interfaces to customizing the Makefile are done through "objects" as in other places in qmake. The notation for this is quite simple, first you fill in an "object" in qmake for example:</p> <pre> mytarget.target = .buildfile mytarget.commands = touch $$mytarget.target diff --git a/doc/html/qmenubar.html b/doc/html/qmenubar.html index fe899bdaa..f20722642 100644 --- a/doc/html/qmenubar.html +++ b/doc/html/qmenubar.html @@ -168,10 +168,10 @@ the Application Menu <tr bgcolor="#d0d0d0"> <td valign="top">config, options, setup, settings or preferences <td valign="top">Application Menu | Preferences <td valign="top">If this entry is not found the Settings item will be disabled -<tr bgcolor="#f0f0f0"> <td valign="top">tquit or exit +<tr bgcolor="#f0f0f0"> <td valign="top">quit or exit <td valign="top">Application Menu | Quit <application name> <td valign="top">If this entry is not found a default Quit item will be -created to call <a href="qapplication.html#tquit">TQApplication::tquit</a>() +created to call <a href="qapplication.html#quit">TQApplication::quit</a>() </table></center> <p> <a href="menu-example.html">menu/menu.cpp</a> is an example of TQMenuBar and <a href="qpopupmenu.html">TQPopupMenu</a> use. @@ -260,7 +260,7 @@ even widgets into popup menus. argument. Use this to insert submenus into existing menus or pulldown menus into a menu bar. <p> The number of insert functions may look confusing, but they are -actually tquite simple to use. +actually quite simple to use. <p> This default version inserts a menu item with the text <em>text</em>, the accelerator key <em>accel</em>, an id and an optional index and connects it to the slot <em>member</em> in the object <em>receiver</em>. diff --git a/doc/html/qmenudata.html b/doc/html/qmenudata.html index 80dfd8eb5..5923d3440 100644 --- a/doc/html/qmenudata.html +++ b/doc/html/qmenudata.html @@ -284,7 +284,7 @@ even widgets into popup menus. argument. Use this to insert submenus into existing menus or pulldown menus into a menu bar. <p> The number of insert functions may look confusing, but they are -actually tquite simple to use. +actually quite simple to use. <p> This default version inserts a menu item with the text <em>text</em>, the accelerator key <em>accel</em>, an id and an optional index and connects it to the slot <em>member</em> in the object <em>receiver</em>. @@ -619,7 +619,7 @@ object. fileMenu-><a href="#insertItem">insertItem</a>( "Open Document", 67 ); // add "Open" item fileMenu-><a href="#setAccel">setAccel</a>( CTRL + Key_O, 67 ); // Ctrl+O to open fileMenu-><a href="#insertItem">insertItem</a>( "Quit", 69 ); // add "Quit" item - fileMenu-><a href="#setAccel">setAccel</a>( CTRL + ALT + Key_Delete, 69 ); // add Alt+Del to tquit + fileMenu-><a href="#setAccel">setAccel</a>( CTRL + ALT + Key_Delete, 69 ); // add Alt+Del to quit mainMenu-><a href="#insertItem">insertItem</a>( "File", fileMenu ); // add the file menu </pre> diff --git a/doc/html/qnetworkprotocol.html b/doc/html/qnetworkprotocol.html index 6aac280c3..78b3e7d3e 100644 --- a/doc/html/qnetworkprotocol.html +++ b/doc/html/qnetworkprotocol.html @@ -206,7 +206,7 @@ Returns TRUE if auto-deleting is enabled; otherwise returns FALSE. <h3 class=fn>bool <a name="checkConnection"></a>TQNetworkProtocol::checkConnection ( <a href="qnetworkoperation.html">TQNetworkOperation</a> * op )<tt> [virtual protected]</tt> </h3> For processing operations the network protocol base class calls -this method tquite often. This should be reimplemented by new +this method quite often. This should be reimplemented by new network protocols. It should return TRUE if the connection is OK (open); otherwise it should return FALSE. If the connection is not open the protocol should open it. diff --git a/doc/html/qobject.html b/doc/html/qobject.html index b84fedca1..2cf997252 100644 --- a/doc/html/qobject.html +++ b/doc/html/qobject.html @@ -741,7 +741,7 @@ of a <a href="qregexp.html">TQRegExp</a>. If <em>regexpMatch</em> is FALSE, <em> and object names must match it exactly. <p> Note that <em>inheritsClass</em> uses single inheritance from TQObject, the way <a href="#inherits">inherits</a>() does. According to inherits(), <a href="qmenubar.html">TQMenuBar</a> -inherits <a href="qwidget.html">TQWidget</a> but not <a href="qmenudata.html">TQMenuData</a>. This does not tquite match +inherits <a href="qwidget.html">TQWidget</a> but not <a href="qmenudata.html">TQMenuData</a>. This does not quite match reality, but is the best that can be done on the wide variety of compilers TQt supports. <p> Finally, if <em>recursiveSearch</em> is TRUE (the default), <a href="#queryList">queryList</a>() diff --git a/doc/html/qpopupmenu.html b/doc/html/qpopupmenu.html index 17a6dfbd6..d56e13940 100644 --- a/doc/html/qpopupmenu.html +++ b/doc/html/qpopupmenu.html @@ -386,7 +386,7 @@ even widgets into popup menus. argument. Use this to insert submenus into existing menus or pulldown menus into a menu bar. <p> The number of insert functions may look confusing, but they are -actually tquite simple to use. +actually quite simple to use. <p> This default version inserts a menu item with the text <em>text</em>, the accelerator key <em>accel</em>, an id and an optional index and connects it to the slot <em>member</em> in the object <em>receiver</em>. @@ -735,7 +735,7 @@ object. fileMenu-><a href="qmenudata.html#insertItem">insertItem</a>( "Open Document", 67 ); // add "Open" item fileMenu-><a href="qmenudata.html#setAccel">setAccel</a>( CTRL + Key_O, 67 ); // Ctrl+O to open fileMenu-><a href="qmenudata.html#insertItem">insertItem</a>( "Quit", 69 ); // add "Quit" item - fileMenu-><a href="qmenudata.html#setAccel">setAccel</a>( CTRL + ALT + Key_Delete, 69 ); // add Alt+Del to tquit + fileMenu-><a href="qmenudata.html#setAccel">setAccel</a>( CTRL + ALT + Key_Delete, 69 ); // add Alt+Del to quit mainMenu-><a href="qmenudata.html#insertItem">insertItem</a>( "File", fileMenu ); // add the file menu </pre> diff --git a/doc/html/qptrqueue.html b/doc/html/qptrqueue.html index a98474a32..b79acb513 100644 --- a/doc/html/qptrqueue.html +++ b/doc/html/qptrqueue.html @@ -188,7 +188,7 @@ was an item, i.e. the queue wasn't empty; otherwise returns FALSE. <p> Sets the queue to auto-delete its contents if <em>enable</em> is TRUE and not to delete them if <em>enable</em> is FALSE. <p> If auto-deleting is turned on, all the items in a queue are -deleted when the queue itself is deleted. This can be tquite +deleted when the queue itself is deleted. This can be quite convenient if the queue has the only pointer to the items. <p> The default setting is FALSE, for safety. If you turn it on, be careful about copying the queue: you might find yourself with two diff --git a/doc/html/qscrollview.html b/doc/html/qscrollview.html index 887e83777..4c97fbbeb 100644 --- a/doc/html/qscrollview.html +++ b/doc/html/qscrollview.html @@ -152,7 +152,7 @@ The TQScrollView widget provides a scrolling area with on-demand scroll bars. <p> The TQScrollView is a large canvas - potentially larger than the coordinate system normally supported by the underlying window -system. This is important because it is tquite easy to go beyond +system. This is important because it is quite easy to go beyond these limitations (e.g. many web pages are more than 32000 pixels high). Additionally, the TQScrollView can have TQWidgets positioned on it that scroll around with the drawn content. These sub-widgets @@ -742,7 +742,7 @@ See the <a href="qscrollview.html#resizePolicy-prop">"resizePolicy"</a> property Sets the scrollview to have a static background if <em>y</em> is TRUE, or a scrolling background if <em>y</em> is FALSE. By default, the background is scrolling. -<p> Be aware that this mode is tquite slow, as a full repaint of the +<p> Be aware that this mode is quite slow, as a full repaint of the visible area has to be triggered on every contents move. <p> <p>See also <a href="#hasStaticBackground">hasStaticBackground</a>(). diff --git a/doc/html/qsessionmanager.html b/doc/html/qsessionmanager.html index 9ad3ae9fb..04077a504 100644 --- a/doc/html/qsessionmanager.html +++ b/doc/html/qsessionmanager.html @@ -106,7 +106,7 @@ the session is shut down, it wants to be restarted at the start of the next session. <li><tt>TQSessionManager::RestartAnyway</tt> - the application wants to be started at the start of the next session, no matter what. (This is useful for -utilities that run just after startup and then tquit.) +utilities that run just after startup and then quit.) <li><tt>TQSessionManager::RestartImmediately</tt> - the application wants to be started immediately whenever it is not running. <li><tt>TQSessionManager::RestartNever</tt> - the application does not want to be restarted diff --git a/doc/html/qsocket.html b/doc/html/qsocket.html index 1899f20b0..955ef0621 100644 --- a/doc/html/qsocket.html +++ b/doc/html/qsocket.html @@ -126,7 +126,7 @@ general, you can treat it as a TQIODevice for writing, and mostly also for reading. The match isn't perfect, since the TQIODevice API is designed for devices that are controlled by the same machine, and an asynchronous peer-to-peer network connection isn't -tquite like that. For example, there is nothing that matches +quite like that. For example, there is nothing that matches <a href="qiodevice.html#size">TQIODevice::size</a>() exactly. The documentation for <a href="#open">open</a>(), <a href="#close">close</a>(), <a href="#flush">flush</a>(), <a href="#size">size</a>(), <a href="#at">at</a>(), <a href="#atEnd">atEnd</a>(), <a href="#readBlock">readBlock</a>(), <a href="#writeBlock">writeBlock</a>(), <a href="#getch">getch</a>(), <a href="#putch">putch</a>(), <a href="#ungetch">ungetch</a>() and <a href="#readLine">readLine</a>() describes the diff --git a/doc/html/qsocketdevice.html b/doc/html/qsocketdevice.html index 3b8350404..571bee68f 100644 --- a/doc/html/qsocketdevice.html +++ b/doc/html/qsocketdevice.html @@ -249,7 +249,7 @@ Returns TRUE if this is a valid socket; otherwise returns FALSE. </h3> Specifies how many pending connections a server socket can have. Returns TRUE if the operation was successful; otherwise returns -FALSE. A <em>backlog</em> value of 50 is tquite common. +FALSE. A <em>backlog</em> value of 50 is quite common. <p> The <a href="#listen">listen</a>() call only applies to sockets where <a href="#type">type</a>() is <a href="#Type-enum">Stream</a>, i.e. not to <a href="#Type-enum">Datagram</a> sockets. listen() must not be called before <a href="#bind">bind</a>() or after <a href="#accept">accept</a>(). <p> <p>See also <a href="#bind">bind</a>() and <a href="#accept">accept</a>(). diff --git a/doc/html/qt.dcf b/doc/html/qt.dcf index 0ea63b12a..107f90c70 100644 --- a/doc/html/qt.dcf +++ b/doc/html/qt.dcf @@ -185,7 +185,7 @@ <keyword ref="qapplication.html#polish">polish</keyword> <keyword ref="qapplication.html#postEvent">postEvent</keyword> <keyword ref="qapplication.html#processEvents">processEvents</keyword> - <keyword ref="qapplication.html#tquit">tquit</keyword> + <keyword ref="qapplication.html#quit">quit</keyword> <keyword ref="qapplication.html#qwsDecoration">qwsDecoration</keyword> <keyword ref="qapplication.html#qwsEventFilter">qwsEventFilter</keyword> <keyword ref="qapplication.html#qwsSetCustomColors">qwsSetCustomColors</keyword> diff --git a/doc/html/qtimer.html b/doc/html/qtimer.html index db1f79100..6b20cb856 100644 --- a/doc/html/qtimer.html +++ b/doc/html/qtimer.html @@ -147,7 +147,7 @@ to create a local TQTimer object. int main( int argc, char **argv ) { <a href="qapplication.html">TQApplication</a> a( argc, argv ); - TQTimer::<a href="#singleShot">singleShot</a>( 10*60*1000, &a, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + TQTimer::<a href="#singleShot">singleShot</a>( 10*60*1000, &a, SLOT(<a href="qapplication.html#quit">quit</a>()) ); ... // create and show your widgets return a.<a href="qapplication.html#exec">exec</a>(); } diff --git a/doc/html/qtooltip.html b/doc/html/qtooltip.html index 7f501c2ab..4ddd9b9e8 100644 --- a/doc/html/qtooltip.html +++ b/doc/html/qtooltip.html @@ -102,21 +102,21 @@ lets the mouse hover for five seconds or moves the mouse outside <p> To add a tip to a widget, call the <em>static</em> function <a href="#add">TQToolTip::add</a>() with the widget and tip as arguments: <p> <pre> - TQToolTip::<a href="#add">add</a>( tquitButton, "Leave the application" ); + TQToolTip::<a href="#add">add</a>( quitButton, "Leave the application" ); </pre> <p> This is the simplest and most common use of TQToolTip. The tip -will be deleted automatically when <em>tquitButton</em> is deleted, but +will be deleted automatically when <em>quitButton</em> is deleted, but you can remove it yourself, too: <p> <pre> - TQToolTip::<a href="#remove">remove</a>( tquitButton ); + TQToolTip::<a href="#remove">remove</a>( quitButton ); </pre> <p> You can also display another text (typically in a <a href="qstatusbar.html">status bar),</a> courtesy of <a href="qtooltipgroup.html">TQToolTipGroup</a>. This example assumes that <em>grp</em> is a <tt>TQToolTipGroup *</tt> and is already connected to the appropriate status bar: <p> <pre> - TQToolTip::<a href="#add">add</a>( tquitButton, "Leave the application", grp, + TQToolTip::<a href="#add">add</a>( quitButton, "Leave the application", grp, "Leave the application, prompting to save if necessary" ); TQToolTip::<a href="#add">add</a>( closeButton, "Close this window", grp, "Close this window, prompting to save if necessary" ); diff --git a/doc/html/qwerty-example.html b/doc/html/qwerty-example.html index b9d16bd8f..8bd0b6e8f 100644 --- a/doc/html/qwerty-example.html +++ b/doc/html/qwerty-example.html @@ -492,7 +492,7 @@ int main( int argc, char **argv ) e-><a href="qwidget.html#show">show</a>(); } } -<a name="x416"></a> a.<a href="qobject.html#connect">connect</a>( &a, SIGNAL(<a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>()), &a, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); +<a name="x416"></a> a.<a href="qobject.html#connect">connect</a>( &a, SIGNAL(<a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>()), &a, SLOT(<a href="qapplication.html#quit">quit</a>()) ); return a.<a href="qapplication.html#exec">exec</a>(); } </pre> diff --git a/doc/html/qwidget.html b/doc/html/qwidget.html index 982c0a192..2d76389b2 100644 --- a/doc/html/qwidget.html +++ b/doc/html/qwidget.html @@ -569,7 +569,7 @@ If not, it will be a child of <em>parent</em>, and be constrained by <em>parent< <a href="qt.html#WidgetFlags">widget flag</a>). <li> <tt>const char *name = 0</tt> is the widget name of the new widget. You can access it using <a href="qobject.html#name">name</a>(). The widget name is little -used by programmers but is tquite useful with GUI builders such as +used by programmers but is quite useful with GUI builders such as <em>TQt Designer</em> (you can name a widget in <em>TQt Designer</em>, and <a href="qobject.html#connect">connect</a>() to it using the name in your code). The <a href="qobject.html#dumpObjectTree">dumpObjectTree</a>() debugging function also uses it. @@ -606,10 +606,10 @@ somewhere else, then releases, <em>your</em> widget receives the release event. There is one exception: if a popup menu appears while the mouse button is held down, this popup immediately steals the mouse events. -<p> <li> <a href="#mouseDoubleClickEvent">mouseDoubleClickEvent</a>() - not tquite as obvious as it might seem. +<p> <li> <a href="#mouseDoubleClickEvent">mouseDoubleClickEvent</a>() - not quite as obvious as it might seem. If the user double-clicks, the widget receives a mouse press event (perhaps a mouse move event or two if they don't hold the mouse -tquite steady), a mouse release event and finally this event. It is +quite steady), a mouse release event and finally this event. It is <em>not possible</em> to distinguish a click from a double click until you've seen whether the second click arrives. (This is one reason why most GUI books recommend that double clicks be an extension of single clicks, @@ -855,7 +855,7 @@ no matter if the widget is visible or not. last visible top level widget is closed. <p> Note that closing the <a href="qapplication.html#mainWidget">TQApplication::mainWidget</a>() terminates the application. -<p> <p>See also <a href="#closeEvent">closeEvent</a>(), <a href="qcloseevent.html">TQCloseEvent</a>, <a href="#hide">hide</a>(), <a href="qapplication.html#tquit">TQApplication::tquit</a>(), <a href="qapplication.html#setMainWidget">TQApplication::setMainWidget</a>(), and <a href="qapplication.html#lastWindowClosed">TQApplication::lastWindowClosed</a>(). +<p> <p>See also <a href="#closeEvent">closeEvent</a>(), <a href="qcloseevent.html">TQCloseEvent</a>, <a href="#hide">hide</a>(), <a href="qapplication.html#quit">TQApplication::quit</a>(), <a href="qapplication.html#setMainWidget">TQApplication::setMainWidget</a>(), and <a href="qapplication.html#lastWindowClosed">TQApplication::lastWindowClosed</a>(). <h3 class=fn>void <a name="closeEvent"></a>TQWidget::closeEvent ( <a href="qcloseevent.html">TQCloseEvent</a> * e )<tt> [virtual protected]</tt> </h3> diff --git a/doc/html/qxmlsimplereader.html b/doc/html/qxmlsimplereader.html index fa9092dd4..57b112abf 100644 --- a/doc/html/qxmlsimplereader.html +++ b/doc/html/qxmlsimplereader.html @@ -115,7 +115,7 @@ with the incremental argument set to TRUE. <p> Returns FALSE if a parsing error occurs; otherwise returns TRUE. <p> If the input source returns an empty string for the function <a href="qxmlinputsource.html#data">TQXmlInputSource::data</a>(), then this means that the end of the XML -file has been reached; this is tquite important, especially if you +file has been reached; this is quite important, especially if you want to use the reader to parse more than one XML file. <p> The case of the end of the XML file being reached without having finished parsing is not considered to be an error: you can diff --git a/doc/html/regexptester-example.html b/doc/html/regexptester-example.html index 4e16660b3..8afc5d77f 100644 --- a/doc/html/regexptester-example.html +++ b/doc/html/regexptester-example.html @@ -75,7 +75,7 @@ public: <a href="qtable.html">TQTable</a> *resultTable; <a href="qpushbutton.html">TQPushButton</a> *executePushButton; <a href="qpushbutton.html">TQPushButton</a> *copyPushButton; - <a href="qpushbutton.html">TQPushButton</a> *tquitPushButton; + <a href="qpushbutton.html">TQPushButton</a> *quitPushButton; <a href="qstatusbar.html">TQStatusBar</a> *statusBar; public slots: @@ -132,7 +132,7 @@ private: executePushButton = new <a href="qpushbutton.html">TQPushButton</a>(this); <a name="x2484"></a> executePushButton-><a href="qpushbutton.html#setDefault">setDefault</a>(true); copyPushButton = new <a href="qpushbutton.html">TQPushButton</a>(this); - tquitPushButton = new <a href="qpushbutton.html">TQPushButton</a>(this); + quitPushButton = new <a href="qpushbutton.html">TQPushButton</a>(this); statusBar = new <a href="qstatusbar.html">TQStatusBar</a>(this); <a href="qgridlayout.html">TQGridLayout</a> *gridLayout = new <a href="qgridlayout.html">TQGridLayout</a>(2, 2, 6); @@ -148,7 +148,7 @@ private: <a href="qvboxlayout.html">TQVBoxLayout</a> *buttonLayout = new <a href="qvboxlayout.html">TQVBoxLayout</a>(0, 6, 6); buttonLayout-><a href="qboxlayout.html#addWidget">addWidget</a>(executePushButton); buttonLayout-><a href="qboxlayout.html#addWidget">addWidget</a>(copyPushButton); - buttonLayout-><a href="qboxlayout.html#addWidget">addWidget</a>(tquitPushButton); + buttonLayout-><a href="qboxlayout.html#addWidget">addWidget</a>(quitPushButton); buttonLayout-><a href="qboxlayout.html#addStretch">addStretch</a>(1); <a href="qhboxlayout.html">TQHBoxLayout</a> *middleLayout = new <a href="qhboxlayout.html">TQHBoxLayout</a>(0, 6, 6); middleLayout-><a href="qboxlayout.html#addWidget">addWidget</a>(resultTable); @@ -165,7 +165,7 @@ private: <a href="qobject.html#connect">connect</a>(copyPushButton, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), this, SLOT(copy())); <a href="qobject.html#connect">connect</a>(executePushButton, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), this, SLOT(execute())); - <a href="qobject.html#connect">connect</a>(tquitPushButton, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), this, SLOT(<a href="qdialog.html#accept">accept</a>())); + <a href="qobject.html#connect">connect</a>(quitPushButton, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), this, SLOT(<a href="qdialog.html#accept">accept</a>())); execute(); } @@ -267,7 +267,7 @@ void <a name="f559"></a>RegexpTester::languageChange() wildcardCheckBox-><a href="qbutton.html#setText">setText</a>(<a href="qobject.html#tr">tr</a>("&Wildcard")); copyPushButton-><a href="qbutton.html#setText">setText</a>(<a href="qobject.html#tr">tr</a>("&Copy")); executePushButton-><a href="qbutton.html#setText">setText</a>(<a href="qobject.html#tr">tr</a>("&Execute")); - tquitPushButton-><a href="qbutton.html#setText">setText</a>(<a href="qobject.html#tr">tr</a>("&Quit")); + quitPushButton-><a href="qbutton.html#setText">setText</a>(<a href="qobject.html#tr">tr</a>("&Quit")); } </pre> @@ -282,7 +282,7 @@ int main(int argc, char **argv) <a href="qapplication.html">TQApplication</a> app(argc, argv); RegexpTester form; <a name="x2511"></a> form.<a href="qdialog.html#show">show</a>(); -<a name="x2512"></a><a name="x2510"></a><a name="x2509"></a> app.<a href="qobject.html#connect">connect</a>(&app, SIGNAL(<a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>()), &app, SLOT(<a href="qapplication.html#tquit">tquit</a>())); +<a name="x2512"></a><a name="x2510"></a><a name="x2509"></a> app.<a href="qobject.html#connect">connect</a>(&app, SIGNAL(<a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>()), &app, SLOT(<a href="qapplication.html#quit">quit</a>())); return app.<a href="qapplication.html#exec">exec</a>(); } </pre> diff --git a/doc/html/richtext-example.html b/doc/html/richtext-example.html index 692e7a483..8276b17f4 100644 --- a/doc/html/richtext-example.html +++ b/doc/html/richtext-example.html @@ -182,7 +182,7 @@ static const char* sayings[] = { <a name="x466"></a> bPrev-><a href="qwidget.html#setEnabled">setEnabled</a>( FALSE ); -<a name="x462"></a> <a href="qobject.html#connect">connect</a>( bClose, SIGNAL( <a href="qbutton.html#clicked">clicked</a>() ), qApp, SLOT( <a href="qapplication.html#tquit">tquit</a>() ) ); +<a name="x462"></a> <a href="qobject.html#connect">connect</a>( bClose, SIGNAL( <a href="qbutton.html#clicked">clicked</a>() ), qApp, SLOT( <a href="qapplication.html#quit">quit</a>() ) ); <a href="qobject.html#connect">connect</a>( bPrev, SIGNAL( <a href="qbutton.html#clicked">clicked</a>() ), this, SLOT( prev() ) ); <a href="qobject.html#connect">connect</a>( bNext, SIGNAL( <a href="qbutton.html#clicked">clicked</a>() ), this, SLOT( next() ) ); diff --git a/doc/html/rot-example.html b/doc/html/rot-example.html index 91835dc2e..2f66bf1ed 100644 --- a/doc/html/rot-example.html +++ b/doc/html/rot-example.html @@ -103,14 +103,14 @@ private: <a name="x1375"></a> <a href="qobject.html#connect">connect</a>( left, SIGNAL(<a href="qtextedit.html#textChanged">textChanged</a>()), this, SLOT(changeRight()) ); <a href="qobject.html#connect">connect</a>( right, SIGNAL(<a href="qtextedit.html#textChanged">textChanged</a>()), this, SLOT(changeLeft()) ); - <a href="qpushbutton.html">TQPushButton</a> * tquit = new <a href="qpushbutton.html">TQPushButton</a>( "&Quit", this ); -<a name="x1379"></a> tquit-><a href="qwidget.html#setFocusPolicy">setFocusPolicy</a>( NoFocus ); - <a href="qobject.html#connect">connect</a>( tquit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + <a href="qpushbutton.html">TQPushButton</a> * quit = new <a href="qpushbutton.html">TQPushButton</a>( "&Quit", this ); +<a name="x1379"></a> quit-><a href="qwidget.html#setFocusPolicy">setFocusPolicy</a>( NoFocus ); + <a href="qobject.html#connect">connect</a>( quit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#quit">quit</a>()) ); <a href="qgridlayout.html">TQGridLayout</a> * l = new <a href="qgridlayout.html">TQGridLayout</a>( this, 2, 2, 5 ); <a name="x1370"></a> l-><a href="qgridlayout.html#addWidget">addWidget</a>( left, 0, 0 ); l-><a href="qgridlayout.html#addWidget">addWidget</a>( right, 0, 1 ); - l-><a href="qgridlayout.html#addWidget">addWidget</a>( tquit, 1, 1, AlignRight ); + l-><a href="qgridlayout.html#addWidget">addWidget</a>( quit, 1, 1, AlignRight ); <a name="x1378"></a> left-><a href="qwidget.html#setFocus">setFocus</a>(); } diff --git a/doc/html/scrollview-example.html b/doc/html/scrollview-example.html index eb78ca25d..31f30e80a 100644 --- a/doc/html/scrollview-example.html +++ b/doc/html/scrollview-example.html @@ -83,7 +83,7 @@ public: for (int y=0; y<2000-h; y+=h+10) { if (y == 0) { <a href="qbutton.html">TQButton</a>* q=new <a href="qpushbutton.html">TQPushButton</a>("Quit", this); - connect(q, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>())); + connect(q, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#quit">quit</a>())); } else { <a href="qstring.html">TQString</a> str; if ( b > 0 ) { @@ -247,7 +247,7 @@ public: <a href="qpopupmenu.html">TQPopupMenu</a>* file = new <a href="qpopupmenu.html">TQPopupMenu</a>( menubar ); <a href="qapplication.html#Q_CHECK_PTR">Q_CHECK_PTR</a>( file ); <a name="x634"></a> menubar-><a href="qmenudata.html#insertItem">insertItem</a>( "&File", file ); - file-><a href="qmenudata.html#insertItem">insertItem</a>( "Quit", qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + file-><a href="qmenudata.html#insertItem">insertItem</a>( "Quit", qApp, SLOT(<a href="qapplication.html#quit">quit</a>()) ); vp_options = new <a href="qpopupmenu.html">TQPopupMenu</a>( menubar ); <a href="qapplication.html#Q_CHECK_PTR">Q_CHECK_PTR</a>( vp_options ); @@ -473,7 +473,7 @@ int main( int argc, char **argv ) ve3.<a href="qwidget.html#setCaption">setCaption</a>("TQt Example - Scrollviews"); ve3.<a href="qwidget.html#show">show</a>(); - TQObject::<a href="qobject.html#connect">connect</a>(qApp, SIGNAL(<a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>()), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>())); + TQObject::<a href="qobject.html#connect">connect</a>(qApp, SIGNAL(<a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>()), qApp, SLOT(<a href="qapplication.html#quit">quit</a>())); return a.<a href="qapplication.html#exec">exec</a>(); } diff --git a/doc/html/showimg-example.html b/doc/html/showimg-example.html index ff42ab332..99828891d 100644 --- a/doc/html/showimg-example.html +++ b/doc/html/showimg-example.html @@ -195,7 +195,7 @@ private slots: si = file-><a href="qmenudata.html#insertItem">insertItem</a>( "Save image", saveimage ); sp = file-><a href="qmenudata.html#insertItem">insertItem</a>( "Save pixmap", savepixmap ); <a name="x1328"></a> file-><a href="qmenudata.html#insertSeparator">insertSeparator</a>(); - file-><a href="qmenudata.html#insertItem">insertItem</a>( "E&xit", qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()), CTRL+Key_Q ); + file-><a href="qmenudata.html#insertItem">insertItem</a>( "E&xit", qApp, SLOT(<a href="qapplication.html#quit">quit</a>()), CTRL+Key_Q ); edit = new <a href="qpopupmenu.html">TQPopupMenu</a>( menubar ); menubar-><a href="qmenudata.html#insertItem">insertItem</a>( "&Edit", edit ); @@ -865,7 +865,7 @@ int main( int argc, char **argv ) } } - TQObject::<a href="qobject.html#connect">connect</a>(qApp, SIGNAL(<a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>()), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>())); + TQObject::<a href="qobject.html#connect">connect</a>(qApp, SIGNAL(<a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>()), qApp, SLOT(<a href="qapplication.html#quit">quit</a>())); return a.<a href="qapplication.html#exec">exec</a>(); } diff --git a/doc/html/signalsandslots.html b/doc/html/signalsandslots.html index 02a0d1566..a3f18f2a2 100644 --- a/doc/html/signalsandslots.html +++ b/doc/html/signalsandslots.html @@ -229,9 +229,9 @@ rest of the world. may connect signals to. This is intended for very tightly connected classes, where even subclasses aren't trusted to get the connections right. -<p> You can also define slots to be virtual, which we have found tquite +<p> You can also define slots to be virtual, which we have found quite useful in practice. -<p> The signals and slots mechanism is efficient, but not tquite as fast as +<p> The signals and slots mechanism is efficient, but not quite as fast as "real" callbacks. Signals and slots are slightly slower because of the increased flexibility they provide, although the difference for real applications is insignificant. In general, emitting a signal that is diff --git a/doc/html/simple-application-example.html b/doc/html/simple-application-example.html index 0eb57587c..fd7877e36 100644 --- a/doc/html/simple-application-example.html +++ b/doc/html/simple-application-example.html @@ -408,7 +408,7 @@ int main( int argc, char ** argv ) { ApplicationWindow *mw = new ApplicationWindow(); mw-><a href="qwidget.html#setCaption">setCaption</a>( "TQt Example - Application" ); <a name="x1598"></a> mw-><a href="qwidget.html#show">show</a>(); -<a name="x1599"></a> a.<a href="qobject.html#connect">connect</a>( &a, SIGNAL(<a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>()), &a, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); +<a name="x1599"></a> a.<a href="qobject.html#connect">connect</a>( &a, SIGNAL(<a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>()), &a, SLOT(<a href="qapplication.html#quit">quit</a>()) ); return a.<a href="qapplication.html#exec">exec</a>(); } </pre> diff --git a/doc/html/simple-application.html b/doc/html/simple-application.html index 239908cd7..b029bc846 100644 --- a/doc/html/simple-application.html +++ b/doc/html/simple-application.html @@ -118,7 +118,7 @@ int main( int argc, char ** argv ) { ApplicationWindow *mw = new ApplicationWindow(); mw-><a href="qwidget.html#setCaption">setCaption</a>( "TQt Example - Application" ); <a name="x1598"></a> mw-><a href="qwidget.html#show">show</a>(); -<a name="x1599"></a> a.<a href="qobject.html#connect">connect</a>( &a, SIGNAL(<a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>()), &a, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); +<a name="x1599"></a> a.<a href="qobject.html#connect">connect</a>( &a, SIGNAL(<a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>()), &a, SLOT(<a href="qapplication.html#quit">quit</a>()) ); return a.<a href="qapplication.html#exec">exec</a>(); } </pre> @@ -141,9 +141,9 @@ behave the way X clients are expected to. <p> We create an <em>ApplicationWindow</em> as a top-level widget, set its window system caption to "Document 1", and <em>show()</em> it. <p> <a name="close"></a> -<pre> a.<a href="qobject.html#connect">connect</a>( &a, SIGNAL(<a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>()), &a, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); +<pre> a.<a href="qobject.html#connect">connect</a>( &a, SIGNAL(<a href="qapplication.html#lastWindowClosed">lastWindowClosed</a>()), &a, SLOT(<a href="qapplication.html#quit">quit</a>()) ); </pre> -<p> When the application's last window is closed, it should tquit. Both +<p> When the application's last window is closed, it should quit. Both the signal and the slot are predefined members of <a href="qapplication.html">TQApplication</a>. <p> <pre> return a.<a href="qapplication.html#exec">exec</a>(); </pre> @@ -157,7 +157,7 @@ that TQApplication returns when it leaves the event loop. </h2> <a name="3"></a><p> -<p> Since the implementation is tquite large (almost 300 lines) we +<p> Since the implementation is quite large (almost 300 lines) we won't list the whole thing. (The source code is included in the examples/application directory.) Before we start with the constructor there are three <tt>#include</tt>s worth mentioning: diff --git a/doc/html/sound-example.html b/doc/html/sound-example.html index 0ebf892e6..8fe39cee6 100644 --- a/doc/html/sound-example.html +++ b/doc/html/sound-example.html @@ -128,7 +128,7 @@ private: file-><a href="qmenudata.html#insertItem">insertItem</a>("Play 3 and 4 together", this, SLOT(doPlay34())); file-><a href="qmenudata.html#insertItem">insertItem</a>("Play all together", this, SLOT(doPlay1234())); file-><a href="qmenudata.html#insertSeparator">insertSeparator</a>(); - file-><a href="qmenudata.html#insertItem">insertItem</a>("E&xit", qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>())); + file-><a href="qmenudata.html#insertItem">insertItem</a>("E&xit", qApp, SLOT(<a href="qapplication.html#quit">quit</a>())); <a href="qmainwindow.html#menuBar">menuBar</a>()->insertItem("&File", file); } diff --git a/doc/html/t10-main-cpp.html b/doc/html/t10-main-cpp.html index a0b86164a..1e575a894 100644 --- a/doc/html/t10-main-cpp.html +++ b/doc/html/t10-main-cpp.html @@ -58,10 +58,10 @@ public: <a name="f52"></a>MyWidget::MyWidget( <a href="qwidget.html">TQWidget</a> *parent, const char *name ) : <a href="qwidget.html">TQWidget</a>( parent, name ) { - <a href="qpushbutton.html">TQPushButton</a> *tquit = new <a href="qpushbutton.html">TQPushButton</a>( "&Quit", this, "tquit" ); - tquit-><a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); + <a href="qpushbutton.html">TQPushButton</a> *quit = new <a href="qpushbutton.html">TQPushButton</a>( "&Quit", this, "quit" ); + quit-><a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); - <a href="qobject.html#connect">connect</a>( tquit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + <a href="qobject.html#connect">connect</a>( quit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#quit">quit</a>()) ); LCDRange *angle = new LCDRange( this, "angle" ); angle->setRange( 5, 70 ); @@ -82,7 +82,7 @@ public: force, SLOT(setValue(int)) ); <a href="qgridlayout.html">TQGridLayout</a> *grid = new <a href="qgridlayout.html">TQGridLayout</a>( this, 2, 2, 10 ); - grid-><a href="qgridlayout.html#addWidget">addWidget</a>( tquit, 0, 0 ); + grid-><a href="qgridlayout.html#addWidget">addWidget</a>( quit, 0, 0 ); grid-><a href="qgridlayout.html#addWidget">addWidget</a>( cannonField, 1, 1 ); grid-><a href="qgridlayout.html#setColStretch">setColStretch</a>( 1, 10 ); diff --git a/doc/html/t11-main-cpp.html b/doc/html/t11-main-cpp.html index 3a059a06d..5c852f895 100644 --- a/doc/html/t11-main-cpp.html +++ b/doc/html/t11-main-cpp.html @@ -58,10 +58,10 @@ public: <a name="f66"></a>MyWidget::MyWidget( <a href="qwidget.html">TQWidget</a> *parent, const char *name ) : <a href="qwidget.html">TQWidget</a>( parent, name ) { - <a href="qpushbutton.html">TQPushButton</a> *tquit = new <a href="qpushbutton.html">TQPushButton</a>( "&Quit", this, "tquit" ); - tquit-><a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); + <a href="qpushbutton.html">TQPushButton</a> *quit = new <a href="qpushbutton.html">TQPushButton</a>( "&Quit", this, "quit" ); + quit-><a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); - <a href="qobject.html#connect">connect</a>( tquit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + <a href="qobject.html#connect">connect</a>( quit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#quit">quit</a>()) ); LCDRange *angle = new LCDRange( this, "angle" ); angle->setRange( 5, 70 ); @@ -87,7 +87,7 @@ public: <a href="qobject.html#connect">connect</a>( shoot, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), cannonField, SLOT(shoot()) ); <a href="qgridlayout.html">TQGridLayout</a> *grid = new <a href="qgridlayout.html">TQGridLayout</a>( this, 2, 2, 10 ); - grid-><a href="qgridlayout.html#addWidget">addWidget</a>( tquit, 0, 0 ); + grid-><a href="qgridlayout.html#addWidget">addWidget</a>( quit, 0, 0 ); grid-><a href="qgridlayout.html#addWidget">addWidget</a>( cannonField, 1, 1 ); grid-><a href="qgridlayout.html#setColStretch">setColStretch</a>( 1, 10 ); diff --git a/doc/html/t12-main-cpp.html b/doc/html/t12-main-cpp.html index 2106eb5e3..e20f3dd09 100644 --- a/doc/html/t12-main-cpp.html +++ b/doc/html/t12-main-cpp.html @@ -58,10 +58,10 @@ public: <a name="f86"></a>MyWidget::MyWidget( <a href="qwidget.html">TQWidget</a> *parent, const char *name ) : <a href="qwidget.html">TQWidget</a>( parent, name ) { - <a href="qpushbutton.html">TQPushButton</a> *tquit = new <a href="qpushbutton.html">TQPushButton</a>( "&Quit", this, "tquit" ); - tquit-><a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); + <a href="qpushbutton.html">TQPushButton</a> *quit = new <a href="qpushbutton.html">TQPushButton</a>( "&Quit", this, "quit" ); + quit-><a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); - <a href="qobject.html#connect">connect</a>( tquit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + <a href="qobject.html#connect">connect</a>( quit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#quit">quit</a>()) ); LCDRange *angle = new LCDRange( "ANGLE", this, "angle" ); angle->setRange( 5, 70 ); @@ -87,7 +87,7 @@ public: <a href="qobject.html#connect">connect</a>( shoot, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), cannonField, SLOT(shoot()) ); <a href="qgridlayout.html">TQGridLayout</a> *grid = new <a href="qgridlayout.html">TQGridLayout</a>( this, 2, 2, 10 ); - grid-><a href="qgridlayout.html#addWidget">addWidget</a>( tquit, 0, 0 ); + grid-><a href="qgridlayout.html#addWidget">addWidget</a>( quit, 0, 0 ); grid-><a href="qgridlayout.html#addWidget">addWidget</a>( cannonField, 1, 1 ); grid-><a href="qgridlayout.html#setColStretch">setColStretch</a>( 1, 10 ); diff --git a/doc/html/t13-gamebrd-cpp.html b/doc/html/t13-gamebrd-cpp.html index 62f0a481b..41ecdaca3 100644 --- a/doc/html/t13-gamebrd-cpp.html +++ b/doc/html/t13-gamebrd-cpp.html @@ -53,10 +53,10 @@ body { background: #ffffff; color: black; } <a name="f109"></a>GameBoard::GameBoard( <a href="qwidget.html">TQWidget</a> *parent, const char *name ) : <a href="qwidget.html">TQWidget</a>( parent, name ) { - <a href="qpushbutton.html">TQPushButton</a> *tquit = new <a href="qpushbutton.html">TQPushButton</a>( "&Quit", this, "tquit" ); - tquit-><a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); + <a href="qpushbutton.html">TQPushButton</a> *quit = new <a href="qpushbutton.html">TQPushButton</a>( "&Quit", this, "quit" ); + quit-><a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); - <a href="qobject.html#connect">connect</a>( tquit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + <a href="qobject.html#connect">connect</a>( quit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#quit">quit</a>()) ); LCDRange *angle = new LCDRange( "ANGLE", this, "angle" ); angle->setRange( 5, 70 ); @@ -101,7 +101,7 @@ body { background: #ffffff; color: black; } = new <a href="qlabel.html">TQLabel</a>( "SHOTS LEFT", this, "shotsleftLabel" ); <a href="qgridlayout.html">TQGridLayout</a> *grid = new <a href="qgridlayout.html">TQGridLayout</a>( this, 2, 2, 10 ); - grid-><a href="qgridlayout.html#addWidget">addWidget</a>( tquit, 0, 0 ); + grid-><a href="qgridlayout.html#addWidget">addWidget</a>( quit, 0, 0 ); grid-><a href="qgridlayout.html#addWidget">addWidget</a>( cannonField, 1, 1 ); grid-><a href="qgridlayout.html#setColStretch">setColStretch</a>( 1, 10 ); diff --git a/doc/html/t14-gamebrd-cpp.html b/doc/html/t14-gamebrd-cpp.html index 38289264f..5130978de 100644 --- a/doc/html/t14-gamebrd-cpp.html +++ b/doc/html/t14-gamebrd-cpp.html @@ -55,10 +55,10 @@ body { background: #ffffff; color: black; } <a name="f139"></a>GameBoard::GameBoard( <a href="qwidget.html">TQWidget</a> *parent, const char *name ) : <a href="qwidget.html">TQWidget</a>( parent, name ) { - <a href="qpushbutton.html">TQPushButton</a> *tquit = new <a href="qpushbutton.html">TQPushButton</a>( "&Quit", this, "tquit" ); - tquit-><a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); + <a href="qpushbutton.html">TQPushButton</a> *quit = new <a href="qpushbutton.html">TQPushButton</a>( "&Quit", this, "quit" ); + quit-><a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); - <a href="qobject.html#connect">connect</a>( tquit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + <a href="qobject.html#connect">connect</a>( quit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#quit">quit</a>()) ); LCDRange *angle = new LCDRange( "ANGLE", this, "angle" ); angle->setRange( 5, 70 ); @@ -112,10 +112,10 @@ body { background: #ffffff; color: black; } accel-><a href="qaccel.html#connectItem">connectItem</a>( accel-><a href="qaccel.html#insertItem">insertItem</a>( Key_Return ), this, SLOT(fire()) ); accel-><a href="qaccel.html#connectItem">connectItem</a>( accel-><a href="qaccel.html#insertItem">insertItem</a>( CTRL+Key_Q ), - qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + qApp, SLOT(<a href="qapplication.html#quit">quit</a>()) ); <a href="qgridlayout.html">TQGridLayout</a> *grid = new <a href="qgridlayout.html">TQGridLayout</a>( this, 2, 2, 10 ); - grid-><a href="qgridlayout.html#addWidget">addWidget</a>( tquit, 0, 0 ); + grid-><a href="qgridlayout.html#addWidget">addWidget</a>( quit, 0, 0 ); grid-><a href="qgridlayout.html#addWidget">addWidget</a>( box, 1, 1 ); grid-><a href="qgridlayout.html#setColStretch">setColStretch</a>( 1, 10 ); diff --git a/doc/html/t7-main-cpp.html b/doc/html/t7-main-cpp.html index 2355f3946..bd7132d32 100644 --- a/doc/html/t7-main-cpp.html +++ b/doc/html/t7-main-cpp.html @@ -58,10 +58,10 @@ public: <a name="f29"></a>MyWidget::MyWidget( <a href="qwidget.html">TQWidget</a> *parent, const char *name ) : <a href="qvbox.html">TQVBox</a>( parent, name ) { - <a href="qpushbutton.html">TQPushButton</a> *tquit = new <a href="qpushbutton.html">TQPushButton</a>( "Quit", this, "tquit" ); - tquit-><a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); + <a href="qpushbutton.html">TQPushButton</a> *quit = new <a href="qpushbutton.html">TQPushButton</a>( "Quit", this, "quit" ); + quit-><a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); - <a href="qobject.html#connect">connect</a>( tquit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + <a href="qobject.html#connect">connect</a>( quit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#quit">quit</a>()) ); <a href="qgrid.html">TQGrid</a> *grid = new <a href="qgrid.html">TQGrid</a>( 4, this ); diff --git a/doc/html/t8-main-cpp.html b/doc/html/t8-main-cpp.html index 0d5f4d012..b0233cdb2 100644 --- a/doc/html/t8-main-cpp.html +++ b/doc/html/t8-main-cpp.html @@ -58,10 +58,10 @@ public: <a name="f36"></a>MyWidget::MyWidget( <a href="qwidget.html">TQWidget</a> *parent, const char *name ) : <a href="qwidget.html">TQWidget</a>( parent, name ) { - <a href="qpushbutton.html">TQPushButton</a> *tquit = new <a href="qpushbutton.html">TQPushButton</a>( "Quit", this, "tquit" ); - tquit-><a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); + <a href="qpushbutton.html">TQPushButton</a> *quit = new <a href="qpushbutton.html">TQPushButton</a>( "Quit", this, "quit" ); + quit-><a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); - <a href="qobject.html#connect">connect</a>( tquit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + <a href="qobject.html#connect">connect</a>( quit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#quit">quit</a>()) ); LCDRange *angle = new LCDRange( this, "angle" ); angle->setRange( 5, 70 ); @@ -77,7 +77,7 @@ public: <a href="qgridlayout.html">TQGridLayout</a> *grid = new <a href="qgridlayout.html">TQGridLayout</a>( this, 2, 2, 10 ); //2x2, 10 pixel border - grid-><a href="qgridlayout.html#addWidget">addWidget</a>( tquit, 0, 0 ); + grid-><a href="qgridlayout.html#addWidget">addWidget</a>( quit, 0, 0 ); grid-><a href="qgridlayout.html#addWidget">addWidget</a>( angle, 1, 0, TQt::AlignTop ); grid-><a href="qgridlayout.html#addWidget">addWidget</a>( cannonField, 1, 1 ); grid-><a href="qgridlayout.html#setColStretch">setColStretch</a>( 1, 10 ); diff --git a/doc/html/t9-main-cpp.html b/doc/html/t9-main-cpp.html index e9ca64c0a..6ecb07511 100644 --- a/doc/html/t9-main-cpp.html +++ b/doc/html/t9-main-cpp.html @@ -58,10 +58,10 @@ public: <a name="f43"></a>MyWidget::MyWidget( <a href="qwidget.html">TQWidget</a> *parent, const char *name ) : <a href="qwidget.html">TQWidget</a>( parent, name ) { - <a href="qpushbutton.html">TQPushButton</a> *tquit = new <a href="qpushbutton.html">TQPushButton</a>( "&Quit", this, "tquit" ); - tquit-><a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); + <a href="qpushbutton.html">TQPushButton</a> *quit = new <a href="qpushbutton.html">TQPushButton</a>( "&Quit", this, "quit" ); + quit-><a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); - <a href="qobject.html#connect">connect</a>( tquit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + <a href="qobject.html#connect">connect</a>( quit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#quit">quit</a>()) ); LCDRange *angle = new LCDRange( this, "angle" ); angle->setRange( 5, 70 ); @@ -74,7 +74,7 @@ public: angle, SLOT(setValue(int)) ); <a href="qgridlayout.html">TQGridLayout</a> *grid = new <a href="qgridlayout.html">TQGridLayout</a>( this, 2, 2, 10 ); - grid-><a href="qgridlayout.html#addWidget">addWidget</a>( tquit, 0, 0 ); + grid-><a href="qgridlayout.html#addWidget">addWidget</a>( quit, 0, 0 ); grid-><a href="qgridlayout.html#addWidget">addWidget</a>( angle, 1, 0, TQt::AlignTop ); grid-><a href="qgridlayout.html#addWidget">addWidget</a>( cannonField, 1, 1 ); grid-><a href="qgridlayout.html#setColStretch">setColStretch</a>( 1, 10 ); diff --git a/doc/html/tabdialog-example.html b/doc/html/tabdialog-example.html index a38da3370..a40d1b40e 100644 --- a/doc/html/tabdialog-example.html +++ b/doc/html/tabdialog-example.html @@ -106,7 +106,7 @@ protected: setupTab2(); setupTab3(); - <a href="qobject.html#connect">connect</a>( this, SIGNAL( <a href="qtabdialog.html#applyButtonPressed">applyButtonPressed</a>() ), qApp, SLOT( <a href="qapplication.html#tquit">tquit</a>() ) ); + <a href="qobject.html#connect">connect</a>( this, SIGNAL( <a href="qtabdialog.html#applyButtonPressed">applyButtonPressed</a>() ), qApp, SLOT( <a href="qapplication.html#quit">quit</a>() ) ); } void <a name="f201"></a>TabDialog::setupTab1() diff --git a/doc/html/themes-example.html b/doc/html/themes-example.html index dbd93459f..b30208b18 100644 --- a/doc/html/themes-example.html +++ b/doc/html/themes-example.html @@ -2253,7 +2253,7 @@ private: } <a name="x318"></a> ag-><a href="qactiongroup.html#addTo">addTo</a>(style); style-><a href="qmenudata.html#insertSeparator">insertSeparator</a>(); - style-><a href="qmenudata.html#insertItem">insertItem</a>("&Quit", qApp, SLOT( <a href="qapplication.html#tquit">tquit</a>() ), CTRL | Key_Q ); + style-><a href="qmenudata.html#insertItem">insertItem</a>("&Quit", qApp, SLOT( <a href="qapplication.html#quit">quit</a>() ), CTRL | Key_Q ); <a href="qpopupmenu.html">TQPopupMenu</a> * help = new <a href="qpopupmenu.html">TQPopupMenu</a>( this ); <a href="qmainwindow.html#menuBar">menuBar</a>()->insertSeparator(); diff --git a/doc/html/tictac-example.html b/doc/html/tictac-example.html index 32dde137c..c1631b5b3 100644 --- a/doc/html/tictac-example.html +++ b/doc/html/tictac-example.html @@ -126,7 +126,7 @@ private: // -------------------------------------------------------------------------- // TicTacToe implements the complete game. // TicTacToe is a composite widget that contains a TicTacGameBoard and -// two push buttons for starting the game and tquitting. +// two push buttons for starting the game and quitting. // class TicTacToe : public <a href="qwidget.html">TQWidget</a> @@ -141,7 +141,7 @@ private: void newState(); <a href="qcombobox.html">TQComboBox</a> *whoStarts; <a href="qpushbutton.html">TQPushButton</a> *newGame; - <a href="qpushbutton.html">TQPushButton</a> *tquit; + <a href="qpushbutton.html">TQPushButton</a> *quit; <a href="qlabel.html">TQLabel</a> *message; TicTacGameBoard *board; }; @@ -478,12 +478,12 @@ void <a name="f195"></a>TicTacGameBoard::computerMove() newGame = new <a href="qpushbutton.html">TQPushButton</a>( "Play!", this ); <a href="qobject.html#connect">connect</a>( newGame, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), SLOT(newGameClicked()) ); - tquit = new <a href="qpushbutton.html">TQPushButton</a>( "Quit", this ); - <a href="qobject.html#connect">connect</a>( tquit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + quit = new <a href="qpushbutton.html">TQPushButton</a>( "Quit", this ); + <a href="qobject.html#connect">connect</a>( quit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#quit">quit</a>()) ); <a href="qhboxlayout.html">TQHBoxLayout</a> * b = new <a href="qhboxlayout.html">TQHBoxLayout</a>; <a name="x19"></a> l-><a href="qboxlayout.html#addLayout">addLayout</a>( b ); b-><a href="qboxlayout.html#addWidget">addWidget</a>( newGame ); - b-><a href="qboxlayout.html#addWidget">addWidget</a>( tquit ); + b-><a href="qboxlayout.html#addWidget">addWidget</a>( quit ); newState(); } diff --git a/doc/html/tutorial1-02.html b/doc/html/tutorial1-02.html index 125537d4c..7b84b5ecb 100644 --- a/doc/html/tutorial1-02.html +++ b/doc/html/tutorial1-02.html @@ -34,7 +34,7 @@ body { background: #ffffff; color: black; } <p> <center><img src="t2.png" alt="Screenshot of tutorial two"></center> <p> Having created a window in <a href="tutorial1-01.html">Chapter 1,</a> we will -now go on to make the application tquit properly when the user tells it to. +now go on to make the application quit properly when the user tells it to. <p> We will also use a font that is more exciting than the default one. <p> <pre>/**************************************************************** ** @@ -51,14 +51,14 @@ int main( int argc, char **argv ) { <a href="qapplication.html">TQApplication</a> a( argc, argv ); - <a href="qpushbutton.html">TQPushButton</a> tquit( "Quit", 0 ); - tquit.<a href="qwidget.html#resize">resize</a>( 75, 30 ); - tquit.<a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); + <a href="qpushbutton.html">TQPushButton</a> quit( "Quit", 0 ); + quit.<a href="qwidget.html#resize">resize</a>( 75, 30 ); + quit.<a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); - TQObject::<a href="qobject.html#connect">connect</a>( &tquit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), &a, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + TQObject::<a href="qobject.html#connect">connect</a>( &quit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), &a, SLOT(<a href="qapplication.html#quit">quit</a>()) ); - a.<a href="qapplication.html#setMainWidget">setMainWidget</a>( &tquit ); - tquit.<a href="qwidget.html#show">show</a>(); + a.<a href="qapplication.html#setMainWidget">setMainWidget</a>( &quit ); + quit.<a href="qwidget.html#show">show</a>(); return a.<a href="qapplication.html#exec">exec</a>(); } </pre> @@ -72,22 +72,22 @@ int main( int argc, char **argv ) <p> Since this program uses <a href="qfont.html">TQFont</a>, it needs to include qfont.h. TQt's font abstraction is rather different from the horror provided by X, and loading and using fonts has been highly optimized. -<p> <pre> <a href="qpushbutton.html">TQPushButton</a> tquit( "Quit", 0 ); +<p> <pre> <a href="qpushbutton.html">TQPushButton</a> quit( "Quit", 0 ); </pre> <p> This time, the button says "Quit" and that's exactly what the program will do when the user clicks the button. This is not a coincidence. We still pass 0 as the parent, since the button is a top-level window. -<p> <pre> <a name="x2292"></a> tquit.<a href="qwidget.html#resize">resize</a>( 75, 30 ); +<p> <pre> <a name="x2292"></a> quit.<a href="qwidget.html#resize">resize</a>( 75, 30 ); </pre> <p> We've chosen another size for the button since the text is a bit shorter than "Hello world!". We could also have used <a href="qfontmetrics.html">TQFontMetrics</a> to set right size. -<p> <pre> <a name="x2293"></a> tquit.<a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); +<p> <pre> <a name="x2293"></a> quit.<a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); </pre> <p> Here we choose a new font for the button, an 18-point bold font from the Times family. Note that we create the font on the spot. <p> It is also possible to change the default font (using <a href="qapplication.html#setFont">TQApplication::setFont</a>()) for the whole application. -<p> <pre> <a name="x2291"></a><a name="x2290"></a><a name="x2288"></a> TQObject::<a href="qobject.html#connect">connect</a>( &tquit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), &a, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); +<p> <pre> <a name="x2291"></a><a name="x2290"></a><a name="x2288"></a> TQObject::<a href="qobject.html#connect">connect</a>( &quit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), &a, SLOT(<a href="qapplication.html#quit">quit</a>()) ); </pre> <p> connect() is perhaps <em>the</em> most central feature of TQt. Note that connect() is a static function in <a href="qobject.html">TQObject</a>. Do not confuse it @@ -97,8 +97,8 @@ that inherit TQObject, directly or indirectly). Every TQt object can have both <tt>signals</tt> (to send messages) and <tt>slots</tt> (to receive messages). All widgets are TQt objects. They inherit <a href="qwidget.html">TQWidget</a> which in turn inherits TQObject. -<p> Here, the <em>clicked()</em> signal of <em>tquit</em> is connected to the <em>tquit()</em> slot of <em>a</em>, so that when the button is clicked, the -application tquits. +<p> Here, the <em>clicked()</em> signal of <em>quit</em> is connected to the <em>quit()</em> slot of <em>a</em>, so that when the button is clicked, the +application quits. <p> The <a href="signalsandslots.html">Signals and Slots</a> documentation describes this topic in detail. <p> <h2> Behavior @@ -111,7 +111,7 @@ makefile and build the application.) </h2> <a name="3"></a><p> Try to resize the window. Press the button. Oops! That connect() would seem to make some difference. -<p> Are there any other signals in <a href="qpushbutton.html">TQPushButton</a> you can connect to tquit? +<p> Are there any other signals in <a href="qpushbutton.html">TQPushButton</a> you can connect to quit? Hint: The TQPushButton inherits most of its behavior from <a href="qbutton.html">TQButton</a>. <p> You're now ready for <a href="tutorial1-03.html">Chapter 3.</a> <p> [<a href="tutorial1-01.html">Previous tutorial</a>] diff --git a/doc/html/tutorial1-03.html b/doc/html/tutorial1-03.html index b7bb972d0..b760c089c 100644 --- a/doc/html/tutorial1-03.html +++ b/doc/html/tutorial1-03.html @@ -53,10 +53,10 @@ int main( int argc, char **argv ) <a href="qvbox.html">TQVBox</a> box; box.<a href="qwidget.html#resize">resize</a>( 200, 120 ); - <a href="qpushbutton.html">TQPushButton</a> tquit( "Quit", &box ); - tquit.<a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); + <a href="qpushbutton.html">TQPushButton</a> quit( "Quit", &box ); + quit.<a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); - TQObject::<a href="qobject.html#connect">connect</a>( &tquit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), &a, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + TQObject::<a href="qobject.html#connect">connect</a>( &quit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), &a, SLOT(<a href="qapplication.html#quit">quit</a>()) ); a.<a href="qapplication.html#setMainWidget">setMainWidget</a>( &box ); box.<a href="qwidget.html#show">show</a>(); @@ -80,7 +80,7 @@ space according to each child's <a href="qwidget.html#sizePolicy">TQWidget::size <p> <pre> <a name="x2300"></a> box.<a href="qwidget.html#resize">resize</a>( 200, 120 ); </pre> <p> We set its width to 200 pixels and the height to 120 pixels. -<p> <pre> <a href="qpushbutton.html">TQPushButton</a> tquit( "Quit", &box ); +<p> <pre> <a href="qpushbutton.html">TQPushButton</a> quit( "Quit", &box ); </pre> <p> A child is born. <p> This <a href="qpushbutton.html">TQPushButton</a> is created with both a text ("Quit") and a parent diff --git a/doc/html/tutorial1-04.html b/doc/html/tutorial1-04.html index 005aa983c..820cc797d 100644 --- a/doc/html/tutorial1-04.html +++ b/doc/html/tutorial1-04.html @@ -59,11 +59,11 @@ public: <a href="qwidget.html#setMinimumSize">setMinimumSize</a>( 200, 120 ); <a href="qwidget.html#setMaximumSize">setMaximumSize</a>( 200, 120 ); - <a href="qpushbutton.html">TQPushButton</a> *tquit = new <a href="qpushbutton.html">TQPushButton</a>( "Quit", this, "tquit" ); - tquit-><a href="qwidget.html#setGeometry">setGeometry</a>( 62, 40, 75, 30 ); - tquit-><a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); + <a href="qpushbutton.html">TQPushButton</a> *quit = new <a href="qpushbutton.html">TQPushButton</a>( "Quit", this, "quit" ); + quit-><a href="qwidget.html#setGeometry">setGeometry</a>( 62, 40, 75, 30 ); + quit-><a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); - <a href="qobject.html#connect">connect</a>( tquit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + <a href="qobject.html#connect">connect</a>( quit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#quit">quit</a>()) ); } @@ -116,15 +116,15 @@ constructor. <p> Because this widget doesn't know how to handle resizing, we fix its size by setting the minimum and maximum to be equal. In the next chapter we will show how a widget can respond to resize event from the user. -<p> <pre> <a href="qpushbutton.html">TQPushButton</a> *tquit = new <a href="qpushbutton.html">TQPushButton</a>( "Quit", this, "tquit" ); - <a name="x2308"></a> tquit-><a href="qwidget.html#setGeometry">setGeometry</a>( 62, 40, 75, 30 ); - <a name="x2307"></a> tquit-><a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); +<p> <pre> <a href="qpushbutton.html">TQPushButton</a> *quit = new <a href="qpushbutton.html">TQPushButton</a>( "Quit", this, "quit" ); + <a name="x2308"></a> quit-><a href="qwidget.html#setGeometry">setGeometry</a>( 62, 40, 75, 30 ); + <a name="x2307"></a> quit-><a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); </pre> <p> Here we create and set up a child widget of this widget (the new widget's -parent is <tt>this</tt>) which has the widget name "tquit". The widget +parent is <tt>this</tt>) which has the widget name "quit". The widget name has nothing to do with the button text; it just happens to be similar in this case. -<p> Note that <tt>tquit</tt> is a local variable in the constructor. MyWidget +<p> Note that <tt>quit</tt> is a local variable in the constructor. MyWidget does not keep track of it, but TQt does, and will by default delete it when MyWidget is deleted. This is why MyWidget doesn't need a destructor. (On the other hand, there is no harm in deleting a child @@ -132,7 +132,7 @@ when you choose to, the child will automatically tell TQt about its imminent death.) <p> The setGeometry() call does the same as move() and resize() did in the previous chapters. -<p> <pre> <a name="x2306"></a><a name="x2304"></a> <a href="qobject.html#connect">connect</a>( tquit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); +<p> <pre> <a name="x2306"></a><a name="x2304"></a> <a href="qobject.html#connect">connect</a>( quit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#quit">quit</a>()) ); } </pre> <p> Because the MyWidget class doesn't know about the application object, it diff --git a/doc/html/tutorial1-05.html b/doc/html/tutorial1-05.html index 8aabed708..239448714 100644 --- a/doc/html/tutorial1-05.html +++ b/doc/html/tutorial1-05.html @@ -59,10 +59,10 @@ public: <a name="f553"></a>MyWidget::MyWidget( <a href="qwidget.html">TQWidget</a> *parent, const char *name ) : <a href="qvbox.html">TQVBox</a>( parent, name ) { - <a href="qpushbutton.html">TQPushButton</a> *tquit = new <a href="qpushbutton.html">TQPushButton</a>( "Quit", this, "tquit" ); - tquit-><a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); + <a href="qpushbutton.html">TQPushButton</a> *quit = new <a href="qpushbutton.html">TQPushButton</a>( "Quit", this, "quit" ); + quit-><a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); - <a href="qobject.html#connect">connect</a>( tquit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + <a href="qobject.html#connect">connect</a>( quit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#quit">quit</a>()) ); <a href="qlcdnumber.html">TQLCDNumber</a> *lcd = new <a href="qlcdnumber.html">TQLCDNumber</a>( 2, this, "lcd" ); @@ -152,7 +152,7 @@ makefile and build the application.) buttons to set the number base. <p> You can also change the slider's range. <p> Perhaps it would have been better to use <a href="qspinbox.html">TQSpinBox</a> than a slider? -<p> Try to make the application tquit when the LCD number overflows. +<p> Try to make the application quit when the LCD number overflows. <p> You're now ready for <a href="tutorial1-06.html">Chapter 6.</a> <p> [<a href="tutorial1-04.html">Previous tutorial</a>] [<a href="tutorial1-06.html">Next tutorial</a>] diff --git a/doc/html/tutorial1-06.html b/doc/html/tutorial1-06.html index 96d8cb28a..e85f34bf0 100644 --- a/doc/html/tutorial1-06.html +++ b/doc/html/tutorial1-06.html @@ -77,10 +77,10 @@ public: <a name="f555"></a>MyWidget::MyWidget( <a href="qwidget.html">TQWidget</a> *parent, const char *name ) : <a href="qvbox.html">TQVBox</a>( parent, name ) { - <a href="qpushbutton.html">TQPushButton</a> *tquit = new <a href="qpushbutton.html">TQPushButton</a>( "Quit", this, "tquit" ); - tquit-><a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); + <a href="qpushbutton.html">TQPushButton</a> *quit = new <a href="qpushbutton.html">TQPushButton</a>( "Quit", this, "quit" ); + quit-><a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); - <a href="qobject.html#connect">connect</a>( tquit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + <a href="qobject.html#connect">connect</a>( quit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#quit">quit</a>()) ); <a href="qgrid.html">TQGrid</a> *grid = new <a href="qgrid.html">TQGrid</a>( 4, this ); @@ -136,10 +136,10 @@ is renamed. <p> <pre> MyWidget::MyWidget( <a href="qwidget.html">TQWidget</a> *parent, const char *name ) : <a href="qvbox.html">TQVBox</a>( parent, name ) { - <a href="qpushbutton.html">TQPushButton</a> *tquit = new <a href="qpushbutton.html">TQPushButton</a>( "Quit", this, "tquit" ); - <a name="x2328"></a> tquit-><a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); + <a href="qpushbutton.html">TQPushButton</a> *quit = new <a href="qpushbutton.html">TQPushButton</a>( "Quit", this, "quit" ); + <a name="x2328"></a> quit-><a href="qwidget.html#setFont">setFont</a>( TQFont( "Times", 18, TQFont::Bold ) ); - <a name="x2321"></a> <a href="qobject.html#connect">connect</a>( tquit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + <a name="x2321"></a> <a href="qobject.html#connect">connect</a>( quit, SIGNAL(<a href="qbutton.html#clicked">clicked</a>()), qApp, SLOT(<a href="qapplication.html#quit">quit</a>()) ); </pre> <p> The push button that used to be in what is now LCDRange has been separated so that we can have one "Quit" button and many LCDRange diff --git a/doc/html/tutorial1-08.html b/doc/html/tutorial1-08.html index afb3e3390..bd65a26d9 100644 --- a/doc/html/tutorial1-08.html +++ b/doc/html/tutorial1-08.html @@ -221,7 +221,7 @@ manage the children of <em>any</em> widget. <p> As the comment indicates, we create a two-by-two array with ten pixel borders. (The constructor for <a href="qgridlayout.html">TQGridLayout</a> can be a little cryptic, so it's good to put in such comments.) -<p> <pre> <a name="x2337"></a> grid-><a href="qgridlayout.html#addWidget">addWidget</a>( tquit, 0, 0 ); +<p> <pre> <a name="x2337"></a> grid-><a href="qgridlayout.html#addWidget">addWidget</a>( quit, 0, 0 ); </pre> <p> We add the Quit button in the top-left cell of the grid: 0, 0. <p> <pre> grid-><a href="qgridlayout.html#addWidget">addWidget</a>( angle, 1, 0, TQt::AlignTop ); diff --git a/doc/html/tutorial1-10.html b/doc/html/tutorial1-10.html index a57936906..e25f0c194 100644 --- a/doc/html/tutorial1-10.html +++ b/doc/html/tutorial1-10.html @@ -119,7 +119,7 @@ the drawing a little bit. emit forceChanged( f ); } </pre> -<p> The implementation of setForce() is tquite similar to that of +<p> The implementation of setForce() is quite similar to that of setAngle(). The only difference is that because we don't show the force value, we don't need to repaint the widget. <p> <pre> void CannonField::<a href="qwidget.html#paintEvent">paintEvent</a>( <a href="qpaintevent.html">TQPaintEvent</a> *e ) diff --git a/doc/html/tutorial1-14.html b/doc/html/tutorial1-14.html index b155373eb..957e99832 100644 --- a/doc/html/tutorial1-14.html +++ b/doc/html/tutorial1-14.html @@ -221,12 +221,12 @@ keys. Note that an accelerator is a child of a widget and will be destroyed when that widget is destroyed. <a href="qaccel.html">TQAccel</a> is <em>not</em> a widget and has no visible effect on its parent. <p> We define two shortcut keys. We want the slot fire() to be called -when the user presses Enter, and we want the application to tquit when +when the user presses Enter, and we want the application to quit when key Ctrl+Q is pressed. Because Enter is sometimes Return and there are even keyboards with <em>both</em> keys, we make both Enter and Return invoke fire(). <p> <pre> accel-><a href="qaccel.html#connectItem">connectItem</a>( accel-><a href="qaccel.html#insertItem">insertItem</a>( CTRL+Key_Q ), - qApp, SLOT(<a href="qapplication.html#tquit">tquit</a>()) ); + qApp, SLOT(<a href="qapplication.html#quit">quit</a>()) ); </pre> <p> And then we set up Ctrl+Q to do the same thing as Alt+Q. Some people are more used to Ctrl+Q (and anyway it shows how do do it). @@ -234,7 +234,7 @@ people are more used to Ctrl+Q (and anyway it shows how do do it). TQt. They're actually TQt::Key_Enter, etc., but practically all classes inherit the <a href="qt.html">TQt</a> namespace class. <p> <pre> <a href="qgridlayout.html">TQGridLayout</a> *grid = new <a href="qgridlayout.html">TQGridLayout</a>( this, 2, 2, 10 ); - <a name="x2441"></a> grid-><a href="qgridlayout.html#addWidget">addWidget</a>( tquit, 0, 0 ); + <a name="x2441"></a> grid-><a href="qgridlayout.html#addWidget">addWidget</a>( quit, 0, 0 ); grid-><a href="qgridlayout.html#addWidget">addWidget</a>( box, 1, 1 ); <a name="x2442"></a> grid-><a href="qgridlayout.html#setColStretch">setColStretch</a>( 1, 10 ); </pre> diff --git a/doc/html/tutorial2-05.html b/doc/html/tutorial2-05.html index 9f9bbec06..93195a325 100644 --- a/doc/html/tutorial2-05.html +++ b/doc/html/tutorial2-05.html @@ -124,7 +124,7 @@ context menu. application's GUI. All our drawing operations take place on the canvas; but events (e.g. mouse clicks) take place on the canvas view. </table></center> -<p> Each action is represented by a private slot, e.g. <tt>fileNew()</tt>, <tt>optionsSetData()</tt>, etc. We also have tquite a number of private +<p> Each action is represented by a private slot, e.g. <tt>fileNew()</tt>, <tt>optionsSetData()</tt>, etc. We also have quite a number of private functions and data members; we'll look at all these as we go through the implementation. <p> For the sake of convenience and compilation speed the chart form's @@ -503,7 +503,7 @@ item id. } } </pre> -<p> When the user tquits we give them the opportunity to save any unsaved +<p> When the user quits we give them the opportunity to save any unsaved data (okToClear()) then save their options, e.g. window size and position, chart type, etc., before terminating. <p> <pre> void ChartForm::saveOptions() diff --git a/doc/html/tutorial2-08.html b/doc/html/tutorial2-08.html index 77719f583..b8dbfd86e 100644 --- a/doc/html/tutorial2-08.html +++ b/doc/html/tutorial2-08.html @@ -106,7 +106,7 @@ member functions. <p> We set a caption for the dialog and resize it. <p> <pre> tableButtonBox = new <a href="qvboxlayout.html">TQVBoxLayout</a>( this, 11, 6, "table button box layout" ); </pre> -<p> The layout of the form is tquite simple. The buttons will be grouped +<p> The layout of the form is quite simple. The buttons will be grouped together in a horizontal layout and the table and the button layout will be grouped together vertically using the tableButtonBox layout. <p> <pre> table = new <a href="qtable.html">TQTable</a>( this, "data table" ); diff --git a/doc/html/xml.html b/doc/html/xml.html index 2167b7852..688f5a0f9 100644 --- a/doc/html/xml.html +++ b/doc/html/xml.html @@ -527,7 +527,7 @@ attribute from the <em>http://trolltech.com/fnord/</em> namespace to <em>book:au prefix <em>fnord</em> that is declared in the <em>book:author</em> element. <p> Clearly the <em>fnord</em> namespace has the same namespace URI as the default namespace. So why didn't we simply use the default namespace -we'd already declared? The answer is tquite complex: +we'd already declared? The answer is quite complex: <ul> <li> attributes without a prefix don't belong to any XML namespace at all, not even to the default namespace; diff --git a/doc/i18n.doc b/doc/i18n.doc index d9b7a7ef2..766464023 100644 --- a/doc/i18n.doc +++ b/doc/i18n.doc @@ -271,7 +271,7 @@ it. The correct idiom is \code QPopupMenu *file = new QPopupMenu( this ); - file->insertItem( tr("&Quit"), this, SLOT(tquit()), + file->insertItem( tr("&Quit"), this, SLOT(quit()), QKeySequence(tr("Ctrl+Q", "File|Quit")) ); \endcode diff --git a/doc/man/man3/qaccel.3qt b/doc/man/man3/qaccel.3qt index 07e8f3ee8..9c5e23e5f 100644 --- a/doc/man/man3/qaccel.3qt +++ b/doc/man/man3/qaccel.3qt @@ -176,7 +176,7 @@ Connects the accelerator item \fIid\fR to the slot \fImember\fR of \fIreceiver\f .PP .nf .br - a->connectItem( 201, mainView, SLOT(tquit()) ); + a->connectItem( 201, mainView, SLOT(quit()) ); .br .fi .PP @@ -212,9 +212,9 @@ If \fIid\fR is negative, then the item will be assigned a unique negative identi .br a->insertItem( CTRL + Key_P, 200 ); // Ctrl+P, e.g. to print document .br - a->insertItem( ALT + Key_X, 201 ); // Alt+X, e.g. to tquit + a->insertItem( ALT + Key_X, 201 ); // Alt+X, e.g. to quit .br - a->insertItem( UNICODE_ACCEL + 'q', 202 ); // Unicode 'q', e.g. to tquit + a->insertItem( UNICODE_ACCEL + 'q', 202 ); // Unicode 'q', e.g. to quit .br a->insertItem( Key_D ); // gets a unique negative id < -1 .br diff --git a/doc/man/man3/qapplication.3qt b/doc/man/man3/qapplication.3qt index d76b7561a..88db7b847 100644 --- a/doc/man/man3/qapplication.3qt +++ b/doc/man/man3/qapplication.3qt @@ -466,7 +466,7 @@ Since it also deals with common command line arguments, it is usually a good ide .PP <center>.nf .TS -l - l. Groups of functions System settings desktopSettingsAware(), setDesktopSettingsAware(), cursorFlashTime(), setCursorFlashTime(), doubleClickInterval(), setDoubleClickInterval(), wheelScrollLines(), setWheelScrollLines(), palette(), setPalette(), font(), setFont(), fontMetrics(). Event handling exec(), processEvents(), enter_loop(), exit_loop(), exit(), tquit(). sendEvent(), postEvent(), sendPostedEvents(), removePostedEvents(), hasPendingEvents(), notify(), macEventFilter(), qwsEventFilter(), x11EventFilter(), x11ProcessEvent(), winEventFilter(). GUI Styles style(), setStyle(), polish(). Color usage colorSpec(), setColorSpec(), qwsSetCustomColors(). Text handling installTranslator(), removeTranslator() translate(). Widgets mainWidget(), setMainWidget(), allWidgets(), topLevelWidgets(), desktop(), activePopupWidget(), activeModalWidget(), clipboard(), focusWidget(), winFocus(), activeWindow(), widgetAt(). Advanced cursor handling hasGlobalMouseTracking(), setGlobalMouseTracking(), overrideCursor(), setOverrideCursor(), restoreOverrideCursor(). X Window System synchronization flushX(), syncX(). Session management isSessionRestored(), sessionId(), commitData(), saveState(). Threading lock(), unlock(), locked(), tryLock(), wakeUpGuiThread() Miscellaneous +l - l. Groups of functions System settings desktopSettingsAware(), setDesktopSettingsAware(), cursorFlashTime(), setCursorFlashTime(), doubleClickInterval(), setDoubleClickInterval(), wheelScrollLines(), setWheelScrollLines(), palette(), setPalette(), font(), setFont(), fontMetrics(). Event handling exec(), processEvents(), enter_loop(), exit_loop(), exit(), quit(). sendEvent(), postEvent(), sendPostedEvents(), removePostedEvents(), hasPendingEvents(), notify(), macEventFilter(), qwsEventFilter(), x11EventFilter(), x11ProcessEvent(), winEventFilter(). GUI Styles style(), setStyle(), polish(). Color usage colorSpec(), setColorSpec(), qwsSetCustomColors(). Text handling installTranslator(), removeTranslator() translate(). Widgets mainWidget(), setMainWidget(), allWidgets(), topLevelWidgets(), desktop(), activePopupWidget(), activeModalWidget(), clipboard(), focusWidget(), winFocus(), activeWindow(), widgetAt(). Advanced cursor handling hasGlobalMouseTracking(), setGlobalMouseTracking(), overrideCursor(), setOverrideCursor(), restoreOverrideCursor(). X Window System synchronization flushX(), syncX(). Session management isSessionRestored(), sessionId(), commitData(), saveState(). Threading lock(), unlock(), locked(), tryLock(), wakeUpGuiThread() Miscellaneous .TE .fi </center> @@ -629,11 +629,11 @@ This is useful for inclusion in the Help menu of an application. See the example .PP This function is a convenience slot for QMessageBox::aboutQt(). .SH "void QApplication::aboutToQuit ()\fC [signal]\fR" -This signal is emitted when the application is about to tquit the main event loop, e.g. when the event loop level drops to zero. This may happen either after a call to tquit() from inside the application or when the users shuts down the entire desktop session. +This signal is emitted when the application is about to quit the main event loop, e.g. when the event loop level drops to zero. This may happen either after a call to quit() from inside the application or when the users shuts down the entire desktop session. .PP The signal is particularly useful if your application has to do some last-second cleanup. Note that no user interaction is possible in this state. .PP -See also tquit(). +See also quit(). .SH "QWidget * QApplication::activeModalWidget ()\fC [static]\fR" Returns the active modal widget. .PP @@ -795,15 +795,15 @@ This function is particularly useful for applications with many top-level window file->insertItem( "&Quit", qApp, SLOT(closeAllWindows()), CTRL+Key_Q ); .br .br - // when the last window is closed, the application should tquit + // when the last window is closed, the application should quit .br - connect( qApp, SIGNAL( lastWindowClosed() ), qApp, SLOT( tquit() ) ); + connect( qApp, SIGNAL( lastWindowClosed() ), qApp, SLOT( quit() ) ); .br .fi .PP The windows are closed in random order, until one window does not accept the close event. .PP -See also QWidget::close(), QWidget::closeEvent(), lastWindowClosed(), tquit(), topLevelWidgets(), and QWidget::isTopLevel. +See also QWidget::close(), QWidget::closeEvent(), lastWindowClosed(), quit(), topLevelWidgets(), and QWidget::isTopLevel. .PP Examples: .)l action/application.cpp, application/application.cpp, helpviewer/helpwindow.cpp, mdi/application.cpp, and qwerty/qwerty.cpp. @@ -883,7 +883,7 @@ See also QEventLoop. .PP Example: distributor/distributor.ui.h. .SH "int QApplication::exec ()" -Enters the main event loop and waits until exit() is called or the main widget is destroyed, and returns the value that was set to exit() (which is 0 if exit() is called via tquit()). +Enters the main event loop and waits until exit() is called or the main widget is destroyed, and returns the value that was set to exit() (which is 0 if exit() is called via quit()). .PP It is necessary to call this function to start event handling. The main event loop receives events from the window system and dispatches these to the application widgets. .PP @@ -891,7 +891,7 @@ Generally speaking, no user interaction can take place before calling exec(). As .PP To make your application perform idle processing, i.e. executing a special function whenever there are no pending events, use a QTimer with 0 timeout. More advanced idle processing schemes can be achieved using processEvents(). .PP -See also tquit(), exit(), processEvents(), and setMainWidget(). +See also quit(), exit(), processEvents(), and setMainWidget(). .PP Examples: .)l helpsystem/main.cpp, life/main.cpp, network/archivesearch/main.cpp, network/ftpclient/main.cpp, opengl/main.cpp, t1/main.cpp, and t4/main.cpp. @@ -904,7 +904,7 @@ By convention, a \fIretcode\fR of 0 means success, and any non-zero value indica .PP Note that unlike the C library function of the same name, this function \fIdoes\fR return to the caller -- it is event processing that stops. .PP -See also tquit() and exec(). +See also quit() and exec(). .PP Examples: .)l chart/chartform.cpp, extension/mainform.ui.h, and picture/picture.cpp. @@ -982,7 +982,7 @@ See also sessionId(), commitData(), and saveState(). .SH "void QApplication::lastWindowClosed ()\fC [signal]\fR" This signal is emitted when the user has closed the last top level window. .PP -The signal is very useful when your application has many top level widgets but no main widget. You can then connect it to the tquit() slot. +The signal is very useful when your application has many top level widgets but no main widget. You can then connect it to the quit() slot. .PP For convenience, this signal is \fInot\fR emitted for transient top level widgets such as popup menus and dialogs. .PP @@ -1120,18 +1120,18 @@ This function is useful for adapting Qt to situations where the event processing Using this function in new applications may be an indication of design problems. .PP See also processEvents(), exec(), and QTimer. -.SH "void QApplication::tquit ()\fC [slot]\fR" +.SH "void QApplication::quit ()\fC [slot]\fR" Tells the application to exit with return code 0 (success). Equivalent to calling QApplication::exit( 0 ). .PP -It's common to connect the lastWindowClosed() signal to tquit(), and you also often connect e.g. QButton::clicked() or signals in QAction, QPopupMenu or QMenuBar to it. +It's common to connect the lastWindowClosed() signal to quit(), and you also often connect e.g. QButton::clicked() or signals in QAction, QPopupMenu or QMenuBar to it. .PP Example: .PP .nf .br - QPushButton *tquitButton = new QPushButton( "Quit" ); + QPushButton *quitButton = new QPushButton( "Quit" ); .br - connect( tquitButton, SIGNAL(clicked()), qApp, SLOT(tquit()) ); + connect( quitButton, SIGNAL(clicked()), qApp, SLOT(quit()) ); .br .fi .PP @@ -1404,11 +1404,11 @@ Sets the application's main widget to \fImainWidget\fR. .PP In most respects the main widget is like any other widget, except that if it is closed, the application exits. Note that QApplication does \fInot\fR take ownership of the \fImainWidget\fR, so if you create your main widget on the heap you must delete it yourself. .PP -You need not have a main widget; connecting lastWindowClosed() to tquit() is an alternative. +You need not have a main widget; connecting lastWindowClosed() to quit() is an alternative. .PP For X11, this function also resizes and moves the main widget according to the \fI-geometry\fR command-line option, so you should set the default geometry (using QWidget::setGeometry()) before calling setMainWidget(). .PP -See also mainWidget(), exec(), and tquit(). +See also mainWidget(), exec(), and quit(). .PP Examples: .)l chart/main.cpp, helpsystem/main.cpp, life/main.cpp, network/ftpclient/main.cpp, opengl/main.cpp, t1/main.cpp, and t4/main.cpp. diff --git a/doc/man/man3/qcdestyle.3qt b/doc/man/man3/qcdestyle.3qt index 5835be2b3..9f5b92f8a 100644 --- a/doc/man/man3/qcdestyle.3qt +++ b/doc/man/man3/qcdestyle.3qt @@ -25,7 +25,7 @@ Inherits QMotifStyle. .SH DESCRIPTION The QCDEStyle class provides a CDE look and feel. .PP -This style provides a slightly improved Motif look similar to some versions of the Common Desktop Environment (CDE). The main differences are thinner frames and more modern radio buttons and checkboxes. Together with a dark background and a bright text/foreground color, the style looks tquite attractive (at least for Motif fans). +This style provides a slightly improved Motif look similar to some versions of the Common Desktop Environment (CDE). The main differences are thinner frames and more modern radio buttons and checkboxes. Together with a dark background and a bright text/foreground color, the style looks quite attractive (at least for Motif fans). .PP Note that the functions provided by QCDEStyle are reimplementations of QStyle functions; see QStyle for their documentation. .PP diff --git a/doc/man/man3/qcloseevent.3qt b/doc/man/man3/qcloseevent.3qt index 03ed11727..1032d13a3 100644 --- a/doc/man/man3/qcloseevent.3qt +++ b/doc/man/man3/qcloseevent.3qt @@ -49,7 +49,7 @@ If the last top-level window is closed, the QApplication::lastWindowClosed() sig .PP The isAccepted() function returns TRUE if the event's receiver has agreed to close the widget; call accept() to agree to close the widget and call ignore() if the receiver of this event does not want the widget to be closed. .PP -See also QWidget::close(), QWidget::hide(), QObject::destroyed(), QApplication::setMainWidget(), QApplication::lastWindowClosed(), QApplication::exec(), QApplication::tquit(), and Event Classes. +See also QWidget::close(), QWidget::hide(), QObject::destroyed(), QApplication::setMainWidget(), QApplication::lastWindowClosed(), QApplication::exec(), QApplication::quit(), and Event Classes. .SH MEMBER FUNCTION DOCUMENTATION .SH "QCloseEvent::QCloseEvent ()" Constructs a close event object with the accept parameter flag set to FALSE. diff --git a/doc/man/man3/qcolorgroup.3qt b/doc/man/man3/qcolorgroup.3qt index 0bde55063..de2e82f85 100644 --- a/doc/man/man3/qcolorgroup.3qt +++ b/doc/man/man3/qcolorgroup.3qt @@ -185,7 +185,7 @@ Finally, there is a special role for text that needs to be drawn where Text or F .TP \fCQColorGroup::NColorRoles\fR - Internal. .PP -Note that text colors can be used for things other than just words; text colors are \fIusually\fR used for text, but it's tquite common to use the text color roles for lines, icons, etc. +Note that text colors can be used for things other than just words; text colors are \fIusually\fR used for text, but it's quite common to use the text color roles for lines, icons, etc. .PP This image shows most of the color roles in use: <center> .ce 1 diff --git a/doc/man/man3/qdialog.3qt b/doc/man/man3/qdialog.3qt index 31f3911bd..7d23207f6 100644 --- a/doc/man/man3/qdialog.3qt +++ b/doc/man/man3/qdialog.3qt @@ -213,7 +213,7 @@ Closes the dialog and sets its result code to \fIr\fR. If this dialog is shown w .PP As with QWidget::close(), done() deletes the dialog if the WDestructiveClose flag is set. If the dialog is the application's main widget, the application terminates. If the dialog is the last window closed, the QApplication::lastWindowClosed() signal is emitted. .PP -See also accept(), reject(), QApplication::mainWidget(), and QApplication::tquit(). +See also accept(), reject(), QApplication::mainWidget(), and QApplication::quit(). .SH "int QDialog::exec ()\fC [slot]\fR" Shows the dialog as a modal dialog, blocking until the user closes it. The function returns a DialogCode result. .PP diff --git a/doc/man/man3/qeventloop.3qt b/doc/man/man3/qeventloop.3qt index a72100022..cf7a0fee4 100644 --- a/doc/man/man3/qeventloop.3qt +++ b/doc/man/man3/qeventloop.3qt @@ -147,7 +147,7 @@ Generally speaking, no user interaction can take place before calling exec(). As .PP To make your application perform idle processing, i.e. executing a special function whenever there are no pending events, use a QTimer with 0 timeout. More advanced idle processing schemes can be achieved using processEvents(). .PP -See also QApplication::tquit(), exit(), and processEvents(). +See also QApplication::quit(), exit(), and processEvents(). .SH "void QEventLoop::exit ( int retcode = 0 )\fC [virtual]\fR" Tells the event loop to exit with a return code. .PP @@ -157,7 +157,7 @@ By convention, a \fIretcode\fR of 0 means success, and any non-zero value indica .PP Note that unlike the C library function of the same name, this function \fIdoes\fR return to the caller -- it is event processing that stops. .PP -See also QApplication::tquit() and exec(). +See also QApplication::quit() and exec(). .SH "void QEventLoop::exitLoop ()\fC [virtual]\fR" This function exits from a recursive call to the main event loop. Do not call it unless you really know what you are doing. .SH "bool QEventLoop::hasPendingEvents () const\fC [virtual]\fR" diff --git a/doc/man/man3/qfont.3qt b/doc/man/man3/qfont.3qt index 962ba6128..d3c413ff6 100644 --- a/doc/man/man3/qfont.3qt +++ b/doc/man/man3/qfont.3qt @@ -392,7 +392,7 @@ South and Southeast Asian scripts (left to right with few historical exceptions) .TP \fCQFont::Thai\fR - is used to write Thai and other Southeast Asian languages. .TP -\fCQFont::Lao\fR - is a language and script tquite similar to Thai. +\fCQFont::Lao\fR - is a language and script quite similar to Thai. .TP \fCQFont::Tibetan\fR - is the script used to write Tibetan in several countries like Tibet, the bordering Indian regions and Nepal. It is also used in the Buddist philosophy and liturgy of the Mongolian cultural area. .TP diff --git a/doc/man/man3/qglcontext.3qt b/doc/man/man3/qglcontext.3qt index d90d57f61..13ff2fbcd 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 tquite 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 retquirements 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 tquite 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 retquirements on visual selection. .PP See also chooseContext(). .SH "bool QGLContext::create ( const QGLContext * shareContext = 0 )\fC [virtual]\fR" diff --git a/doc/man/man3/qhebrewcodec.3qt b/doc/man/man3/qhebrewcodec.3qt index 63a39d67d..e07d93ef3 100644 --- a/doc/man/man3/qhebrewcodec.3qt +++ b/doc/man/man3/qhebrewcodec.3qt @@ -33,7 +33,7 @@ In contrast to this, Unicode defines characters to be in logical order (the orde .PP Transformation from Unicode to visual Hebrew (8859-8) is done using the bidi algorithm in Qt, and will produce correct results, so long as the codec is given the text a whole paragraph at a time. Places where newlines are supposed to go can be indicated by a newline character ('\\n'). Note that these newline characters change the reordering behaviour of the algorithm, since the bidi reordering only takes place within one line of text, whereas line breaks are determined in visual order. .PP -Visually ordered Hebrew is still used tquite often in some places, mainly in email communication (since most email programs still don't understand logically ordered Hebrew) and on web pages. The use on web pages is rapidly decreasing, due to the availability of browsers that correctly support logically ordered Hebrew. +Visually ordered Hebrew is still used quite often in some places, mainly in email communication (since most email programs still don't understand logically ordered Hebrew) and on web pages. The use on web pages is rapidly decreasing, due to the availability of browsers that correctly support logically ordered Hebrew. .PP This codec has the name "iso8859-8". If you don't want any bidi reordering to happen during conversion, use the "iso8859-8-i" codec, which assumes logical order for the 8-bit string. .PP diff --git a/doc/man/man3/qlistbox.3qt b/doc/man/man3/qlistbox.3qt index 9d842ca17..7608d6270 100644 --- a/doc/man/man3/qlistbox.3qt +++ b/doc/man/man3/qlistbox.3qt @@ -441,7 +441,7 @@ If the user does not select anything, no signals are emitted and currentItem() r .PP A list box has WheelFocus as a default focusPolicy(), i.e. it can get keyboard focus by tabbing, clicking and through the use of the mouse wheel. .PP -New items can be inserted using insertItem(), insertStrList() or insertStringList(). inSort() is obsolete because this method is tquite inefficient. It's preferable to insert the items normally and call sort() afterwards, or to insert a sorted QStringList(). +New items can be inserted using insertItem(), insertStrList() or insertStringList(). inSort() is obsolete because this method is quite inefficient. It's preferable to insert the items normally and call sort() afterwards, or to insert a sorted QStringList(). .PP By default, vertical and horizontal scroll bars are added and removed as necessary. setHScrollBarMode() and setVScrollBarMode() can be used to change this policy. .PP @@ -634,7 +634,7 @@ See also currentChanged(), selected(), currentItem, and selectionChanged(). .SH "int QListBox::inSort ( const QListBoxItem * lbi )" \fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code. .PP -Using this method is tquite inefficient. We suggest to use insertItem() for inserting and sort() afterwards. +Using this method is quite inefficient. We suggest to use insertItem() for inserting and sort() afterwards. .PP Inserts \fIlbi\fR at its sorted position in the list box and returns the position. .PP @@ -646,7 +646,7 @@ See also insertItem() and sort(). .PP This is an overloaded member function, provided for convenience. It behaves essentially like the above function. .PP -Using this method is tquite inefficient. We suggest to use insertItem() for inserting and sort() afterwards. +Using this method is quite inefficient. We suggest to use insertItem() for inserting and sort() afterwards. .PP Inserts a new item of \fItext\fR at its sorted position in the list box and returns the position. .PP diff --git a/doc/man/man3/qmenubar.3qt b/doc/man/man3/qmenubar.3qt index e1308a6ba..f31b2d3ef 100644 --- a/doc/man/man3/qmenubar.3qt +++ b/doc/man/man3/qmenubar.3qt @@ -218,7 +218,7 @@ Qt/Mac also provides a menubar merging feature to make QMenuBar conform more clo .PP <center>.nf .TS -l - l. String matches Placement Notes about.* Application Menu | About If this entry is not found no About item will appear in the Application Menu config, options, setup, settings or preferences Application Menu | Preferences If this entry is not found the Settings item will be disabled tquit or exit Application Menu | Quit If this entry is not found a default Quit item will be created to call +l - l. String matches Placement Notes about.* Application Menu | About If this entry is not found no About item will appear in the Application Menu config, options, setup, settings or preferences Application Menu | Preferences If this entry is not found the Settings item will be disabled quit or exit Application Menu | Quit If this entry is not found a default Quit item will be created to call .TE .fi </center> @@ -282,7 +282,7 @@ A menu item is usually either a text string or a pixmap, both with an optional i .PP Some insertItem() members take a popup menu as an additional argument. Use this to insert submenus into existing menus or pulldown menus into a menu bar. .PP -The number of insert functions may look confusing, but they are actually tquite simple to use. +The number of insert functions may look confusing, but they are actually quite simple to use. .PP This default version inserts a menu item with the text \fItext\fR, the accelerator key \fIaccel\fR, an id and an optional index and connects it to the slot \fImember\fR in the object \fIreceiver\fR. .PP diff --git a/doc/man/man3/qmenudata.3qt b/doc/man/man3/qmenudata.3qt index 9199b1b06..306f5d4fb 100644 --- a/doc/man/man3/qmenudata.3qt +++ b/doc/man/man3/qmenudata.3qt @@ -322,7 +322,7 @@ A menu item is usually either a text string or a pixmap, both with an optional i .PP Some insertItem() members take a popup menu as an additional argument. Use this to insert submenus into existing menus or pulldown menus into a menu bar. .PP -The number of insert functions may look confusing, but they are actually tquite simple to use. +The number of insert functions may look confusing, but they are actually quite simple to use. .PP This default version inserts a menu item with the text \fItext\fR, the accelerator key \fIaccel\fR, an id and an optional index and connects it to the slot \fImember\fR in the object \fIreceiver\fR. .PP @@ -607,7 +607,7 @@ Example: .br fileMenu->insertItem( "Quit", 69 ); // add "Quit" item .br - fileMenu->setAccel( CTRL + ALT + Key_Delete, 69 ); // add Alt+Del to tquit + fileMenu->setAccel( CTRL + ALT + Key_Delete, 69 ); // add Alt+Del to quit .br mainMenu->insertItem( "File", fileMenu ); // add the file menu .br diff --git a/doc/man/man3/qnetworkprotocol.3qt b/doc/man/man3/qnetworkprotocol.3qt index 6760cc76f..3d1a15197 100644 --- a/doc/man/man3/qnetworkprotocol.3qt +++ b/doc/man/man3/qnetworkprotocol.3qt @@ -226,7 +226,7 @@ Returns TRUE if auto-deleting is enabled; otherwise returns FALSE. .PP See also QNetworkProtocol::setAutoDelete(). .SH "bool QNetworkProtocol::checkConnection ( QNetworkOperation * op )\fC [virtual protected]\fR" -For processing operations the network protocol base class calls this method tquite often. This should be reimplemented by new network protocols. It should return TRUE if the connection is OK (open); otherwise it should return FALSE. If the connection is not open the protocol should open it. +For processing operations the network protocol base class calls this method quite often. This should be reimplemented by new network protocols. It should return TRUE if the connection is OK (open); otherwise it should return FALSE. If the connection is not open the protocol should open it. .PP If the connection can't be opened (e.g. because you already tried but the host couldn't be found), set the state of \fIop\fR to QNetworkProtocol::StFailed and emit the finished() signal with this QNetworkOperation as argument. .PP diff --git a/doc/man/man3/qobject.3qt b/doc/man/man3/qobject.3qt index 8dcb7c829..e1d365474 100644 --- a/doc/man/man3/qobject.3qt +++ b/doc/man/man3/qobject.3qt @@ -779,7 +779,7 @@ Searches the children and optionally grandchildren of this object, and returns a .PP If \fIregexpMatch\fR is TRUE (the default), \fIobjName\fR is a regular expression that the objects's names must match. The syntax is that of a QRegExp. If \fIregexpMatch\fR is FALSE, \fIobjName\fR is a string and object names must match it exactly. .PP -Note that \fIinheritsClass\fR uses single inheritance from QObject, the way inherits() does. According to inherits(), QMenuBar inherits QWidget but not QMenuData. This does not tquite match reality, but is the best that can be done on the wide variety of compilers Qt supports. +Note that \fIinheritsClass\fR uses single inheritance from QObject, the way inherits() does. According to inherits(), QMenuBar inherits QWidget but not QMenuData. This does not quite match reality, but is the best that can be done on the wide variety of compilers Qt supports. .PP Finally, if \fIrecursiveSearch\fR is TRUE (the default), queryList() searches \fIn\fRth-generation as well as first-generation children. .PP diff --git a/doc/man/man3/qpopupmenu.3qt b/doc/man/man3/qpopupmenu.3qt index a20cd7c5c..10d3fff5f 100644 --- a/doc/man/man3/qpopupmenu.3qt +++ b/doc/man/man3/qpopupmenu.3qt @@ -410,7 +410,7 @@ A menu item is usually either a text string or a pixmap, both with an optional i .PP Some insertItem() members take a popup menu as an additional argument. Use this to insert submenus into existing menus or pulldown menus into a menu bar. .PP -The number of insert functions may look confusing, but they are actually tquite simple to use. +The number of insert functions may look confusing, but they are actually quite simple to use. .PP This default version inserts a menu item with the text \fItext\fR, the accelerator key \fIaccel\fR, an id and an optional index and connects it to the slot \fImember\fR in the object \fIreceiver\fR. .PP @@ -703,7 +703,7 @@ Example: .br fileMenu->insertItem( "Quit", 69 ); // add "Quit" item .br - fileMenu->setAccel( CTRL + ALT + Key_Delete, 69 ); // add Alt+Del to tquit + fileMenu->setAccel( CTRL + ALT + Key_Delete, 69 ); // add Alt+Del to quit .br mainMenu->insertItem( "File", fileMenu ); // add the file menu .br diff --git a/doc/man/man3/qptrqueue.3qt b/doc/man/man3/qptrqueue.3qt index 66fc1a6ac..592506e03 100644 --- a/doc/man/man3/qptrqueue.3qt +++ b/doc/man/man3/qptrqueue.3qt @@ -148,7 +148,7 @@ See also head(), isEmpty(), and dequeue(). .SH "void QPtrQueue::setAutoDelete ( bool enable )" Sets the queue to auto-delete its contents if \fIenable\fR is TRUE and not to delete them if \fIenable\fR is FALSE. .PP -If auto-deleting is turned on, all the items in a queue are deleted when the queue itself is deleted. This can be tquite convenient if the queue has the only pointer to the items. +If auto-deleting is turned on, all the items in a queue are deleted when the queue itself is deleted. This can be quite convenient if the queue has the only pointer to the items. .PP The default setting is FALSE, for safety. If you turn it on, be careful about copying the queue: you might find yourself with two queues deleting the same items. .PP diff --git a/doc/man/man3/qscrollview.3qt b/doc/man/man3/qscrollview.3qt index 611a870ed..617341f1a 100644 --- a/doc/man/man3/qscrollview.3qt +++ b/doc/man/man3/qscrollview.3qt @@ -309,7 +309,7 @@ Inherited by QCanvasView, QTable, QGridView, QIconView, QListBox, QListView, and .SH DESCRIPTION The QScrollView widget provides a scrolling area with on-demand scroll bars. .PP -The QScrollView is a large canvas - potentially larger than the coordinate system normally supported by the underlying window system. This is important because it is tquite easy to go beyond these limitations (e.g. many web pages are more than 32000 pixels high). Additionally, the QScrollView can have QWidgets positioned on it that scroll around with the drawn content. These sub-widgets can also have positions outside the normal coordinate range (but they are still limited in size). +The QScrollView is a large canvas - potentially larger than the coordinate system normally supported by the underlying window system. This is important because it is quite easy to go beyond these limitations (e.g. many web pages are more than 32000 pixels high). Additionally, the QScrollView can have QWidgets positioned on it that scroll around with the drawn content. These sub-widgets can also have positions outside the normal coordinate range (but they are still limited in size). .PP To provide content for the widget, inherit from QScrollView, reimplement drawContents() and use resizeContents() to set the size of the viewed area. Use addChild() and moveChild() to position widgets on the view. .PP @@ -757,7 +757,7 @@ Sets the resize policy. See the "resizePolicy" property for details. .SH "void QScrollView::setStaticBackground ( bool y )" Sets the scrollview to have a static background if \fIy\fR is TRUE, or a scrolling background if \fIy\fR is FALSE. By default, the background is scrolling. .PP -Be aware that this mode is tquite slow, as a full repaint of the visible area has to be triggered on every contents move. +Be aware that this mode is quite slow, as a full repaint of the visible area has to be triggered on every contents move. .PP See also hasStaticBackground(). .SH "void QScrollView::setVBarGeometry ( QScrollBar & vbar, int x, int y, int w, int h )\fC [virtual protected]\fR" diff --git a/doc/man/man3/qsessionmanager.3qt b/doc/man/man3/qsessionmanager.3qt index db170b1f4..5a7eb0e79 100644 --- a/doc/man/man3/qsessionmanager.3qt +++ b/doc/man/man3/qsessionmanager.3qt @@ -90,7 +90,7 @@ This enum type defines the circumstances under which this application wants to b .TP \fCQSessionManager::RestartIfRunning\fR - if the application is still running when the session is shut down, it wants to be restarted at the start of the next session. .TP -\fCQSessionManager::RestartAnyway\fR - the application wants to be started at the start of the next session, no matter what. (This is useful for utilities that run just after startup and then tquit.) +\fCQSessionManager::RestartAnyway\fR - the application wants to be started at the start of the next session, no matter what. (This is useful for utilities that run just after startup and then quit.) .TP \fCQSessionManager::RestartImmediately\fR - the application wants to be started immediately whenever it is not running. .TP diff --git a/doc/man/man3/qsocket.3qt b/doc/man/man3/qsocket.3qt index 7dd6273bd..650721783 100644 --- a/doc/man/man3/qsocket.3qt +++ b/doc/man/man3/qsocket.3qt @@ -165,7 +165,7 @@ The signals error(), connected(), readyRead() and connectionClosed() inform you .PP There are several access functions for the socket: state() returns whether the object is idle, is doing a DNS lookup, is connecting, has an operational connection, etc. address() and port() return the IP address and port used for the connection. The peerAddress() and peerPort() functions return the IP address and port used by the peer, and peerName() returns the name of the peer (normally the name that was passed to connectToHost()). socketDevice() returns a pointer to the QSocketDevice used for this socket. .PP -QSocket inherits QIODevice, and reimplements some functions. In general, you can treat it as a QIODevice for writing, and mostly also for reading. The match isn't perfect, since the QIODevice API is designed for devices that are controlled by the same machine, and an asynchronous peer-to-peer network connection isn't tquite like that. For example, there is nothing that matches QIODevice::size() exactly. The documentation for open(), close(), flush(), size(), at(), atEnd(), readBlock(), writeBlock(), getch(), putch(), ungetch() and readLine() describes the differences in detail. +QSocket inherits QIODevice, and reimplements some functions. In general, you can treat it as a QIODevice for writing, and mostly also for reading. The match isn't perfect, since the QIODevice API is designed for devices that are controlled by the same machine, and an asynchronous peer-to-peer network connection isn't quite like that. For example, there is nothing that matches QIODevice::size() exactly. The documentation for open(), close(), flush(), size(), at(), atEnd(), readBlock(), writeBlock(), getch(), putch(), ungetch() and readLine() describes the differences in detail. .PP \fBWarning:\fR QSocket is not suitable for use in threads. If you need to uses sockets in threads use the lower-level QSocketDevice class. .PP diff --git a/doc/man/man3/qsocketdevice.3qt b/doc/man/man3/qsocketdevice.3qt index 7814ce3ac..d18322eed 100644 --- a/doc/man/man3/qsocketdevice.3qt +++ b/doc/man/man3/qsocketdevice.3qt @@ -244,7 +244,7 @@ Returns TRUE if this is a valid socket; otherwise returns FALSE. .PP See also socket(). .SH "bool QSocketDevice::listen ( int backlog )\fC [virtual]\fR" -Specifies how many pending connections a server socket can have. Returns TRUE if the operation was successful; otherwise returns FALSE. A \fIbacklog\fR value of 50 is tquite common. +Specifies how many pending connections a server socket can have. Returns TRUE if the operation was successful; otherwise returns FALSE. A \fIbacklog\fR value of 50 is quite common. .PP The listen() call only applies to sockets where type() is Stream, i.e. not to Datagram sockets. listen() must not be called before bind() or after accept(). .PP diff --git a/doc/man/man3/qtimer.3qt b/doc/man/man3/qtimer.3qt index 50cb9a851..b4b492bca 100644 --- a/doc/man/man3/qtimer.3qt +++ b/doc/man/man3/qtimer.3qt @@ -130,7 +130,7 @@ Example: .br QApplication a( argc, argv ); .br - QTimer::singleShot( 10*60*1000, &a, SLOT(tquit()) ); + QTimer::singleShot( 10*60*1000, &a, SLOT(quit()) ); .br ... // create and show your widgets .br diff --git a/doc/man/man3/qtooltip.3qt b/doc/man/man3/qtooltip.3qt index 2511f9ed4..30be67b73 100644 --- a/doc/man/man3/qtooltip.3qt +++ b/doc/man/man3/qtooltip.3qt @@ -125,7 +125,7 @@ To add a tip to a widget, call the \fIstatic\fR function QToolTip::add() with th .PP .nf .br - QToolTip::add( tquitButton, "Leave the application" ); + QToolTip::add( quitButton, "Leave the application" ); .br .fi .PP @@ -133,7 +133,7 @@ This is the simplest and most common use of QToolTip. The tip will be deleted au .PP .nf .br - QToolTip::remove( tquitButton ); + QToolTip::remove( quitButton ); .br .fi .PP @@ -141,7 +141,7 @@ You can also display another text (typically in a status bar), courtesy of QTool .PP .nf .br - QToolTip::add( tquitButton, "Leave the application", grp, + QToolTip::add( quitButton, "Leave the application", grp, .br "Leave the application, prompting to save if necessary" ); .br diff --git a/doc/man/man3/qwidget.3qt b/doc/man/man3/qwidget.3qt index 007f06f2f..2da51743d 100644 --- a/doc/man/man3/qwidget.3qt +++ b/doc/man/man3/qwidget.3qt @@ -1028,7 +1028,7 @@ Every widget's constructor accepts two or three standard arguments: <ol type=1> .IP 1 \fCQWidget *parent = 0\fR is the parent of the new widget. If it is 0 (the default), the new widget will be a top-level window. If not, it will be a child of \fIparent\fR, and be constrained by \fIparent\fR's geometry (unless you specify WType_TopLevel as widget flag). .IP 2 -\fCconst char *name = 0\fR is the widget name of the new widget. You can access it using name(). The widget name is little used by programmers but is tquite useful with GUI builders such as \fIQt Designer\fR (you can name a widget in \fIQt Designer\fR, and connect() to it using the name in your code). The dumpObjectTree() debugging function also uses it. +\fCconst char *name = 0\fR is the widget name of the new widget. You can access it using name(). The widget name is little used by programmers but is quite useful with GUI builders such as \fIQt Designer\fR (you can name a widget in \fIQt Designer\fR, and connect() to it using the name in your code). The dumpObjectTree() debugging function also uses it. .IP 3 \fCWFlags f = 0\fR (where available) sets the widget flags; the default is suitable for almost all widgets, but to get, for example, a top-level widget without a window system frame, you must use special flags. .PP @@ -1049,7 +1049,7 @@ mousePressEvent() - called when a mouse button is pressed. There are six mouse-r mouseReleaseEvent() - called when a mouse button is released. A widget receives mouse release events when it has received the corresponding mouse press event. This means that if the user presses the mouse inside \fIyour\fR widget, then drags the mouse to somewhere else, then releases, \fIyour\fR widget receives the release event. There is one exception: if a popup menu appears while the mouse button is held down, this popup immediately steals the mouse events. .IP .TP -mouseDoubleClickEvent() - not tquite as obvious as it might seem. If the user double-clicks, the widget receives a mouse press event (perhaps a mouse move event or two if they don't hold the mouse tquite steady), a mouse release event and finally this event. It is \fInot possible\fR to distinguish a click from a double click until you've seen whether the second click arrives. (This is one reason why most GUI books recommend that double clicks be an extension of single clicks, rather than trigger a different action.) +mouseDoubleClickEvent() - not quite as obvious as it might seem. If the user double-clicks, the widget receives a mouse press event (perhaps a mouse move event or two if they don't hold the mouse quite steady), a mouse release event and finally this event. It is \fInot possible\fR to distinguish a click from a double click until you've seen whether the second click arrives. (This is one reason why most GUI books recommend that double clicks be an extension of single clicks, rather than trigger a different action.) .IP .PP If your widget only contains child widgets, you probably do not need to implement any event handlers. If you want to detect a mouse click in a child widget call the child's hasMouse() function inside the parent widget's mousePressEvent(). @@ -1247,7 +1247,7 @@ The QApplication::lastWindowClosed() signal is emitted when the last visible top .PP Note that closing the QApplication::mainWidget() terminates the application. .PP -See also closeEvent(), QCloseEvent, hide(), QApplication::tquit(), QApplication::setMainWidget(), and QApplication::lastWindowClosed(). +See also closeEvent(), QCloseEvent, hide(), QApplication::quit(), QApplication::setMainWidget(), and QApplication::lastWindowClosed(). .SH "void QWidget::closeEvent ( QCloseEvent * e )\fC [virtual protected]\fR" This event handler, for event \fIe\fR, can be reimplemented in a subclass to receive widget close events. .PP diff --git a/doc/man/man3/qxmlsimplereader.3qt b/doc/man/man3/qxmlsimplereader.3qt index 2c4f5253e..5b1d6d721 100644 --- a/doc/man/man3/qxmlsimplereader.3qt +++ b/doc/man/man3/qxmlsimplereader.3qt @@ -77,7 +77,7 @@ Continues incremental parsing; this function reads the input from the QXmlInputS .PP Returns FALSE if a parsing error occurs; otherwise returns TRUE. .PP -If the input source returns an empty string for the function QXmlInputSource::data(), then this means that the end of the XML file has been reached; this is tquite important, especially if you want to use the reader to parse more than one XML file. +If the input source returns an empty string for the function QXmlInputSource::data(), then this means that the end of the XML file has been reached; this is quite important, especially if you want to use the reader to parse more than one XML file. .PP The case of the end of the XML file being reached without having finished parsing is not considered to be an error: you can continue parsing at a later stage by calling this function again when there is more data available to parse. .PP diff --git a/doc/misc.doc b/doc/misc.doc index bae26156f..cb7c84b3d 100644 --- a/doc/misc.doc +++ b/doc/misc.doc @@ -978,7 +978,7 @@ OS 8 addendum.\endlink <b>The Microsoft Windows User Experience</b>, ISBN 1-55615-679-0, is Microsoft's look and feel Bible. Indispensable for everyone who -has customers that worship Microsoft, and it's tquite good, too. +has customers that worship Microsoft, and it's quite good, too. \link http://www.amazon.com/exec/obidos/ASIN/0735605661/trolltech/t (Read more or buy it.)\endlink @@ -1073,7 +1073,7 @@ Furthermore, a toolkit cannot simply place windows on the screen. All Qt can do is to send certain hints to the window manager. The window manager, a separate process, may either obey, ignore or misunderstand them. Due to the partially unclear Inter-Client Communication -Conventions Manual (ICCCM), window placement is handled tquite +Conventions Manual (ICCCM), window placement is handled quite differently in existing window managers. X11 provides no standard or easy way to get the frame geometry once diff --git a/doc/network.doc b/doc/network.doc index 7b36384d4..5b2eaec50 100644 --- a/doc/network.doc +++ b/doc/network.doc @@ -84,7 +84,7 @@ digital camera using a serial connection. \section1 Working Network Protocol independently with QUrlOperator and QNetworkOperation -It is tquite easy to just use existing network protocol implementations +It is quite easy to just use existing network protocol implementations and operate on URLs. For example, downloading a file from an FTP server to the local filesystem can be done with following code: diff --git a/doc/qptrqueue.doc b/doc/qptrqueue.doc index 40a1f52d2..f67f6d21f 100644 --- a/doc/qptrqueue.doc +++ b/doc/qptrqueue.doc @@ -195,7 +195,7 @@ and not to delete them if \a enable is FALSE. If auto-deleting is turned on, all the items in a queue are - deleted when the queue itself is deleted. This can be tquite + deleted when the queue itself is deleted. This can be quite convenient if the queue has the only pointer to the items. The default setting is FALSE, for safety. If you turn it on, be diff --git a/doc/signalsandslots.doc b/doc/signalsandslots.doc index 3762f337b..fc46ce9e1 100644 --- a/doc/signalsandslots.doc +++ b/doc/signalsandslots.doc @@ -273,10 +273,10 @@ may connect signals to. This is intended for very tightly connected classes, where even subclasses aren't trusted to get the connections right. -You can also define slots to be virtual, which we have found tquite +You can also define slots to be virtual, which we have found quite useful in practice. -The signals and slots mechanism is efficient, but not tquite as fast as +The signals and slots mechanism is efficient, but not quite as fast as "real" callbacks. Signals and slots are slightly slower because of the increased flexibility they provide, although the difference for real applications is insignificant. In general, emitting a signal that is diff --git a/doc/tutorial.doc b/doc/tutorial.doc index 2220e8764..ad56d271e 100644 --- a/doc/tutorial.doc +++ b/doc/tutorial.doc @@ -223,7 +223,7 @@ You're now ready for \link tutorial1-02.html Chapter 2.\endlink \img t2.png Screenshot of tutorial two Having created a window in \link tutorial1-01.html Chapter 1, \endlink we will -now go on to make the application tquit properly when the user tells it to. +now go on to make the application quit properly when the user tells it to. We will also use a font that is more exciting than the default one. @@ -272,9 +272,9 @@ both \c signals (to send messages) and \c slots (to receive messages). All widgets are Qt objects. They inherit QWidget which in turn inherits QObject. -Here, the \e clicked() signal of \e tquit is connected to the \e -tquit() slot of \e a, so that when the button is clicked, the -application tquits. +Here, the \e clicked() signal of \e quit is connected to the \e +quit() slot of \e a, so that when the button is clicked, the +application quits. The \link signalsandslots.html Signals and Slots\endlink documentation describes this topic in detail. @@ -292,7 +292,7 @@ makefile and build the application.) Try to resize the window. Press the button. Oops! That connect() would seem to make some difference. -Are there any other signals in QPushButton you can connect to tquit? +Are there any other signals in QPushButton you can connect to quit? Hint: The QPushButton inherits most of its behavior from QButton. You're now ready for \link tutorial1-03.html Chapter 3.\endlink @@ -334,7 +334,7 @@ space according to each child's \l QWidget::sizePolicy(). We set its width to 200 pixels and the height to 120 pixels. -\printline tquit +\printline quit A child is born. @@ -431,11 +431,11 @@ we will show how a widget can respond to resize event from the user. \printuntil setFont Here we create and set up a child widget of this widget (the new widget's -parent is \c this) which has the widget name "tquit". The widget +parent is \c this) which has the widget name "quit". The widget name has nothing to do with the button text; it just happens to be similar in this case. -Note that \c tquit is a local variable in the constructor. MyWidget +Note that \c quit is a local variable in the constructor. MyWidget does not keep track of it, but Qt does, and will by default delete it when MyWidget is deleted. This is why MyWidget doesn't need a destructor. (On the other hand, there is no harm in deleting a child @@ -570,7 +570,7 @@ You can also change the slider's range. Perhaps it would have been better to use \l QSpinBox than a slider? -Try to make the application tquit when the LCD number overflows. +Try to make the application quit when the LCD number overflows. You're now ready for \link tutorial1-06.html Chapter 6.\endlink @@ -1376,7 +1376,7 @@ the drawing a little bit. \skipto ::setForce \printuntil } -The implementation of setForce() is tquite similar to that of +The implementation of setForce() is quite similar to that of setAngle(). The only difference is that because we don't show the force value, we don't need to repaint the widget. @@ -2592,13 +2592,13 @@ destroyed when that widget is destroyed. QAccel is \e not a widget and has no visible effect on its parent. We define two shortcut keys. We want the slot fire() to be called -when the user presses Enter, and we want the application to tquit when +when the user presses Enter, and we want the application to quit when key Ctrl+Q is pressed. Because Enter is sometimes Return and there are even keyboards with \e both keys, we make both Enter and Return invoke fire(). \printline connectItem -\printline tquit +\printline quit And then we set up Ctrl+Q to do the same thing as Alt+Q. Some people are more used to Ctrl+Q (and anyway it shows how do do it). diff --git a/doc/tutorial2.doc b/doc/tutorial2.doc index 9d68e51fd..91099788b 100644 --- a/doc/tutorial2.doc +++ b/doc/tutorial2.doc @@ -385,7 +385,7 @@ canvas; but events (e.g. mouse clicks) take place on the canvas view. \endtable Each action is represented by a private slot, e.g. \c fileNew(), \c -optionsSetData(), etc. We also have tquite a number of private +optionsSetData(), etc. We also have quite a number of private functions and data members; we'll look at all these as we go through the implementation. @@ -673,7 +673,7 @@ item id. \printline \printline -When the user tquits we give them the opportunity to save any unsaved +When the user quits we give them the opportunity to save any unsaved data (okToClear()) then save their options, e.g. window size and position, chart type, etc., before terminating. @@ -1064,7 +1064,7 @@ We set a caption for the dialog and resize it. \skipto tableButtonBox \printline -The layout of the form is tquite simple. The buttons will be grouped +The layout of the form is quite simple. The buttons will be grouped together in a horizontal layout and the table and the button layout will be grouped together vertically using the tableButtonBox layout. diff --git a/doc/xml.doc b/doc/xml.doc index b5f63c5c2..30f4d1209 100644 --- a/doc/xml.doc +++ b/doc/xml.doc @@ -589,7 +589,7 @@ prefix \e fnord that is declared in the \e book:author element. Clearly the \e fnord namespace has the same namespace URI as the default namespace. So why didn't we simply use the default namespace -we'd already declared? The answer is tquite complex: +we'd already declared? The answer is quite complex: \list \i attributes without a prefix don't belong to any XML namespace at all, not even to the default namespace; |