[PATCH] MarbleDebug: don't use a class extending QIODevice as a null device
Lubomir I. Ivanov
neolit123 at gmail.com
Tue Apr 18 06:54:17 PDT 2017
On 18 April 2017 at 16:47, Stefan Fuchs <sfuchs at gmx.de> wrote:
> Hello Lubomir,
> Am 18.04.2017 um 13:22 schrieb Lubomir I. Ivanov:
> here are the updated Marble files and a patch diff for review.
> i can't build Marble to test these changes ATM though.
> Looks good, so long as "Marble::category" isn't too generic a name.
> ok, i've renamed it to Marable::loggingCategory.
> Stefan, could you please try building and running the attached patch?
> you can toggle the debugging with MarbleDebug::setEnabled(true/false)
> e.g. from the Subsurface source code.
> Sorry, I'm once again lost...
> I have multiple compile issues like this:
> In member function 'virtual void Marble::GeoDataPolygon::pack(QDataStream&)
> error: no match for call to '(QDebug) ()'
> mDebug() << "innerRing: size" << p()->inner.size();
> Also for:
> and many others.
> But all these files do
> #include "MarbleDebug.h"
i must admit i followed Thiago's suggestions blindly.
Thiago, do you have an idea why this happens?
#define mDebug qCDebug(Marble::loggingCategory)
expands calls like this one:
mDebug() << "innerRing: size" << p()->inner.size();
qCDebug(Marble::loggingCategory)() << "innerRing: size" << p()->inner.size();
is it complaining about the extra()?
More information about the subsurface