Viadeo Twitter Google Bookmarks ! Facebook Digg MySpace Yahoo MyWeb Blinklist Netvouz Reddit Simpy StumbleUpon Bookmarks Windows Live Favorites 
Logo Documentation Qt ·  Page d'accueil  ·  Toutes les classes  ·  Toutes les fonctions  ·  Vues d'ensemble  · 

Completer Example


The Completer example shows how to provide string-completion facilities for an input widget based on data provided by a model.

This example uses a custom item model, DirModel, and a QCompleter object. QCompleter is a class that provides completions based on an item model. The type of model, the completion mode, and the case sensitivity can be selected using combo boxes.

The Resource File

The Completer example requires a resource file in order to store the countries.txt and words.txt. The resource file contains the following code:

 <!DOCTYPE RCC><RCC version="1.0">
 <qresource prefix="/">

DirModel Class Definition

The DirModel class is a subclass of QDirModel, which provides a data model for the local filesystem.

 class DirModel : public QDirModel
     DirModel(QObject *parent = 0);
     QVariant data(const QModelIndex &index, int role = Qt::DisplayRole) const;

This class only has a constructor and a data() function as it is only created to enable data() to return the entire file path for the display role, unlike QDirModel's data() function that only returns the folder and not the drive label. This is further explained in DirModel's implementation.

DirModel Class Implementation

The constructor for the DirModel class is used to pass parent to QDirModel.

 DirModel::DirModel(QObject *parent)
     : QDirModel(parent)

