error and warning messages
Ivar Eskerud Smith
ivar_eskerud at hotmail.com
Sun May 15 21:24:01 CEST 2011
Thank you for your answer Scott, and for a great program. I understand most of the messages might not be useful for most people, but if it is not a lot of work to add some logging of the debug info, maybe it could be done? If some sort of logger class is used, I think 1 line of code inside the debug() function is all that is needed. One could log all debug info with the possibility to clear the entire log, and the possibility to turn this logging on/off (could be off by default as I guess most people won`t use it). Or just log the last occurred error which could be accessed through some lastError() function...
> Subject: Re: error and warning messages
> From: wheeler at kde.org
> Date: Fri, 13 May 2011 22:56:40 +0200
> To: taglib-devel at kde.org
> On May 13, 2011, at 9:20 PM, Ivar Eskerud Smith wrote:
> > I have asked this question before, and I don`t think there is a way to do this.
> Historically the reason for this is that the debugging messages were only intended for TagLib developers (honestly, I don't think any of them are particularly useful for application developers). At that time KDE (and related packages, including TagLib) were always built with the NDEBUG define in release packages, which defines debug(x) and debugData(x) as empty macros.
> taglib-devel mailing list
> taglib-devel at kde.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the taglib-devel