How does QComboBox uses/calls QCompleter ?

[d_stranz]

In general, you do not derive from QCompleter to create a custom completer. You instead derive from QAbstractItemModel and set that on your QCompleter as the model it uses to find completions for a partial phrase. The combo box and completer handle the interaction between them and you don't need to care how that works, just what your model does when asked.

If your completions can be simplified to a list of strings, then you can use the version of QCompleter that accepts a QStringList argument, and internally QCompleter will insert that into a QStringListModel.

If your completions are more complex, then you may need to implement your own model. In this case, you have almost total control over how QCompleter searches your model for completions. For example, if you have a table model, you can tell it which column to use for completions, which model role to use to retrieve candidates, and so forth.

The QCompleter example in the docs will help. There is a more advanced example as well. In both cases, note that they use a plain old QCompleter and customize it using models.

[boo9]

I examined above examples but I dont think they answer my question,

Let me be more specific
I need a completer that will complete on many words, e.g, user types in "aa bb" into QEditBox edit, and completer should complete a list where each item on the complete list matches (not just begins with) "aa" and "bb".
that is, the completion for "aa bb" filter from a list {aaa_a, aaa_bbb, aabb, bbb_a}, should be {aaa_bbb, aabb}.

I managed to do that but I needed to sublcass both qeditbox and qcompleter.
Is there any way to accomplish that w/o subclassing QEditBox ?

[boo9]

I subclassed QCompleter

class mySearchFilterComplter : public QCompleter
{
    Q_OBJECT
public:
    mySearchFilterComplter(QObject * parent) :  QCompleter(parent), m_model() 
   { 
      setModel(&m_model); 
    }
public slots:
    void update(const QString & text)
    {
    QDebug() << "update";
    m_model.setStringList(QStringList() << "one" << "two" << "three");
    complete();
    popup()->setCurrentIndex(completionModel()->index(0, 0));
     }
private:
    QStringListModel m_model;
};

class mySearchFilterComplter : public QCompleter
{
    Q_OBJECT
public:
    mySearchFilterComplter(QObject * parent) :  QCompleter(parent), m_model() 
   { 
      setModel(&m_model); 
    }
public slots:
    void update(const QString & text)
    {
    QDebug() << "update";
    m_model.setStringList(QStringList() << "one" << "two" << "three");
    complete();
    popup()->setCurrentIndex(completionModel()->index(0, 0));
     }
private:
    QStringListModel m_model;
};

To copy to clipboard, switch view to plain text mode 

then connected combo box editTextChanged() signal to my completer update() slot.

mySearchFilterComplter * cc = new mySearchFilterComplter(this);
ui->comboBox->setComplter(cc)
connect(ui->comboBox, SIGNAL(editTextChanged(QString)), cc, SLOT(update(QString)));

mySearchFilterComplter * cc = new mySearchFilterComplter(this);
ui->comboBox->setComplter(cc)
connect(ui->comboBox, SIGNAL(editTextChanged(QString)), cc, SLOT(update(QString)));

To copy to clipboard, switch view to plain text mode 

The update() gets called with each keystroke in combo box line edit but there is no popup ?
What am I doing wrong ?
I have similar code with subsclassed QLineEdit and subclassed QCompleter and the completer popup works. (but the completer::update() is called from keyPressedEvent() though)

class MyCompleter : public QCompleter
{
    Q_OBJECT;
public:
    inline MyCompleter(const QStringList& words, QObject * parent) :
            QCompleter(parent), m_model()
    {
        setModel(&m_model);
    }
    inline void update(QString word)
    {
        m_model.setStringList(QStringList() << "one" << "two" << "three");
        complete();
    }
private:
    QStringList m_list;
    QStringListModel m_model;
};
 
class MyLineEdit : public QLineEdit
{
    Q_OBJECT;
public:
    MyLineEdit(QWidget *parent = 0);
    ~MyLineEdit();
    void setCompleter(MyCompleter *c);
    MyCompleter *completer() const;
protected:
    void keyPressEvent(QKeyEvent *e);
private slots:
    void insertCompletion(const QString &completion);
private:
    MyCompleter *c;
};
 
MyLineEdit::MyLineEdit(QWidget *parent)
    : QLineEdit(parent), c(0)
{
}
 
MyLineEdit::~MyLineEdit()
{
}
 
void MyLineEdit::setCompleter(MyCompleter *completer)
{
    if (c)
        QObject::disconnect(c, 0, this, 0);
 
    c = completer;
 
    if (!c)
        return;
 
    c->setWidget(this);
    connect(completer, SIGNAL(activated(const QString&)), this, SLOT(insertCompletion(const QString&)));
}
 
MyCompleter *MyLineEdit::completer() const
{
    return c;
}
 