As mentioned earlier, the data() function is reimplemented in order to get it to return the entire file parth for the display role. For example, with a QDirModel, you will see "Program Files" in the view. However, with DirModel, you will see "C:\Program Files".

 QVariant DirModel::data(const QModelIndex &index, int role) const
     if (role == Qt::DisplayRole && index.column() == 0) {
         QString path  = QDir::toNativeSeparators(filePath(index));
         if (path.endsWith(QDir::separator()))
         return path;

     return QDirModel::data(index, role);

The screenshots below illustrate this difference:

The Qt::EditRole, which QCompleter uses to look for matches, is left unchanged.

MainWindow Class Definition

The MainWindow class is a subclass of QMainWindow and implements five private slots - about(), changeCase(), changeMode(), changeModel(), and changeMaxVisible().

 class MainWindow : public QMainWindow

     MainWindow(QWidget *parent = 0);

 private slots:
     void about();
     void changeCase(int);
     void changeMode(int);
     void changeModel();
     void changeMaxVisible(int);

Within the MainWindow class, we have two private functions: createMenu() and modelFromFile(). We also declare the private widgets needed - three QComboBox objects, a QCheckBox, a QCompleter, a QLabel, and a QLineEdit.

     void createMenu();
     QAbstractItemModel *modelFromFile(const QString& fileName);

     QComboBox *caseCombo;
     QComboBox *modeCombo;
     QComboBox *modelCombo;
     QSpinBox *maxVisibleSpinBox;
     QCheckBox *wrapCheckBox;
     QCompleter *completer;
     QLabel *contentsLabel;
     QLineEdit *lineEdit;

MainWindow Class Implementation

The constructor of MainWindow constructs a MainWindow with a parent widget and initializes the private members. The createMenu() function is then invoked.

We set up three QComboBox objects, modelComb, modeCombo and caseCombo. By default, the modelCombo is set to QDirModel, the modeCombo is set to "Filtered Popup" and the caseCombo is set to "Case Insensitive".

 MainWindow::MainWindow(QWidget *parent)
     : QMainWindow(parent), completer(0), lineEdit(0)

     QWidget *centralWidget = new QWidget;

     QLabel *modelLabel = new QLabel;

     modelCombo = new QComboBox;
     modelCombo->addItem(tr("QDirModel that shows full path"));
     modelCombo->addItem(tr("Country list"));
     modelCombo->addItem(tr("Word list"));

     QLabel *modeLabel = new QLabel;
     modeLabel->setText(tr("Completion Mode"));
     modeCombo = new QComboBox;
     modeCombo->addItem(tr("Filtered Popup"));
     modeCombo->addItem(tr("Unfiltered Popup"));

     QLabel *caseLabel = new QLabel;
     caseLabel->setText(tr("Case Sensitivity"));
     caseCombo = new QComboBox;
     caseCombo->addItem(tr("Case Insensitive"));
     caseCombo->addItem(tr("Case Sensitive"));

The maxVisibleSpinBox is created and determines the number of visible item in the completer

The wrapCheckBox is then set up. This checkBox determines if the completer's setWrapAround() property is enabled or disabled.

     QLabel *maxVisibleLabel = new QLabel;
     maxVisibleLabel->setText(tr("Max Visible Items"));
     maxVisibleSpinBox = new QSpinBox;

     wrapCheckBox = new QCheckBox;
     wrapCheckBox->setText(tr("Wrap around completions"));

We instantiate contentsLabel and set its size policy to fixed. The combo boxes' activated() signals are then connected to their respective slots.

     contentsLabel = new QLabel;
     contentsLabel->setSizePolicy(QSizePolicy::Fixed, QSizePolicy::Fixed);

     connect(modelCombo, SIGNAL(activated(int)), this, SLOT(changeModel()));
     connect(modeCombo, SIGNAL(activated(int)), this, SLOT(changeMode(int)));
     connect(caseCombo, SIGNAL(activated(int)), this, SLOT(changeCase(int)));
     connect(maxVisibleSpinBox, SIGNAL(valueChanged(int)), this, SLOT(changeMaxVisible(int)));

The lineEdit is set up and then we arrange all the widgets using a QGridLayout. The changeModel() function is called, to initialize the completer.

     lineEdit = new QLineEdit;

     QGridLayout *layout = new QGridLayout;
     layout->addWidget(modelLabel, 0, 0); layout->addWidget(modelCombo, 0, 1);
     layout->addWidget(modeLabel, 1, 0);  layout->addWidget(modeCombo, 1, 1);
     layout->addWidget(caseLabel, 2, 0);  layout->addWidget(caseCombo, 2, 1);
     layout->addWidget(maxVisibleLabel, 3, 0); layout->addWidget(maxVisibleSpinBox, 3, 1);
     layout->addWidget(wrapCheckBox, 4, 0);
     layout->addWidget(contentsLabel, 5, 0, 1, 2);
     layout->addWidget(lineEdit, 6, 0, 1, 2);



The createMenu() function is used to instantiate the QAction objects needed to fill the fileMenu and helpMenu. The actions' triggered() signals are connected to their respective slots.

 void MainWindow::createMenu()
     QAction *exitAction = new QAction(tr("Exit"), this);
     QAction *aboutAct = new QAction(tr("About"), this);
     QAction *aboutQtAct = new QAction(tr("About Qt"), this);

     connect(exitAction, SIGNAL(triggered()), qApp, SLOT(quit()));
     connect(aboutAct, SIGNAL(triggered()), this, SLOT(about()));
     connect(aboutQtAct, SIGNAL(triggered()), qApp, SLOT(aboutQt()));

     QMenu* fileMenu = menuBar()->addMenu(tr("File"));

     QMenu* helpMenu = menuBar()->addMenu(tr("About"));

The modelFromFile() function accepts the fileName of a file and processes it depending on its contents.

We first validate the file to ensure that it can be opened in QFile::ReadOnly mode. If this is unsuccessful, the function returns an empty QStringListModel.

 QAbstractItemModel *MainWindow::modelFromFile(const QString& fileName)
     QFile file(fileName);
     if (!
         return new QStringListModel(completer);

The mouse cursor is then overriden with Qt::WaitCursor before we fill a QStringList object, words, with the contents of file. Once this is done, we restore the mouse cursor.

 #ifndef QT_NO_CURSOR
     QStringList words;

     while (!file.atEnd()) {
         QByteArray line = file.readLine();
         if (!line.isEmpty())
             words << line.trimmed();

 #ifndef QT_NO_CURSOR

As mentioned earlier, the resources file contains two files - countries.txt and words.txt. If the file read is words.txt, we return a QStringListModel with words as its QStringList and completer as its parent.

     if (!fileName.contains(QLatin1String("countries.txt")))
         return new QStringListModel(words, completer);

If the file read is countries.txt, then we require a QStandardItemModel with words.count() rows, 2 columns, and completer as its parent.

     QStandardItemModel *m = new QStandardItemModel(words.count(), 2, completer);

A standard line in countries.txt is:

Norway NO

Hence, to populate the QStandardItemModel object, m, we have to split the country name and its symbol. Once this is done, we return m.

     for (int i = 0; i < words.count(); ++i) {
         QModelIndex countryIdx = m->index(i, 0);
         QModelIndex symbolIdx = m->index(i, 1);
         QString country = words[i].mid(0, words[i].length() - 2).trimmed();
         QString symbol = words[i].right(2);
         m->setData(countryIdx, country);
         m->setData(symbolIdx, symbol);

     return m;

The changeMode() function sets the completer's mode, depending on the value of index.

 void MainWindow::changeMode(int index)
     QCompleter::CompletionMode mode;
     if (index == 0)
         mode = QCompleter::InlineCompletion;
     else if (index == 1)
         mode = QCompleter::PopupCompletion;
         mode = QCompleter::UnfilteredPopupCompletion;


The changeModel() function changes the item model used based on the model selected by the user.

A switch statement is used to change the item model based on the index of modelCombo. If case is 0, we use an unsorted QDirModel, providing us with a file path excluding the drive label.

 void MainWindow::changeModel()
     delete completer;
     completer = new QCompleter(this);

     switch (modelCombo->currentIndex()) {
     case 0:
         { // Unsorted QDirModel
             QDirModel *dirModel = new QDirModel(completer);
             contentsLabel->setText(tr("Enter file path"));

Note that we create the model with completer as the parent as this allows us to replace the model with a new model. The completer will ensure that the old one is deleted the moment a new model is assigned to it.

If case is 1, we use the DirModel we defined earlier, resulting in full paths for the files.

     case 1:
         { // DirModel that shows full paths
             DirModel *dirModel = new DirModel(completer);
             contentsLabel->setText(tr("Enter file path"));

When case is 2, we attempt to complete names of countries. This requires a QTreeView object, treeView. The country names are extracted from countries.txt and set the popup used to display completions to treeView.

     case 2:
         { // Country List
             QTreeView *treeView = new QTreeView;
             treeView->header()->setResizeMode(0, QHeaderView::Stretch);
             treeView->header()->setResizeMode(1, QHeaderView::ResizeToContents);
             contentsLabel->setText(tr("Enter name of your country"));

The screenshot below shows the Completer with the country list model.

If case is 3, we attempt to complete words. This is done using a QStringListModel that contains data extracted from words.txt. The model is sorted case insensitively.

The screenshot below shows the Completer with the word list model.

Once the model type is selected, we call the changeMode() function and the changeCase() function and set the wrap option accordingly. The wrapCheckBox's clicked() signal is connected to the completer's setWrapAround() slot.

     case 3:
         { // Word list
             contentsLabel->setText(tr("Enter a word"));

     connect(wrapCheckBox, SIGNAL(clicked(bool)), completer, SLOT(setWrapAround(bool)));

The changeMaxVisible() update the maximum number of visible items in the completer.

 void MainWindow::changeMaxVisible(int max)

The about() function provides a brief description about the example.

 void MainWindow::about()
     QMessageBox::about(this, tr("About"), tr("This example demonstrates the "
         "different features of the QCompleter class."));

main() Function

The main() function instantiates QApplication and MainWindow and invokes the show() function.

 int main(int argc, char *argv[])

     QApplication app(argc, argv);
     MainWindow window;;
     return app.exec();


Best Of

Actualités les plus lues

  1. Microsoft ouvre aux autres compilateurs C++ AMP, la spécification pour la conception d'applications parallèles C++ utilisant le GPU 22
  2. Les développeurs ignorent-ils trop les failles découvertes dans leur code ? Prenez-vous en compte les remarques des autres ? 17
  3. RIM : « 13 % des développeurs ont gagné plus de 100 000 $ sur l'AppWord », Qt et open-source au menu du BlackBerry DevCon Europe 0
  4. « Quelque chose ne va vraiment pas avec les développeurs "modernes" », un développeur à "l'ancienne" critique la multiplication des bibliothèques 12
  5. BlackBerry 10 : premières images du prochain OS de RIM qui devrait intégrer des widgets et des tuiles inspirées de Windows Phone 0
  6. Adieu qmake, bienvenue qbs : Qt Building Suite, un outil déclaratif et extensible pour la compilation de projets Qt 17
  7. Quelles nouveautés de C++11 Visual C++ doit-il rapidement intégrer ? Donnez-nous votre avis 10
Page suivante

Le Qt Developer Network au hasard


La création de colonnes dans une ListView en QML

Le Qt Developer Network est un réseau de développeurs Qt anglophone, où ils peuvent partager leur expérience sur le framework. Lire l'article.



Liens utiles


  • Vous souhaitez rejoindre la rédaction ou proposer un tutoriel, une traduction, une question... ? Postez dans le forum Contribuez ou contactez-nous par MP ou par email (voir en bas de page).

Qt dans le magazine

Cette page est une traduction d'une page de la documentation de Qt, écrite par Nokia Corporation and/or its subsidiary(-ies). Les éventuels problèmes résultant d'une mauvaise traduction ne sont pas imputables à Nokia. Qt 4.6
Copyright © 2012 Developpez LLC. Tous droits réservés Developpez LLC. Aucune reproduction, même partielle, ne peut être faite de ce site et de l'ensemble de son contenu : textes, documents et images sans l'autorisation expresse de Developpez LLC. Sinon, vous encourez selon la loi jusqu'à 3 ans de prison et jusqu'à 300 000 E de dommages et intérêts. Cette page est déposée à la SACD.
Vous avez déniché une erreur ? Un bug ? Une redirection cassée ? Ou tout autre problème, quel qu'il soit ? Ou bien vous désirez participer à ce projet de traduction ? N'hésitez pas à nous contacter ou par MP !

Hébergement Web