apaku at gmx.de
Sun Jun 8 22:13:50 UTC 2008
On 08.06.08 22:39:39, David Nolden wrote:
> Well, I used kWarning when something happened that actually should not and is
> a problem, so the user can tell something "bla doesn't work, and kdevelop is
> giving that warning".
> kDebug is for stuff like "parsing ..." or "loading ...".
> So what's wrong about that?
There's tons of useless output because they can't be de-activated and I
can't read any debug-output while kdevelop is parsing something.
If we need some system for such warnings, which shouldn't be displayed
in the GUI, then we need to implement our own logging. kDebug/kWarning
isn't suitable for that.
Is this really happening?
More information about the KDevelop-devel