2012-12-13, 13:02
Just an update that will not surprise anyone: the issue is unchanged with XBMC 12 RC1
From your statement I see it has to do with calling the log function of XBMC. Although I understand logging is cool and all, I don't really need it because the plugin is working fine for me. I wonder if I can get it running by removing all references to the logging call you know, just to increase the WAF
EDIT: figured it out. Did not need to comment everything out, just some in the __init__ and replace them with a nonsense statement declaring a new madeup variable to be true.
'
EDIT: I did need to comment them ALL out and replaced them with a nonsense statement so that every function still "did something", otherwise it would crash still xbmc when closing Spotimc.
Yay, I learned something new today and got Spotimc working again until we wait for a real fix =)
From your statement I see it has to do with calling the log function of XBMC. Although I understand logging is cool and all, I don't really need it because the plugin is working fine for me. I wonder if I can get it running by removing all references to the logging call you know, just to increase the WAF
EDIT: figured it out. Did not need to comment everything out, just some in the __init__ and replace them with a nonsense statement declaring a new madeup variable to be true.
'
EDIT: I did need to comment them ALL out and replaced them with a nonsense statement so that every function still "did something", otherwise it would crash still xbmc when closing Spotimc.
Yay, I learned something new today and got Spotimc working again until we wait for a real fix =)
Code:
12:38:54 T:2568977216 NOTICE: 192.168.178.104 - - [13/Dec/2012:12:38:54] "HEAD /track/4c4ktiPhwxXweksj7wq1tv.wav?idx=1 HTTP/1.1" 200 45687644 "" "Spotimc/1.0-beta3 (XBMC/12.0-RC1 Git:49b2d1f)"