@ -305,14 +305,14 @@ But what about the <methodname>show()</methodname> method? Now, you see that lik
This shows you a lot of other widgets that are inherited by <classname>QPushButton</classname>,
which we'll use later to explain the signal/slot mechanism. Anyway, the <methodname>show()</methodname>
method is not listed, therefore, it must be a method that is provided by inheritance as well. The class
that <classname>QButton</classname> inherits is <classname>QWidget</classname>. Just follow the link
again, and you will see a whole bunch of methods that the QWidget class provides; including
that <classname>QButton</classname> inherits is <classname>TQWidget</classname>. Just follow the link
again, and you will see a whole bunch of methods that the TQWidget class provides; including
the <methodname>show()</methodname> method. Now we understand what was done in the sample with the button:
<orderedlist>
<listitem><para>Create an instance of <classname>QPushButton</classname>, use the second constructor to set the button text</para></listitem>
<listitem><para>Resize the widget to its contents</para></listitem>
<listitem><para>Set the widget as the main widget of the <classname>QApplication</classname> instance a</para></listitem>
<listitem><para>Tell the widget to display itself on the screen by calling <methodname>show()</methodname>, an inherited method from <classname>QWidget</classname></para></listitem>
<listitem><para>Tell the widget to display itself on the screen by calling <methodname>show()</methodname>, an inherited method from <classname>TQWidget</classname></para></listitem>
</orderedlist>
</para>
<para>
@ -327,7 +327,7 @@ user events.
<note><para>
For already advanced users: The button has no parent declared in the constructor, therefore it
is a top-level widget alone and runs in a local event loop which doesn't need to wait for the main
event loop. See the QWidget class documentation and The TDE Library Reference Guide</para>
event loop. See the TQWidget class documentation and The TDE Library Reference Guide</para>
</note>
</sect3>
@ -352,7 +352,7 @@ provide methods that detect actions and methods that do something as a reaction
The Window system therefore sends all interaction events to the according application. The
<classname>QApplication</classname> then sends them to the active window as a <classname>QEvent</classname>
and the widgets themselves have to decide what to do with them. A widget receives the event and processes
<methodname>QWidget::event(QEvent*)</methodname>, which then decides which event has been executed
<methodname>TQWidget::event(QEvent*)</methodname>, which then decides which event has been executed
and how to react; <methodname>event()</methodname> is therefore the main event handler. Then,
the <methodname>event()</methodname> method passes the event to so-called event filters
that determine what happened and what to do with the event. If no filter signs responsible for the
@ -405,9 +405,9 @@ Window events containing the widget</para>
</para>
<para>
Note that all event functions are virtual and protected; therefore you can re-implement the events
that you need in your own widgets and specify how your widget has to react. <classname>QWidget</classname>
that you need in your own widgets and specify how your widget has to react. <classname>TQWidget</classname>
also contains some other virtual methods that can be useful in your programs; anyway, it is sufficient
to know about <classname>QWidget</classname> very well.
to know about <classname>TQWidget</classname> very well.
</para>
</sect2>
<sect2 id="c1s2s4">
@ -423,7 +423,7 @@ some things about this mechanism:
<itemizedlist>
<listitem><para>
the class declaration of a class using signals/slots has to contain the TQ_OBJECT macro at the beginning
(without a semicolon); and have to be derved from the <classname>QObject</classname> class
(without a semicolon); and have to be derved from the <classname>TQObject</classname> class
</para></listitem>
<listitem><para>
a signal can be emitted by the keyword emit, e.g. emit signal(parameters); from within any member function
@ -445,9 +445,9 @@ implementation (which is not necessary to know). The output files of moc are co
</itemizedlist>
</para>
<para>
Another way to use signals without deriving from <classname>QObject</classname> is to use the
Another way to use signals without deriving from <classname>TQObject</classname> is to use the
<classname>QSignal</classname> class- see the reference documentation for more information and example
usage. In the following, we assume you're deriving from <classname>QObject</classname>.
usage. In the following, we assume you're deriving from <classname>TQObject</classname>.
</para>
<para>
This way, your class is able to send signals anywhere and to provide slots that signals can connect
@ -457,7 +457,7 @@ as normal methods during implementation.
</para>
<para>
Now, to connect a signal to a slot, you have to use the <methodname>connect()</methodname> methods that
are provided by <classname>QObject</classname> or, where available, special methods that objects provide
are provided by <classname>TQObject</classname> or, where available, special methods that objects provide
<string>Insert the base class which your new class will be derived from. If you have checked 'Generate QWidget child class' the new class will be derived from QWidget. If no base class is named, the new class will not have a parent class. You can also use template classes here (like BaseClass<int, int>)</string>
<string>Insert the base class which your new class will be derived from. If you have checked 'Generate TQWidget child class' the new class will be derived from TQWidget. If no base class is named, the new class will not have a parent class. You can also use template classes here (like BaseClass<int, int>)</string>