void MyLineEdit::insertCompletion(const QString& completion)
{
    setText(completion);
    selectAll();
}
void MyLineEdit::keyPressEvent(QKeyEvent *e)
{
    if (c && c->popup()->isVisible())
    {
        // The following keys are forwarded by the completer to the widget
        switch (e->key())
        {
        case Qt::Key_Enter:
        case Qt::Key_Return:
        case Qt::Key_Escape:
        case Qt::Key_Tab:
        case Qt::Key_Backtab:
            e->ignore();
            return; // Let the completer do default behavior
        }
    }
 
    bool isShortcut = (e->modifiers() & Qt::ControlModifier) && e->key() == Qt::Key_E;
    if (!isShortcut)
        QLineEdit::keyPressEvent(e); // Don't send the shortcut (CTRL-E) to the text edit.
 
    if (!c)
        return;
 
    bool ctrlOrShift = e->modifiers() & (Qt::ControlModifier | Qt::ShiftModifier);
    if (!isShortcut && !ctrlOrShift && e->modifiers() != Qt::NoModifier)
    {
        c->popup()->hide();
        return;
    }
 
    c->update(text());
    c->popup()->setCurrentIndex(c->completionModel()->index(0, 0));
}
 
MainWindow::MainWindow(QWidget *parent)
    : QMainWindow(parent)
{   
    MyLineEdit * te = new MyLineEdit();
 
 
         MyCompleter * completer = new MyCompleter(QStringList() << "112233" << "223344" << "334455", this);
         completer->setCaseSensitivity(Qt::CaseInsensitive);
         te->setCompleter(completer);
 
         QVBoxLayout * layout = new QVBoxLayout;
         layout->addWidget(te);
         QWidget *centralWidget = new QWidget;
         centralWidget->setLayout(layout);
         setCentralWidget(centralWidget);
}
 
MainWindow::~MainWindow()
{
 
}

class MyCompleter : public QCompleter
{
    Q_OBJECT;
public:
    inline MyCompleter(const QStringList& words, QObject * parent) :
            QCompleter(parent), m_model()
    {
        setModel(&m_model);
    }
    inline void update(QString word)
    {
        m_model.setStringList(QStringList() << "one" << "two" << "three");
        complete();
    }
private:
    QStringList m_list;
    QStringListModel m_model;
};

class MyLineEdit : public QLineEdit
{
    Q_OBJECT;
public:
    MyLineEdit(QWidget *parent = 0);
    ~MyLineEdit();
    void setCompleter(MyCompleter *c);
    MyCompleter *completer() const;
protected:
    void keyPressEvent(QKeyEvent *e);
private slots:
    void insertCompletion(const QString &completion);
private:
    MyCompleter *c;
};

MyLineEdit::MyLineEdit(QWidget *parent)
    : QLineEdit(parent), c(0)
{
}

MyLineEdit::~MyLineEdit()
{
}

void MyLineEdit::setCompleter(MyCompleter *completer)
{
    if (c)
        QObject::disconnect(c, 0, this, 0);

    c = completer;

    if (!c)
        return;

    c->setWidget(this);
    connect(completer, SIGNAL(activated(const QString&)), this, SLOT(insertCompletion(const QString&)));
}

MyCompleter *MyLineEdit::completer() const
{
    return c;
}

void MyLineEdit::insertCompletion(const QString& completion)
{
    setText(completion);
    selectAll();
}
void MyLineEdit::keyPressEvent(QKeyEvent *e)
{
    if (c && c->popup()->isVisible())
    {
        // The following keys are forwarded by the completer to the widget
        switch (e->key())
        {
        case Qt::Key_Enter:
        case Qt::Key_Return:
        case Qt::Key_Escape:
        case Qt::Key_Tab:
        case Qt::Key_Backtab:
            e->ignore();
            return; // Let the completer do default behavior
        }
    }

    bool isShortcut = (e->modifiers() & Qt::ControlModifier) && e->key() == Qt::Key_E;
    if (!isShortcut)
        QLineEdit::keyPressEvent(e); // Don't send the shortcut (CTRL-E) to the text edit.

    if (!c)
        return;

    bool ctrlOrShift = e->modifiers() & (Qt::ControlModifier | Qt::ShiftModifier);
    if (!isShortcut && !ctrlOrShift && e->modifiers() != Qt::NoModifier)
    {
        c->popup()->hide();
        return;
    }

    c->update(text());
    c->popup()->setCurrentIndex(c->completionModel()->index(0, 0));
}

MainWindow::MainWindow(QWidget *parent)
    : QMainWindow(parent)
{   
    MyLineEdit * te = new MyLineEdit();


         MyCompleter * completer = new MyCompleter(QStringList() << "112233" << "223344" << "334455", this);
         completer->setCaseSensitivity(Qt::CaseInsensitive);
         te->setCompleter(completer);

         QVBoxLayout * layout = new QVBoxLayout;
         layout->addWidget(te);
         QWidget *centralWidget = new QWidget;
         centralWidget->setLayout(layout);
         setCentralWidget(centralWidget);
}

MainWindow::~MainWindow()
{

}

To copy to clipboard, switch view to plain text mode 

[d_stranz]

If you are fixated on subclassing QCompleter, I can't help you.

You could probably accomplish what you want without subclassing by using a combination of a QSortFilterProxyModel, QStringListModel, and QRegExp to set a filter on the completion strings returned by the string list model. Then all of these behavioral problems you are battling with should magically disappear because you are using a wheel that already works rather than trying to invent your own.

