[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Limiting kDebug() output
From:       Thiago Macieira <thiago () kde ! org>
Date:       2007-08-16 14:25:51
Message-ID: 200708161625.51508.thiago () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Kleag wrote:
>Hello Ian,
>
>I already asked that on kde-core-devel and was the second one :-)
>
>In fact, this is due to a recent change and Thiago will soon solve the
> problem (http://lists.kde.org/?l=kde-core-devel&m=118718705504344&w=2)
>
>In the meantime I switched back to qDebug for some messages...

By the way, using qDebug() is OK in KDE applications. You just won't have 
a debug area.

Libraries should use kDebug() so that output can be filtered or switched 
off without rebuilding the library. That's what areas are for.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

["signature.asc" (application/pgp-signature)]

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]