2015-02-13, 11:05
(2015-02-03, 16:40)ronie Wrote:(2015-02-03, 11:28)takoi Wrote:(2015-02-03, 11:21)Razze Wrote: but thats what ruuk mentioned?I think ruuk meant the opposite. So you log notice instead of debug if the addon setting is enabled. If disabled you use debug.
and it would probably be very confusing for most users. if you got an problem with my addon, it's really handy to have the log of kodi + addon log without the noise form all the other addons installed.
let me try to clear things up a bit.
1) we encourage all addon devs to only use the LOGDEBUG level.
we prefer addons not to log anything to the logfile, unless debuglogging in kodi is enabled.
why? because we don't rotate logfiles and on 24/7 systems the logfile will get out of hand quickly (and possibly will fill up all diskspace) if every addon would constantly log to it.
2) adding an additional setting in the addon to enable logging is optional, but very much recommended.
why? because the kodi devs get very annoyed by all the addon logspam if they have to troubleshoot some core issue using the Debug Log file.
so the less your addon logs, the better it is.
if a user has an issue with your addon, just explain him to turn on debug logging in kodi and to enable logging in your addon.
does anyone have any experience with external library that are using the correct levels and how to force every message to logdebug instead?