Home > Articles > Programming > User Interface (UI)

Like this article? We recommend

Like this article? We recommend

Writing Dialogs in Code

Writing a dialog entirely in code using Qt is much easier than in most other toolkits. Qt provides three layout manager classes that take care of positioning widgets (called controls on some platforms) on screen, as shown in Figure 1:

  • QHBoxLayout (left)

  • QVBoxLayout (center)

  • QGridLayout (right)

The layout managers can be nested to create complex dialogs.

Figure 1Figure 1 QHBoxLayout, QVBoxLayout, and QGridLayout classes.

Dialogs that use the layout managers automatically enjoy the following benefits (see Figure 2):

  • The dialogs are user-resizable and have a sensible minimum size.

  • They look good no matter what font, platform, theme, or direction of writing (left-to-right or right-to-left) is applied.

  • They adapt smoothly when the text changes—for example, if the application is translated to another language.

Layout managers relieve the programmer of the tedious task of specifying hard-coded coordinates for the dialog's widgets. Although Qt also offers absolute positioning as an alternative, very few developers use that approach.

Figure xxx   Figure 2bx
     
Figure 2c Figure 2d

Figure 2 A layout-managed Find dialog with different platforms, languages, and directions of writing.

In addition to layout managers, one reason why it's easy to develop Qt dialogs is Qt's "signals and slots" mechanism. Widgets on the screen emit signals in response to user actions. For example, QPushButton, the Qt class for button widgets, emits a clicked() signal whenever the user clicks the button. Similarly, QSpinBox has a valueChanged(int) signal that is emitted when the user changes the value held by the spin box, either by typing a new value or by clicking the tiny arrows on the widget. Signals can be connected to member functions of other objects. Member functions that signals can connect to are called slots.

Here's a simple example of a signal-to-slot connection:

int main(int argc, char *argv[])
{
  QApplication app(argc, argv);
  QPushButton *quitButton = new QPushButton("Quit", 0);

  connect(quitButton, SIGNAL(clicked()),
      &app, SLOT(quit()));
  ...
}

In this example, we connect the Quit button's clicked() signal to the QApplication object's quit() slot.

NOTE

QApplication is a class that provides global-like functionality. Every Qt application must create one instance of that class, typically in main().

To see how this all works in practice, let's implement the Find dialog depicted earlier in Figure 2. This involves subclassing QDialog and writing the code for a few functions. We'll start by reviewing the header file:

#ifndef FINDDIALOG_H
#define FINDDIALOG_H

#include <qbuttongroup.h>
#include <qcheckbox.h>
#include <qdialog.h>
#include <qlabel.h>
#include <qlineedit.h>
#include <qpushbutton.h>
#include <qradiobutton.h>

class FindDialog : public QDialog
{
  Q_OBJECT
public:
  FindDialog(QWidget *parent = 0);

signals:
  void findNext(const QString &text, bool caseSensitive,
         bool forward);

private slots:
  void findNextButtonClicked();

private:
  QLabel *label;
  QLineEdit *lineEdit;
  QCheckBox *caseCheckBox;
  QButtonGroup *buttonGroup;
  QRadioButton *upRadioButton;
  QRadioButton *downRadioButton;
  QPushButton *findNextButton;
  QPushButton *closeButton;
};

#endif

This header file looks like a standard C++ header file, with a few exceptions:

  • The class definition contains the Q_OBJECT macro at the very top. This macro is necessary for all classes that provide their own signals and slots.

  • The signals keyword is used to specify that findNext() is a signal.

  • The slots keyword is used to specify that findNextButtonClicked() is a slot.

The signals and slots keywords are converted into standard C++ by the C++ preprocessor. They serve as markers for Qt's meta-object compiler (moc) tool, which gathers meta-information about Qt classes and generates glue code necessary for the "signals and slots" mechanism.

Let's review the implementation file, starting with the constructor:

#include <qlayout.h>

#include "finddialog.h"

