Hi Stefan,

Thank you for the quick reply. I am on mobile - please excuse any typos in
my response.

> 1. Add a "Clear all errors" button.
> That already exist. Shift-click the "Mark all as read" button to clear
> the errors.
> Obviously that functionality is not too obvious to find. Maybe an
> alternative like a button on the the project page for projects which
> have an error (aka: clear error / clear all errors) and/or an entry in
> the context-menu when right-clicking one of the entries with an error
> might be worthwhile adding?
>
Either proposal would improve the current state.
I had difficulty finding this functionality until you pointed it out. I
went back to check - it's in the documentation... even so, the UI features
should remain intuitive for the average user as much as possible.

>
> > 2. Add an option to auto-clear the error during the next scheduled
> > update, so the monitoring thread can check for updates if the server
> > is available again.

After doing some additional searching, I understand each project is
supposed to clear errors for scheduled update checks, unless the error was
an authentication error.
I am not sure what behavior I am really seeing, as I have not tried to
isolate it.
All I know is the symptom (projects not updating for long periods).
I will do some monitoring on my side and report back if my case is not
already covered.

-----
Regards,
Paul P.

>

-- 
You received this message because you are subscribed to the Google Groups 
"TortoiseSVN" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tortoisesvn/CAH1JgCJHWhEG87L%2Bu7ruhYA%3DUzxE_MN3ybm0pkpkgicEfj8mMw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to