rjvbb added a comment.
> BTW it is *not* curious that isn't qInfo isn't "disabled by *.info=false in qtlogging.ini", it's rather expected since qInfo() is one layer below categorized logging, just like qDebug and qWarning. qtlogging.ini (and the QT_LOGGING_RULES env vars) are about qC*. I've read that before, yet I notice that qDebug() statements don't print for me if I have *.debug=false in my qtlogging.ini file. Whatever the true reason, I've taken to using qWarning() in my own tests before learning about qInfo() (I have *.warning=true set in qtlogging.ini). Regardless of that, I meant that AFAIU one typically enables info level messages when even more verbose output than debug output is required. The qC* categories seem to reflect that, IMHO. > There's proper API for setting applications defaults, without the need for env vars. I only see QLoggingCategory::setFilterRules(), is that what you're referring to? I don't think it'd be proper to use QSettings for a test application, leaving a persistent resource somewhere. REPOSITORY R342 KIO AudioCD REVISION DETAIL https://phabricator.kde.org/D7380 To: rjvbb, #frameworks, davidedmundson, ltoscano Cc: dfaure, ltoscano, davidedmundson