[boo9]

> You could probably accomplish what you want without subclassing by using a combination of a QSortFilterProxyModel, QStringListModel, and QRegExp

You mean to disable default completer on qcombobox and filter items in the combobox directly ?
e.g, on each combobox::editTextChanged() notification, programatically rebuild new combo box item list ?
when user enters "aa bb cc" into combobox edit, then leave only items in the combobox list that contain "aa" and "bb" and "cc" ?

[d_stranz]

ou mean to disable default completer on qcombobox and filter items in the combobox directly ?

No. The "chain of command" is like this: combo box has a completer, completer has a proxy model, proxy model has the string list model with *all* strings and a regular expression that matches a subset (or none) of the strings.

You create your complete string model instance and populate it with strings. You also create the proxy model instance and give it the pointer to the string model as its source model. When you call setModel() on the completer, you would give it the pointer to the proxy model. The completer has no idea it is looking at a proxy instead of the full model; the interfaces and interactions are identical, it's just that the proxy is doing some magic to return only a part of the full model to the completer.

The proxy model does what your manual code does now - it takes the full list of possibilities, applies some logic to select out the matching subset, and passes that to the completer. The "logic" in this case is defined by a QRegExp regular expression.

You will probably have to create your regular expressions on the fly to match what the user is typing, and it will change with every keystroke. So when the user types "a" and you want to match every string that starts with an "a", then your regular expression is "^a[a-z]*[ _]{0,1}[a-z]*" In English this says, "match any string that starts with lowercase 'a', followed by zero or more lowercase letters of any type, followed by 0 or 1 spaces or underscores, followed by zero or more lowercase letters".

When the user types "aa bb", then you need "^aa[a]*[ _]{0,1}bb[b]*" which says, match any string starting with two or more lowercase 'a', followed by zero or one underscore or blank space, followed by two or more 'b' characters."

In essence, you are letting the QRegExp do the filtering for you by changing the rules it uses for filtering. These "rules" would probably be very similar to the "rules" you would be coding by hand, except these are expressed in regular expression syntax rather than a bunch of if / else / endif logic.

[boo9]

Thank you for detailed explanation, however RE will not make it in general case.
For simple searches with two tokens, "aa bb" query means aa followed by bb OR bb followed by aa. One can express that in simple RE
aa.*bb|bb.*aa

However when there is more tokens e.g, "aa bb cc dd" permuting all sequences of aa,bb,cc is not feasable.

3 tokens => 3! = 6 permutations
4 tokens => 4! = 24 permutations

cheers

[d_stranz]

I guess I have no idea what you are trying to do with your completer or what the use case might be.

[boo9]

> I guess I have no idea what you are trying to do with your completer

I have a list with 100 items.
Each list item is a text of 10-50 characters, 2-10 words
When I type in "aa" I would like only items that contain "aa" filtered
When I type in "aa bb" I would like only items that contain "aa" AND "bb" filtered, "aa bb" does not mean that bb follows aa, it only means that list item must contain "aa" and "bb" anywhere in the item text.
When I type in "aa bb cc" I would like only items that contain "aa" AND "bb" AND "cc" filtered, aa,bb,cc can appear at any position in the item text.

[d_stranz]

I have a list with 100 items.
Each list item is a text of 10-50 characters, 2-10 words

OK... can you please give an example with some of the real strings that you have in your list, and what the user might type? "aa bb cc" is just too abstract for me to understand how you might be using this in a real application.

[boo9]

item1: * (Search resistor range)(res-range) eltype=resistor rlcvalue >= %1 rlcvalue <= %2
item2: * (Search electrolite capacitor range)(cap-range) eltype=capacitor electrolite rlcvalue >= %1 and rlcvalue <= %2
item3: * (Search electrolite capacitor range metallic)(metcap-range) ceramic eltype=capacitor rlcvalue >= %1 and rlcvalue <= %2
....
item100: ....

how I want to quicky find correct itemX without scrolling through a list
- entering "cap electro" exepect to filter 2
- entering "cap range" expect to filter 2,3


I dont understand why such requirements appear strange and uncommon.
When one searches an email archive and have thousands of item in the mail box, one would expect to search for email message with words/tokens, and would expect the tokens in the mail message would appear in any order, not necessarilly the order they were entered in the search spec.

[d_stranz]

OK, now it makes more sense. Take a look at this example of a custom sort/filter proxy model.

You would re-implement the QSortFilterProxyModel::filterAcceptsRow(), and add your own method to the custom proxy that takes the string typed by the user in the combobox. In this method, split the string into tokens (QString::split()) and save the stringlist as a member variable in your proxy.

In the filterAcceptsRow() method, you retrieve the full string from your model into a QString (Use QStringListModel::data() and the Qt::DisplayRole ItemDataRole). For each token in the user's input, you call QString::contains() to see if the model string contains the token. If the answer is yes for all of the tokens in the user's string, you return true from filterAcceptsRow, otherwise you return false. Only those entries for which the result is true will be shown as selections in the combobox drop-down list.

This will accomplish your goals of returning only those strings that contain all of the tokens the user has typed and allowing those tokens to appear in any order.