Can't say anything about priority because everyone thinks his issues are most important
Well mine really aren't but here's two requests, not bugs but affect usability:
1) When MPWebint can't connect to database(?) and you get that weird pipeline(?) error, could it be coded so that you'd only get that error popup once instead of flooding the whole desktop while getting new popup twice in a second? I haven't had this issue for a while but some users seems to get it still. Maybe you could change popup so that it would prompt Try again, Stop MPWebint Service and Cancel(Ignore)?
2) MPWebInt definately pins the CPU when user opens TVGuide. I recently installed MPWebint .16 on 3.2ghz dualcore and didn't have this issue anymore but I'm sure people with less horses on they HTPC still suffer from this. Previously with singlecore 2.2ghz system TV picture froze for a half second to second everytime I opened TV guide. I was guessing before it was related somehow to database reading but now that I've though about it, it's probably just MPWebint's call function for generating TV Guide that pins CPU. Could you optimize it so it would run in a threads or at least insert little (1-5 ms) pauses or something on loops so it wouldn't utilize all CPU power available at the moment, leaving little room for other apps like MP
