On segunda-feira, 17 de abril de 2017 13:24:26 PDT Lubomir I. Ivanov wrote: > On 17 April 2017 at 22:29, Thiago Macieira <thi...@macieira.org> wrote: > > On segunda-feira, 17 de abril de 2017 12:01:48 PDT Lubomir I. Ivanov wrote: > >> QDebug mDebug() > >> > >> { > >> > >> return QDebug( QtDebugMsg ); // or "return qDebug();" > >> > >> } > >> > >> which will essentially enable debug output for everything in Marble, > >> until we write a dummy Class with an overloaded << operator to void > >> all the incoming debug calls. > > > > It would be better to use a category and then simply turn the category > > off. It can be enabled manually by users with QT_LOGGING_RULES > > environment variable. > > > > See http://doc.qt.io/qt-5/qloggingcategory.html. > > thanks, for the suggestion, Thiago. > > Stefan, could you please test the attached patch and if it works, > submit it to Github for approval.
This disables the debug output for the default category, that is, every user of qDebug(). I was suggesting turning mDebug() into qCDebug(...). // in a header namespace Marble { Q_DECLARE_LOGGING_CATEGORY(loggingCategory) } #define mDebug qCDebug(Marble::loggingCategory) // in one source file namespace Marble { Q_LOGGING_CATEGORY(loggingCategory, "marble", QtWarningMsg) } -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center _______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface