> From: David Faure
> To: development@qt-project.org; Diego Iastrubni
> Cc:
> Sent: Sunday, February 5, 2012 5:54 PM
> Subject: Re: [Development] Work on qDebug and friends
>
> On Sunday 05 February 2012 10:50:48 BRM wrote:
>> > From: Diego Iastrubni
>> &
On Sunday 05 February 2012 10:50:48 BRM wrote:
> > From: Diego Iastrubni
> >
> >On Fri, Feb 3, 2012 at 1:10 PM, David Faure wrote:
> >
> >Once this goes in I'll add support for %pid%, %processname% and
> >%timestamp%,>
> >>and we'll be all set :)
> >
> >You meant %threadid% of course... right?
>
> From: Diego Iastrubni
>On Fri, Feb 3, 2012 at 1:10 PM, David Faure wrote:
>
>Once this goes in I'll add support for %pid%, %processname% and %timestamp%,
>>and we'll be all set :)
>
>You meant %threadid% of course... right?
Wouldn't having both available be useful?
Ben
On Fri, Feb 3, 2012 at 1:10 PM, David Faure wrote:
> Once this goes in I'll add support for %pid%, %processname% and
> %timestamp%,
> and we'll be all set :)
>
You meant %threadid% of course... right?
___
Development mailing list
Development@qt-project
> From: David Faure
> On Friday 03 February 2012 10:51:50 kai.koe...@nokia.com wrote:
>> Finally I came around to actually implement something:
>>
>> http://codereview.qt-project.org/#change,15129
>>
>> The idea is that you can customize the output by setting the
>> QT_DEBUG_PATTERN environm
On Friday 03 February 2012 10:51:50 kai.koe...@nokia.com wrote:
> Finally I came around to actually implement something:
>
> http://codereview.qt-project.org/#change,15129
>
> The idea is that you can customize the output by setting the
> QT_DEBUG_PATTERN environment variable. Setting it e.g. to
t; Cc: development@qt-project.org
> Subject: Re: [Development] Work on qDebug and friends
>
> > -Original Message-
> > From: ext Diego Iastrubni [mailto:diegoi...@gmail.com]
> > Sent: Tuesday, January 24, 2012 1:18 PM
> > To: Koehne Kai (Nokia-MP/Berlin)
Sorry for the lack of context (dealing with digest emails while on leave :-P ).
With the talk about logging in this thread, is it of interest / scope to also
have the associated classes support capturing the standard C/C++ streams? By
this, I mean capturing whatever gets logged via std::cout or
I think QLog from QTopia was very good.
You define your category in your project and QLog will define a static bool for
each category e.g.
# define QLOG_ENABLE(dbgcat) \
class dbgcat##_QLog : public QLogBase { \
public: \
static inline bool enabled() { return 1; }\
};
On 01/24/2012 09:03 PM, ext kai.koe...@nokia.com wrote:
> One of the things still missing in the current debugging framework is
> to categorize messages by area: This would allow you to
> enable/disable e.g. debug messages for only one part of your app ...
...
> That's at least what I got after doi
Kai Koehne wrote:
> Olivier Goffart wrote:
> > On Tuesday 24 January 2012 11:03:11 kai.koe...@nokia.com wrote:
> > > + comparing int's is fast
> > > - one central registry needed for debug areas (no go for custom
> > > apps?)
> >
> > May I suggest we use something like qHash("MyModule") And ignore
ra
Subject: Re: [Development] Work on qDebug and friends - debug areas
On Wednesday 25 January 2012 20:07:57 Thiago Macieira wrote:
> On Wednesday, 25 de January de 2012 18.28.18, Olivier Goffart wrote:
> > KDebug::registerArea needs a registery. That works for KDE, but I don't
>
On Wednesday 25 January 2012 20:07:57 Thiago Macieira wrote:
> On Wednesday, 25 de January de 2012 18.28.18, Olivier Goffart wrote:
> > KDebug::registerArea needs a registery. That works for KDE, but I don't
> > know if that is a good idea for Qt
don't know if it can be applied to all platform or
On Wednesday, 25 de January de 2012 18.28.18, Olivier Goffart wrote:
> KDebug::registerArea needs a registery. That works for KDE, but I don't
> know if that is a good idea for Qt
TBH, I really don't want the default debugging system in Qt to rely on config
files. We're removing QSettings depende
On Wednesday 25 January 2012 13:18:33 Thiago Macieira wrote:
> On Wednesday, 25 de January de 2012 14.28.04, kai.koe...@nokia.com wrote:
> > I guess the KDebug::registerArea David mentioned does pretty much that.
> > I
> > researched a bit whether you somehow can do hashing already on compile
> > t
On Wednesday, 25 de January de 2012 14.28.04, kai.koe...@nokia.com wrote:
> I guess the KDebug::registerArea David mentioned does pretty much that. I
> researched a bit whether you somehow can do hashing already on compile
> time, but it seems not to be possible even with Cx11 If you're doing
> so
> -Original Message-
> From: ext Olivier Goffart [mailto:oliv...@woboq.com]
> Sent: Wednesday, January 25, 2012 2:03 PM
> To: development@qt-project.org
> Cc: Koehne Kai (Nokia-MP/Berlin)
> Subject: Re: [Development] Work on qDebug and friends - debug areas
>
> On
On Tuesday 24 January 2012 11:03:11 kai.koe...@nokia.com wrote:
> Hi,
>
> One of the things still missing in the current debugging framework is to
> categorize messages by area: This would allow you to enable/disable e.g.
> debug messages for only one part of your app ...
>
> KDE & kDebug
>
> He
Op 25-1-2012 8:33, kai.koe...@nokia.com schreef:
> True. As much as I think a logging framework under the Qt project
> umbrella would be useful, there'll be also always projects who want to
> implement their own one. But ideally they should be able to do this on
> the common infrastructure in Qt
> -Original Message-
> From: Rose Todd (Nokia-M/Alpharetta)
> Sent: Tuesday, January 24, 2012 5:26 PM
> To: Koehne Kai (Nokia-MP/Berlin); development@qt-project.org
> Subject: RE: Work on qDebug and friends
>
> [...]
> The "additional things we need" question is pretty subjective, but ther
> Hi,
>
> I've been working on a patch to the Qt logging framework:
> http://codereview.qt-project.org/#change,13433,patchset=14 . Basically it
> redefines qDebug() and friends as a macro so that we can automatically
> capture the source file, line, and function a particular message comes from:
>
On Tuesday 24 January 2012 11:03:11 kai.koe...@nokia.com wrote:
> KDE & kDebug
>
> Here debug categories are basically ints, which have to be registered
> 'kdelibs/kdecore/kdebug.areas'. You can pass your specific as an argument
> to kDebug(..) et al., but usually you just set a define
> (KDE_DEFA
On Tue, Jan 24, 2012 at 2:39 PM, wrote:
>
> Well, I plan to work on a simple environment switch which will enable the
> default logger to show the file, line, and the log level. My idea is that an
> IDE e.g. Qt Creator sets this environment variable, and voila, you can
> suddenly click on your
> -Original Message-
> From: ext Diego Iastrubni [mailto:diegoi...@gmail.com]
> Sent: Tuesday, January 24, 2012 1:18 PM
> To: Koehne Kai (Nokia-MP/Berlin)
> Cc: development@qt-project.org
> Subject: Re: [Development] Work on qDebug and friends
>
> So, if I want t
On Tue, Jan 24, 2012 at 12:41 PM, wrote:
> I've been working on a patch to the Qt logging framework:
> http://codereview.qt-project.org/#change,13433,patchset=14 . Basically it
> redefines qDebug() and friends as a macro so that we can automatically
> capture the source file, line, and function a
> -Original Message-
> From: Goddard Michael (Nokia-MP/Brisbane)
> Sent: Tuesday, January 24, 2012 11:57 AM
> To: Koehne Kai (Nokia-MP/Berlin); development@qt-project.org
> Subject: Re: [Development] Work on qDebug and friends
>
> Hello,
>
> > QMe
> -Original Message-
> From: ext Frans Klaver [mailto:franskla...@gmail.com]
> Sent: Tuesday, January 24, 2012 11:46 AM
> To: Koehne Kai (Nokia-MP/Berlin)
> Cc: development@qt-project.org
> Subject: Re: [Development] Work on qDebug and friends
>
> [...]
> Soun
Hi,
One of the things still missing in the current debugging framework is to
categorize messages by area: This would allow you to enable/disable e.g. debug
messages for only one part of your app ...
KDE & kDebug
Here debug categories are basically ints, which have to be registered
'kdelibs/k
Hello,
> QMessageLogger(__FILE__, __LINE__, Q_FUNC_INFO):debug("Hello World")
Yay, I don't have to do that any more :) Although now I'll have to remove
the existing ones..
>The patch is almost ready to go in ... Anyhow, the question is whether
>there's additional things we need to have in QtC
On Tue, Jan 24, 2012 at 11:41 AM, wrote:
> I've been working on a patch to the Qt logging framework:
> http://codereview.qt-project.org/#change,13433,patchset=14 . Basically it
> redefines qDebug() and friends as a macro so that we can automatically
> capture the source file, line, and functi
Hi,
I've been working on a patch to the Qt logging framework:
http://codereview.qt-project.org/#change,13433,patchset=14 . Basically it
redefines qDebug() and friends as a macro so that we can automatically capture
the source file, line, and function a particular message comes from:
qDebug("
31 matches
Mail list logo
