Inactivate some output in the new kDebug calls

Thiago Macieira thiago at kde.org
Wed Aug 15 15:08:19 BST 2007


Kleag wrote:
>Hello,
>
>Is there a way to inactivate some output of the new kDebug ? Because in
> the current form I find it somewhat unusable with something like 200
> chars (or 600 if there is some templates) before the actual message.
>
>I have missed some messages I think and I don't understand the rationale
>behind the change. imo, debug messages should be adaptable by the
> developer as they are read by him/her. Thus, the interest of something
> like k_funcinfo or the other __FILE__, etc.
>Maybe this could be made easier to use but I find the current setting
> really too heavy to be useful. I'd prefer to be able to activate the
> current behavior if needed with a kind of switch and to have by default
> the old one.

I'll fix that soon.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070815/4b381009/attachment.sig>


More information about the kde-core-devel mailing list