diff options
Diffstat (limited to 'doc/tutorial.doc')
| -rw-r--r-- | doc/tutorial.doc | 24 |
1 files changed, 12 insertions, 12 deletions
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). |