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

Thiago Macieira thiago at macieira.org
Tue Apr 18 09:42:12 PDT 2017

Em terça-feira, 18 de abril de 2017 00:08:57 PDT você escreveu:
> I will try it this morning.
> Two remaining questions:
> - What is the default state now if we don't set it explicitly? Enabled true
> or false? 

Depends on the argument passed in the macro. With QtDebugMsg, it defaults to 
enabled; with QtWarningMsg, it defaults to disabled.

> - Where would be the right place in Subsurface code to put the
> MarbleDebug::setEnabled(false) ?

If we want it disabled by default, just change the macro.

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

More information about the subsurface mailing list