Re: Porting notice: kDebug and qDebug need to go to qCDebug.

2013-10-16 Thread David Faure
On Wednesday 16 October 2013 15:08:53 Mark wrote: > On Wed, Oct 16, 2013 at 2:39 PM, David Faure wrote: > > On Tuesday 15 October 2013 21:58:51 Mark wrote: > >> Also, by default when porting to a qCDebug line with a category you > >> won't see log output because custom categories have everything >

Re: Porting notice: kDebug and qDebug need to go to qCDebug.

2013-10-16 Thread Mark
On Wed, Oct 16, 2013 at 2:39 PM, David Faure wrote: > On Tuesday 15 October 2013 21:58:51 Mark wrote: >> Also, by default when porting to a qCDebug line with a category you >> won't see log output because custom categories have everything >> disabled by default. > > This has just been fixed in Qt,

Re: Porting notice: kDebug and qDebug need to go to qCDebug.

2013-10-16 Thread David Faure
On Tuesday 15 October 2013 21:58:51 Mark wrote: > Also, by default when porting to a qCDebug line with a category you > won't see log output because custom categories have everything > disabled by default. This has just been fixed in Qt, though. https://codereview.qt-project.org/66744 -- Da

Porting notice: kDebug and qDebug need to go to qCDebug.

2013-10-15 Thread Mark
Hi all, After today' frameworks meeting we (mostly David Faure and Kai Koehne) discussed the categorized debugging support that is new in Qt 5.2. I've written a detailed wiki page to layout the current status of categorized debugging in Qt 5.2 and what we still need (and is coming) in Qt 5.3. You