Clearing "could not connect" message marks an item read
Monitor your SVN repositories and notifies you on new commits
Brought to you by:
steveking
Menu
▾
▴
#68 Clearing "could not connect" message marks an item read
Originally created by: brucetwi...@gmail.com
Originally owned by: tortoisesvn
What steps will reproduce the problem?
1. Start with at least two monitored repositories, one with many unread items.
2. Disconnect from network
3. "Check now" and wait for update to try and fail
4. Click in the tree on the repository with unread items. Note the "unable
to connect message" appearing where the list would normally be.
5. Double-click the message at a position where an unread item would appear
in the list.
>>What is the expected output? What do you see instead?
I expected that the message would go away and the list would appear without
further action. What happens is that the item behind where I clicked has
been selected and marked as read.
>>What version of the product are you using? On what operating system?
1.2.0.296 on Vista Business
>>Please provide any additional information below.
The message is a good idea, but doesn't need to obscure the list. I think
it would be clearer to display the last date updated on the screen
somewhere (useful for other reasons), and an indicator if the last update
failed. Hovering on the indicator could display the existing message in a
tooltip, or just "Update at MM/DD/YYYY HH:mm:SS failed. Click for more
info.". Clicking the indicator would pop up a larger window with the
original text.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: tortoisesvn
starting.
Owner: tortoisesvn
Status: Started
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: tortoisesvn
Fixed in [r306], added the 'last checked' time shown on the info label in [r307].
Status: Fixed
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: brucetwi...@gmail.com
Thanks for the speedy fix and for implementing my suggestion. Looking forward for a
release with this included.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: brucetwi...@gmail.com
This has regressed in 1.5.1.382.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: brucetwi...@gmail.com
I guess I should explain myself. In 1.5.1.382, double-clicking the "could not
connect" message highlights whatever entry is under that position in the list, and
marks it read if it was unread.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: tortoisesvn
(No comment was entered for this change.)
Status: New
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: tortoisesvn
(No comment was entered for this change.)
Status: Started
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: tortoisesvn
Fixed regression in [r388]
Status: Fixed
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: tortoisesvn
(No comment was entered for this change.)
Labels: Release-1.6.0
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: tortoisesvn
(No comment was entered for this change.)
Labels: -Release-1.6.0 Milestone-1.6.0