JFYI: ---------- Forwarded Message ---------- Betreff: [ powersave-Feature Requests-1721072 ] kpowersave: usage of kdDebug Datum: Mittwoch, 13. Juni 2007 Von: "SourceForge.net" <[EMAIL PROTECTED]> An: [EMAIL PROTECTED]
Feature Requests item #1721072, was opened at 2007-05-18 01:07 Message generated for change (Comment added) made by stoppel22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=700012&aid=1721072&group_id=124576 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Priority: 5 Private: No Submitted By: Michael Biebl (mbiebl) >Assigned to: Danny Kukawka (stoppel22) Summary: kpowersave: usage of kdDebug Initial Comment: Hi Danny, I was wondering why kpowersave doesn't use kdDebug [1] for its logging. Atm you are using some homemade debug code, which has to be enabled during ./configure via --enable-debug-msg. This is suboptimal. If kpowersave would use the kdDebug framework, we could set the default to no logging, and in case of a bug report I could asked my users to enable logging into a file (via kdebugdialog e.g.) which would make it much easier to track down any problems. Cheers and keep up the good work, Michael [1] http://api.kde.org/3.2-api/kdecore/html/group__kdebug.html ---------------------------------------------------------------------- >Comment By: Danny Kukawka (stoppel22) Date: 2007-06-13 10:59 Message: Logged In: YES user_id=1138349 Originator: NO done by commit r2973 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=700012&aid=1721072&group_id=124576 ------------------------------------------------------- _______________________________________________ powersave-devel mailing list [email protected] http://forge.novell.com/mailman/listinfo/powersave-devel
