QCompleter problem on Mac

[jules.dentremont]

I recently added a QCompleter to a QComboBox in a legacy application. The code is straightforward:

m_completer = new QCompleter(predefinedComboBox->model(), this);
m_completer->setFilterMode(Qt::MatchContains);
m_completer->setCaseSensitivity(Qt::CaseInsensitive);
m_completer->setCompletionMode(QCompleter::PopupCompletion);
predefinedComboBox->setCompleter(m_completer);

On Windows and Linux, this works just as I expected. Typing a few characters shows a popup with the matching completions, and you can click on one to select it. On Mac, though, clicking on the list of completions has no effect. You have to use up and down keys to select a completion, then press Return.

Is this the expected behaviour on Mac? Is it a bug in QCompleter or my code? Is there something I can do differently to get this working?

Using Qt 5.15.0.

[VRonin]

I don't understand what you are trying to accomplish, QComboBox already has a completer, you don't need to set it manually. predefinedComboBox->setAutoCompletion(true);

[jules.dentremont]

Thanks for the quick response. I'll try that out, but why isn't it documented at https://doc.qt.io/qt-5/qcombobox.html?

[artwaw]

@jules-dentremont

'By default, for an editable combo box, a QCompleter that performs case insensitive inline completion is automatically created.'

https://doc.qt.io/qt-5/qcombobox.html#setCompleter

[VRonin]

It's actually documented as obsolete. The reason is that the completer is already set up by default and you can call predefinedComboBox->setCompleter(nullptr); to disable it

[jules.dentremont]

Thanks, but that is not my main point, which is that setCompletionMode(QCompleter::PopupCompletion) doesn't work properly on Mac. You can't select from the list of completions using a mouse like you can on Windows or Linux.

[VRonin]

Unfortunately I don't have a Mac to test. @SGaist you are renown for Mac stuff, could you confirm?

[SGaist]

Hi,

Expected behaviour ? No it's not.

Can you provide a minimal compilable example that triggers this behaviour ?

Which version of macOS ?
Did you also check with a more recent version of 5.15 ?