summaryrefslogtreecommitdiffstats
path: root/doc/tutorial2.doc
diff options
context:
space:
mode:
authorTimothy Pearson <kb9vqf@pearsoncomputing.net>2015-03-05 20:59:01 -0600
committerTimothy Pearson <kb9vqf@pearsoncomputing.net>2015-03-05 20:59:01 -0600
commitdfb87398c72e9248aa709ae212e6ab7f2209003d (patch)
tree52422e7b6774fcc503d7c701cb2c77fa016386e8 /doc/tutorial2.doc
parent891a448afad4ab1f09bfb0cfee71652975bd7687 (diff)
downloadtqt3-dfb87398c72e9248aa709ae212e6ab7f2209003d.tar.gz
tqt3-dfb87398c72e9248aa709ae212e6ab7f2209003d.zip
Automated update from Qt3
Diffstat (limited to 'doc/tutorial2.doc')
-rw-r--r--doc/tutorial2.doc18
1 files changed, 9 insertions, 9 deletions
diff --git a/doc/tutorial2.doc b/doc/tutorial2.doc
index 4291ffe62..4066338e0 100644
--- a/doc/tutorial2.doc
+++ b/doc/tutorial2.doc
@@ -20,8 +20,8 @@
\title Tutorial #2
-This tutorial presents a more "real world" example of Qt programming
-than the first tutorial. It introduces many aspects of Qt programming,
+This tutorial presents a more "real world" example of TQt programming
+than the first tutorial. It introduces many aspects of TQt programming,
including the creation of menus (including a recent files list),
toolbars and dialogs, loading and saving user settings, etc.
@@ -134,15 +134,15 @@ of chart has a (relative) position stored in the \c m_propoints array.
\printto class
Although the \c Element class is a purely internal data class, it
-\c{#include}s four Qt classes. Qt is often perceived as a purely GUI
+\c{#include}s four TQt classes. TQt is often perceived as a purely GUI
toolkit, but it provides many non-GUI classes to support most aspects
of application programming. We use \c ntqcolor.h so that we can hold the
paint color and text color in the \c Element class. The use of \c
-ntqnamespace.h is slightly obscure. Most Qt classes are derived from the
+ntqnamespace.h is slightly obscure. Most TQt classes are derived from the
\link ntqt.html Qt\endlink superclass which contains various
enumerations. The \c Element class does not derive from \link ntqt.html
Qt\endlink, so we need to include \c ntqnamespace.h to have access to
-the Qt enum names. An alternative approach would have been to have
+the TQt enum names. An alternative approach would have been to have
made \c Element a \link ntqt.html Qt\endlink subclass. We include \c
ntqstring.h to make use of Qt's Unicode strings. As a convenience we
will \c typedef a vector container for \c{Element}s, which is why we
@@ -307,7 +307,7 @@ which our users will create, edit and visualise their data sets.
\row
\i For more information on Qt's data streaming facilities see \link
datastreamformat.html QDataStream Operators' Formats\endlink, and see
-the source code for any of the Qt classes mentioned that are similar
+the source code for any of the TQt classes mentioned that are similar
to what you want to store.
\endtable
@@ -422,7 +422,7 @@ outside of the constructor.
\table
\row
\i Most user actions are suitable as both menu items and as toolbar
-buttons. Qt allows us to create a single QAction which can be added to
+buttons. TQt allows us to create a single QAction which can be added to
both a menu and a toolbar. This approach ensures that menu items and
toolbar buttons stay in sync and saves duplicating code.
\endtable
@@ -642,7 +642,7 @@ menu item an id which is the same as the index position of the item in
the string list, and connect each menu item to the fileOpenRecent()
slot. The old file menu items are deleted at the same time by going
through each possible recent file menu item id. This works because the
-other file menu items had ids created by Qt (all of which are \< 0);
+other file menu items had ids created by TQt (all of which are \< 0);
whereas the menu items we're creating all have ids \>= 0.
\quotefile chart/chartform.cpp
@@ -1313,7 +1313,7 @@ The user may opt to display their own labels as they are or to add the
values at the end of each label, either as-is or as percentages.
We create a frame to present the radio buttons in and create a layout
-for them. We create a button group (so that Qt will take care of
+for them. We create a button group (so that TQt will take care of
handling the exclusive radio button behaviour automatically). Next we
create the radio buttons, making "No" the default.