Project Monitor: Commits remain unread

[Oliver Kopp]

Hi,

I'm using the new Project Monitor. I assume that a bold font indicates
an unread commit. If I click on "Mark all as read", not all commits
are unmarked. One commit remains marked. It's a commit by me. In one
repository, it's the last commit, in another repository, it's a commit
of yesterday.

Another issue is that after clicking "Check now", the window showing
the revisions gets emptied. I have to click on the repository again to
get the list filled.

Finally :), "Open working copy in explorer" opens the parent path of
the working copy folder, not the working copy folder itself.

Does anyone stumble upon the same behavior?

context:
* TortoiseSVN 1.9.1, Build 26747 - 64 Bit , 2015/08/31 20:16:00
* Local Repository paths
* Paths end without backslash
* Paths not encoded, plain path as copied from the explorer window
* Own username listed in "Users to ignore"
* Windows 10

Cheers,

Oliver

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3136393

To unsubscribe from this discussion, e-mail: [users-un...@tortoisesvn.tigris.org].

[Stefan Küng]

On 08.09.2015 12:28, Oliver Kopp wrote:
> Hi,
>
> I'm using the new Project Monitor. I assume that a bold font indicates
> an unread commit. If I click on "Mark all as read", not all commits
> are unmarked. One commit remains marked. It's a commit by me. In one
> repository, it's the last commit, in another repository, it's a commit
> of yesterday.

A bold font also indicates the revision the working copy is on. So if a
revision stays bold, that's the revision your working copy was last
updated to.

> Another issue is that after clicking "Check now", the window showing
> the revisions gets emptied. I have to click on the repository again to
> get the list filled.

Yes: that's to ensure that after the check has finished the view is
properly updated.
But I'll see if I can improve that a little bit.

>
> Finally :), "Open working copy in explorer" opens the parent path of
> the working copy folder, not the working copy folder itself.

Yes, but the working copy folder is selected in the explorer list view
(the one on the right).
That's the behavior of the explorer if told to browse directly to a folder.

Stefan

--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest interface to (Sub)version control
/_/ \_\ http://tortoisesvn.net

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3136481

[GH vM]

Hello,

So the commit is still bold if it's read but it's the revision of the current working copy is a feature, not a bug?

If it signifies a different status than being unread, then it should have been a different marking, not the same as being unread.

I'd advise a separate column or some other place (like the actions column) to put an indicator that shows it is the current revision of the working copy (which is what I would have done in the first place).

It also messes up the view: the date column automatically restores to a width that can not accommodate the text in bold (after setting it to a correct width manually), and will cut it off, making it impossible to see the actual time of the commit (which is important, at least in my case).

This happens every time I open the window and have to click on the project in the left pane to see anything useful, I guess this has not been improved in the 6.5 years this issue has been known.

It is not dependant on the contents of the column, since the date/time format does not result in a big enough of a margin to not be able to select the correct width to accommodate the contents in bold.

Regards,

G

Op dinsdag 8 september 2015 om 19:58:06 UTC+2 schreef Stefan: