http://bugs.gpodder.org/show_bug.cgi?id=173
Tyler Rick <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugs.gpodder....@tylerrick. | |com --- Comment #7 from Tyler Rick <[email protected]> 2009-03-09 19:33:01 --- (In reply to comment #4) > Here's a proposal: have the error dialog behave like normal, and as soon as > more errors happen, just modify the message dialog and add a "details" button > that, when clicked, shows a window with all the error messages. > > This is just an example on how it would look like. One "error" happens every 5 > seconds, and the message dialog is updated accordingly. > > What do you think? I definitely agree that multiple download errors need to be aggregated somehow, but is a pop-up dialog box really the best place for them? I find popups to be distracting. It's not like any action is required from the user (maybe there would be if we gave the option to retry). Usually I just want to let gPodder download a bunch of stuff in the background, trust it to do the "right thing" with download errors, and simply check back in an hour (or day...) to see if the downloads are finished and if there were any errors. So from my perspective, I don't even care to find out about the failed downloads until I come back and foreground gPodder to check on my downloads. Furthermore, if a download failed, it's hopefully due to a transient network problem or similar and the desired behavior I think would be for it to time out, log the error, but keep it in the queue and continue it later. If I understand correctly, your proposed UI would only work to collect multiple error messages if the user left the dialog open. What if they closed it immediately and an error happened 1 minute later? Wouldn't that just reopen "the error window" again and defeat the effort to aggregate errors? Because in my experience at least, I had many errors spread widely apart (separated by as much as 10 minutes) and by that time I would have closed any new windows that popped up. So I was thinking maybe we should show the error messages on the Downloads tab itself instead of in a new window. We could add a new column -- "Last error" or "Status" perhaps -- that was normally blank but showed the last error message if there was an error. But since we would want it to retry failed downloads, it could just stay there in the queue. The Error column could also say when it was scheduled to retry ("Retrying in 5 minutes...") and how many times it had already tried. So when the user gets around to checking on his downloads, he can see at a glance all the failed downloads (maybe they could be conveniently grouped at the top or in a separate pane) and choose to either cancel (if it didn't look like an error for which retrying would likely help) or just leave it there to let it auto-retry. See also: Bug 137 - Auto retry downloads Bug 361 - Advanced pause and resume support (particularly Restart/retry failed downloads) Bug 364 - Implement aggressive timeouts for feed updates -- Configure bugmail: http://bugs.gpodder.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes. _______________________________________________ gPodder-Bugs mailing list [email protected] https://lists.berlios.de/mailman/listinfo/gpodder-bugs
