Re: [Development] Qt::MatchRecursive on QTreeWidget does not work

2017-02-14 Thread wim delvaux
First let me say that I am no newbie to Qt. In fact I have been using Qt since v 1. I checked the source code and found this in qtreewidget.cpp (near line 3050) method findItems d->model->match(model()->index(0, column, QModelIndex()), Qt::DisplayRole, text, -1, flags ); The model is a

Re: [Development] Qt::MatchRecursive on QTreeWidget does not work

2017-02-14 Thread Marc Mutz
On Tuesday 14 February 2017 23:46:45 wim delvaux wrote: > I have this code on a QTreeWidget in Qt 5.7 on Linux > > Qt::MatchFlags F = Qt::MatchRecursive | Qt::MatchContains | > Qt::MatchWrap | Qt::MatchFixedString; > > if( ui->Regex_CB->isChecked() ) { > F |= Qt::MatchRegExp; >

[Development] Qt::MatchRecursive on QTreeWidget does not work

2017-02-14 Thread wim delvaux
I have this code on a QTreeWidget in Qt 5.7 on Linux Qt::MatchFlags F = Qt::MatchRecursive | Qt::MatchContains | Qt::MatchWrap | Qt::MatchFixedString; if( ui->Regex_CB->isChecked() ) { F |= Qt::MatchRegExp; } CurrentMatches = ui->Output_TW->findItems( Txt, F ); I would

Re: [Development] [meta-qt5] Qt5.8 qdbuscpp2xml broken for kde baloo?

2017-02-14 Thread Thiago Macieira
Em terça-feira, 14 de fevereiro de 2017, às 10:08:27 PST, Andreas Müller via Development escreveu: > On Tue, Feb 14, 2017 at 12:18 AM, Andreas Müller > > wrote: > > I just ran a gdb session but debug information gets lost somewhere - > > only see non very helpful

[Development] First Qt 5.9 alpha snapshot available

2017-02-14 Thread Jani Heikkinen
Hi all, You can find (soon, mirroring still ongoing) first qt 5.9 alpha snapshot (src only) from http://download.qt.io/snapshots/qt/5.9/5.9.0-alpha/latest_src/ Those aren't yet official alpha src packages but quite close so please inform me immediately if you notice something important

Re: [Development] [meta-qt5] Qt5.8 qdbuscpp2xml broken for kde baloo?

2017-02-14 Thread Andreas Müller via Development
On Tue, Feb 14, 2017 at 12:18 AM, Andreas Müller wrote: > I just ran a gdb session but debug information gets lost somewhere - > only see non very helpful disassembler. Need to sort out where debug > information gets lost or paths are aligned to break gdb... > OK -g