Xbmc.log vs. xbmc.output

i'm using xbmc 12-12.

in this version xbmc.log(..) leaves a fatal entry in the xbmc.log file, xbmc.output(..) leaves no entry in the log file. hmm.. is this a known bug?

and is there a function allowing me to define the log level while logging? i think the naming of log and output is not the best way to name the functions. xbmc.logfatal() and xbmc.lognotice() would be better and a function xbmc.log(loglevel,string) would be very helpfull...

this is not a bug. the idea was that xbmc.log would write something to the logfile no matter what (thus you get a fatal error). xbmc.output was already there from the beginning and is used to log with info.

xbmc.log will be extended in the future with an optional argument so you can specify the log level

well, thanks for the information, but xbmc.output() does log nothing in my situation. even with loglevel 0 in xboxmediacenter.xml, xbmc.output() logs nothing.