2013-03-25, 18:43
(2013-03-24, 20:41)theowiesengrund Wrote: Hi MariusTh86,
that was pretty weird with the multipart episode problem: I tried to send you the bug report, but then i recognized that i hadn't configured my mailto link to Gmail yet (had a fresh OS install a few days ago). Tried to recreate the problem, but then all of a sudden it worked without a problem. Well, i'm not complaining ;-)
I'm still having a suggestion (i think it was mentioned before): When updating metadata of a huge database (over a hundreds of movies), i would like to do it over night respectively when i'm not in front of the computer. But the process is nearly everytime stopped because TMDB is not reachable for a second or something else. While i appreciate the notion, that the user is informed about the errors, it would be great if the process would continue after a timeout (30 seconds?). Now, i have to click away every message box, which makes it difficult to let updates run over night. Would be a nice option, don't you think?
Had now finally a chance to send you a small donation. Keep up the good work and the awesome support here!
(2013-03-24, 23:56)MariusTh86 Wrote: Thank you for the donation!
I think I can come up with something here using growl or now OS X 10.8's notification center instead of process interrupting messages.
Are you using the cocoa or intel build? Because the cocoa build is actually more likely to 'timeout' when there's no activity on the computer.
Intel / Cocoa build for me. Timing out often. Anything you can do to just log it, but move on; will be tremendously helpful.