[PATCH] MarbleDebug: don't use a class extending QIODevice as a null device

Thiago Macieira thiago at kde.org
Tue Apr 18 09:36:17 PDT 2017

Em terça-feira, 18 de abril de 2017, às 09:23:12 PDT, Stefan Fuchs escreveu:
> /home/stefan/Entwicklung/Subsurface/marble-source/src/lib/marble/MarbleDebug
> .cpp:27:53: error: passing 'const QLoggingCategory' as 'this' argument of
> 'void QLoggingCategory::setEnabled(QtMsgType, bool)' discards qualifiers
> [-fpermissive] loggingCategory().setEnabled(QtDebugMsg, enabled);

Hold on. This one is weird, because how can you call that non-const method if 
everything is const?

Kai, how is one supposed to call QLoggingCategory::setEnabled()? Or are we not 
supposed to?

Or should we skip the Q_LOGGING_CATEGORY macro and deploy our own code?

Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel Open Source Technology Center

More information about the subsurface mailing list