~oif-team/ubuntu/natty/qt4-x11/xi2.1

<td width="1">  </td><td class="postheader" valign="center"><a href="index.html"><font color="#004faf">Home</font></a> · <a href="classes.html"><font color="#004faf">All Classes</font></a> · <a href="mainclasses.html"><font color="#004faf">Main Classes</font></a> · <a href="annotated.html"><font color="#004faf">Annotated</font></a> · <a href="groups.html"><font color="#004faf">Grouped Classes</font></a> · <a href="functions.html"><font color="#004faf">Functions</font></a></td>

<td align="right" valign="top" width="230"><img src="images/trolltech-logo.png" align="right" width="203" height="32" border="0" /></td></tr></table><h1 align="center">Calculator Builder</h1>

<p>Files:</p>

<ul>

<li><a href="designer-calculatorbuilder-calculatorform-cpp.html">designer/calculatorbuilder/calculatorform.cpp</a></li>

<li><a href="designer-calculatorbuilder-calculatorform-h.html">designer/calculatorbuilder/calculatorform.h</a></li>

<li><a href="designer-calculatorbuilder-main-cpp.html">designer/calculatorbuilder/main.cpp</a></li>

<li><a href="designer-calculatorbuilder-calculatorbuilder-qrc.html">designer/calculatorbuilder/calculatorbuilder.qrc</a></li>

</ul>

<p>The Calculator Builder example shows how to create a user interface from a <i>Qt Designer</i> form at runtime, using the <tt>FormBuilder</tt> class.</p>

<p>We use the form created in the <a href="designer-calculatorform.html">Calculator Form</a> example to show that the same user interface can be generated when the application is executed or defined when the application is built.</p>

<h2>Preparation</h2>

<p>The <a href="designer-calculatorform.html">Calculator Form</a> example defines a user interface that we can use without modification. In this example, we use a <a href="resources.html">resource file</a> to contain the <tt>calculatorform.ui</tt> file created in the previous example, but it could be stored on disk instead.</p>

<p>To generate a form at run time, we need to link the example against the <tt>libQtDesigner</tt> library. The project file we use contains all the necessary information to do this:</p>

<pre>  CONFIG += designer

HEADERS = calculatorform.h

SOURCES = calculatorform.cpp \

main.cpp

RESOURCES = calculatorbuilder.qrc</pre>

<p>All the other necessary files are declared as usual.</p>

<h2>CalculatorForm Class Definition</h2>

<p>The <tt>CalculatorForm</tt> class defines the widget used to host the form's user interface:</p>

<pre>  class CalculatorForm : public QWidget

{

Q_OBJECT

public:

CalculatorForm(QWidget *parent = 0);

private slots:

void on_inputSpinBox1_valueChanged(int value);

void on_inputSpinBox2_valueChanged(int value);

private:

QSpinBox *ui_inputSpinBox1;

QSpinBox *ui_inputSpinBox2;

QLabel *ui_outputWidget;

};</pre>

<p>Note that we do not need to include a header file to describe the user interface. We only define two public slots, using the auto-connection naming convention required by <tt>uic</tt>, and declare private variables that we will use to access widgets provided by the form after they are constructed.</p>

<h2>CalculatorForm Class Implementation</h2>

<p>We will need to use the <tt>FormBuilder</tt> class that is provided by the <tt>libQtDesigner</tt> library, so we first ensure that we include the header file for it:</p>

<p>The constructor uses a <tt>FormBuilder</tt> object to construct the user interface that we retrieve, via a <a href="qfile.html">QFile</a> object, from the example's resources:</p>

<pre>  CalculatorForm::CalculatorForm(QWidget *parent)

: QWidget(parent)

{

QFormBuilder builder;

QFile file(":/forms/calculatorform.ui");

file.open(QFile::ReadOnly);

QWidget *formWidget = builder.load(&file, this);

file.close();</pre>

<p>By including the user interface in the example's resources, we ensure that it will be present when the example is run. The <tt>builder.load()</tt> function takes the user interface description contained in the file and constructs the form widget as a child widget of the <tt>CalculatorForm</tt>.</p>

<p>We are interested in three widgets in the generated user interface: two spin boxes and a label. For convenience, we retrieve pointers to these widgets from the widget that was constructed by the <tt>FormBuilder</tt>, and we record them for later use. The <tt>qFindChild()</tt> template function allows us to query widgets in order to find named child widgets.</p>

<p>The widgets created by the <tt>FormBuilder</tt> need to be connected to the specially-named slots in the <tt>CalculatorForm</tt> object. We use Qt's meta-object system to enable these connections:</p>

<p>The form widget is added to a layout, and the window title is set:</p>

<pre>  QVBoxLayout *layout = new QVBoxLayout;

layout->addWidget(formWidget);

setLayout(layout);

setWindowTitle(tr("Calculator Builder"));

}</pre>

<p>The two slots that modify widgets provided by the form are defined in a similar way to those in the <a href="designer-calculatorform.html">Calculator Form</a> example, except that we read the values from the spin boxes and write the result to the output widget via the pointers we recorded in the constructor:</p>

<pre>  void CalculatorForm::on_inputSpinBox1_valueChanged(int value)

{

ui_outputWidget->setText(QString::number(value + ui_inputSpinBox2->value()));

}

void CalculatorForm::on_inputSpinBox2_valueChanged(int value)

{

ui_outputWidget->setText(QString::number(value + ui_inputSpinBox1->value()));

}</pre>

<p>The advantage of this approach is that we can replace the form when the application is run, but we can still manipulate the widgets it contains as long as they are given appropriate names.</p>

<td width="40%" align="center"><a href="trademarks.html">Trademarks</a></td>

100

101

</tr></table></div></address></body>

102

</html>

Older »