FindDialog::FindDialog(QWidget *parent)
  : QDialog(parent)
{
  setCaption(tr("Find"));

  label = new QLabel(tr("Find &what:"), this);
  lineEdit = new QLineEdit(this);
  label->setBuddy(lineEdit);

  buttonGroup = new QButtonGroup(tr("Direction"), this);
  buttonGroup->setColumns(2);

  upRadioButton = new QRadioButton(tr("&Up"), buttonGroup);
  downRadioButton = new QRadioButton(tr("&Down"), buttonGroup);
  downRadioButton->setChecked(true);

  caseCheckBox = new QCheckBox(tr("&Case sensitive"), this);

  findNextButton = new QPushButton(tr("&Find Next"), this);
  closeButton = new QPushButton(tr("Close"), this);

  // more follows

The FindDialog constructor takes a QWidget * parameter that specifies the dialog's parent window. If a parent is specified (that is, parent isn't a null pointer), the dialog automatically centers itself on top of that window and shares that window's taskbar entry; otherwise, the dialog acts as an independent window inside the application.

At the top of the constructor, we call setCaption() to set the window title to Find. The tr() function that surrounds the "Find" string marks the string as translatable.

Then we create a label widget showing the text Find what:, an empty line editor widget, a button group with the heading text Direction, two radio buttons (Up and Down), a check box with the text Case sensitive, and two push buttons (Find Next and Close).

Most of the widgets are created with this as the last argument, to specify that they're children of the FindDialog object. Child widgets are shown onscreen inside their parent. The two radio buttons are created with buttonGroup, not this, as the parent, because they're displayed inside the button group's area. Qt allows widgets to be nested to any depth.

Let's continue reviewing the constructor code. Now that we've created the child widgets, we need to create layout managers to manage them:

QHBoxLayout *topLeftLayout = new QHBoxLayout;
topLeftLayout->addWidget(label);
topLeftLayout->addWidget(lineEdit);

QVBoxLayout *leftLayout = new QVBoxLayout;
leftLayout->addLayout(topLeftLayout);
leftLayout->addWidget(buttonGroup);
leftLayout->addWidget(caseCheckBox);

QVBoxLayout *rightLayout = new QVBoxLayout;
rightLayout->addWidget(findNextButton);
rightLayout->addWidget(closeButton);
rightLayout->addStretch(1);

QHBoxLayout *mainLayout = new QHBoxLayout(this);
mainLayout->setMargin(11);
mainLayout->setSpacing(6);
mainLayout->addLayout(leftLayout);
mainLayout->addLayout(rightLayout);

// more follows

We create four layout manager objects, as shown in Figure 3:

  • The first one, topLeftLayout, is a horizontal layout that contains the Find what label and the line edit side-by-side.

  • leftLayout is a vertical layout that contains topLeftLayout, buttonGroup, and caseCheckBox.

  • Similarly, rightLayout is a vertical layout that contains the two push buttons and a stretch (represented by a blue "spring" in Figure 3). The stretch fills empty space in a layout, and ensures that the Find Next and Close buttons stay aligned at the top. Finally, mainLayout is a horizontal layout that contains leftLayout and rightLayout side-by-side.

Figure 3Figure 3 The Find dialog's layout.

Notice that we need no layout for the two radio buttons inside the QButtonGroup. Thanks to the setColumns(2) call on the QButtonGroup earlier in the constructor, QButtonGroup will automatically arrange its child widgets as a grid.

Once we're done with the layouts, the only thing that's left of the constructor code is the following signal/slot connections:

  connect(findNextButton, SIGNAL(clicked()),
      this, SLOT(findNextButtonClicked()));
  connect(closeButton, SIGNAL(clicked()),
      this, SLOT(close()));
}

We connect the Find Next button's clicked() signal to the Find dialog's findNextButtonClicked() slot. This ensures that findNextButtonClicked() will be called whenever the user clicks the button, or presses the Spacebar when the button has the focus.

Then we connect the Close button to the Find dialog's close() slot. This slot is provided by QDialog, FindDialog's base class.

Apart from the constructor, the only function we need to implement is the findNextButtonClicked() slot:

void FindDialog::findNextButtonClicked()
{
  emit findNext(lineEdit->text(), caseCheckBox->isOn(),
         upRadioButton->isOn());
}

When the user clicks Find Next, we emit the dialog's findNext() signal with three arguments:

  • Text typed by the user

  • Boolean value indicating whether the search is case sensitive

  • Boolean value indicating whether the search should go up or down

The emit keyword is Qt-specific; like the signals and slots keywords, it's converted to standard C++ by the C++ preprocessor.

This completes the FindDialog class. The result is a fully functional Find dialog that can be used from a Qt application. The application simply needs to connect the findNext() signal to a slot that takes three parameters of the same types as the signal, and implement the actual search functionality in that slot.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020