On 4/17/21 11:40 AM, Chris Cannam wrote:
Can anyone recall why we introduced the RG_DEBUG macros in the first place?
Location and filtering as David said. Then Tom Breton took it to the next level and added a file-by-file prefix to the logging messages (the current RG_MODULE_STRING). Later on I added RG_WARNING to replace all the legitimate use of cerr for warnings to help the user.
I personally have no need for location information. In fact I find it annoying since it is on Every Single Line of logging. I would rather log it manually once, then follow that with the rest of the logging. (Having the location on every line can help with nested calls, but that's pretty rare for me. I usually come up with some clever indenting if needed.)
It would be really nice to have my own logging category that only I would have enabled. Then only I see my logging. Logging is a very personal thing. Other people's logging is of limited use to me.
To that end, the existing logging could be dumped into a "misc" or "legacy" category and then it would all disappear for me. This would be *really* nice. I seriously do not care about 99% of the logging that I see in the output right now. It just gets in my way.
So, getting rid of RG_MODULE_STRING and using QLoggingCategory is starting to sound interesting to me.
Ted. _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
