User:Ned Scott/Sandbox3: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 19: | Line 19: | ||
; 1:Debug logging | ; 1:Debug logging | ||
; 2:Debug logging with freemem, fps and cpu usage shown on screen | ; 2:Debug logging with freemem, fps and cpu usage shown on screen | ||
;3:Debug logging with freemem, fps and cpu usage and full smb logging | ; 3:Debug logging with freemem, fps and cpu usage and full smb logging | ||
loglevel also accepts a "hide" boolean attribute. Default value is true (old behavior), which hides the "enable debugging" guisetting. When false, the "enable debugging" guisetting will switch between min(loglevel, 0) and max(loglevel, 2) for off and on respectively. This is useful for chasing infrequent bugs where you may always want a debug text log, yet still be able to get at the on screen debug info without restarting the app. | loglevel also accepts a "hide" boolean attribute. Default value is true (old behavior), which hides the "enable debugging" guisetting. When false, the "enable debugging" guisetting will switch between min(loglevel, 0) and max(loglevel, 2) for off and on respectively. This is useful for chasing infrequent bugs where you may always want a debug text log, yet still be able to get at the on screen debug info without restarting the app. | ||
}} | }} |
Revision as of 21:34, 7 October 2012
<loglevel hide="attribute">options</loglevel>
The logging level that XBMC will use to log errors and information. Available values are:
- -1
- No logging, suppresses all log output
- 0
- Normal logging, only logging errors (Default)
- 1
- Debug logging
- 2
- Debug logging with freemem, fps and cpu usage shown on screen
- 3
- Debug logging with freemem, fps and cpu usage and full smb logging
loglevel also accepts a "hide" boolean attribute. Default value is true (old behavior), which hides the "enable debugging" guisetting. When false, the "enable debugging" guisetting will switch between min(loglevel, 0) and max(loglevel, 2) for off and on respectively. This is useful for chasing infrequent bugs where you may always want a debug text log, yet still be able to get at the on screen debug info without restarting the app.
Main options:
-1, 0, 1, 2, 3