[kservice] new warnings from kbuildsycoca5, every time

[David Faure]

On mardi 31 mai 2016 00:15:45 CEST René J.V. Bertin wrote:
> That's another weird thing then. I keep adding qDebug() statements to code
> I'm working on, wonder why I don't see them on the terminal, and then
> either set "*.debug=true" in qtlogging.ini or replace qDebug() with
> qWarning() (I have *.warning=true). I'm not expecting qDebug() etc. to be
> subject to fine-grained filtering, of course :)

My point is that it's not subject to ANY filtering, not even 
the filtering you seem to expect with *.debug=true/false.

That filtering mechanism is for qCDebug/qCWarning only;
qDebug/qWarning is older and "one layer below", architecturally speaking.

-- 
David Faure, faure at kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5