Closed herrnst closed 11 years ago
Sorry Daniel, I have to close this. I wrote a working version on my own: 67cada1fc0216ad090ef79f2818c4e31a4dfa1c8
No problem, looking at your commit, I even missed many things (so the term "half-assed try" applies very well it seems). Will happily test your changes this evening (and I have a feeling it will work even without touching the server side at all...)
Just tested and found working without further adjustment to the server - thanks for taking on this! (really should leave such things to the pro's - no promises here, though ;)) )
These changes sort-of lift xbmc-addon-xvdr's compatibility to recent API 1.7.0 updates.
Please note: While this PR makes XBMC-master initialise and load the addon, and connects to the XVDR server, this will - for some reason I don't understand, maybe you have an idea - crash the VDR (1.7.33) server:
According to the backtrace (see http://pastebin.com/jqXv4E3M - "bt full") it crashes in src/xvdr/xvdrclient.c in processTIMER_Add() in the call to cTimer::Parse(buffer). I guess the format (or order) of some options retrieved at the top of that method have changed somehow, so the string passed to cTimer::Parse() is invalid. But this needs to be investigated further.
So while this PR doesn't provide a fully working solution ATM (and maybe looks like some half-assed attempt to update things ;) ), this PR might still act as a starting point for something. At least the client addon builds without errors :)