Simon Large wrote:
> Peter McNab wrote:
>> Did a commit and all went well. The icon status trickled *up* the
>> tree as it should and icons all visible where they should be.
>> I always find that up/down notion confusing, don't know if I'm too
>> used to looking a real trees or if it's a Northern/Southern
>> hemisphere thing but to me the direction to the root should be down.
>> Anyway, I'm still happy to be able to say I could find no fault and
>> so don't (personally) have to report a bug to Stefan and ruin another
>> So this leaves you with a local problem. It sounds like something
>> some others have experienced with Windows and the limited number of
>> Have a look at the FAQs at
> I think we are talking about 2 different issues here.
> Peter, are you pressing F5 to get this trickle up/down, or does the
> overlay update itself after a commit?
Not quite sure who is asking the question (Simon?), but after the commit
I don't recall having to press F5, the overlay icons updated themselves.
> When I commit (using latest nightly, r4939) the overlay remains at
> modified until I press F5.
> I think Peter is saying that the overlay is displayed correctly when
> you hit F5, which was previously buggy. He is not talking about
I think I'm saying it all worked like magic and I didn't even need to
initiate the refresh by pressing F5.
> Others are saying that the overlays don't update until you press F5,
> which they did in the past. They are not talking about correctness
> after F5.
I suspect these folk might still be on 1.2.6 or nightlies earlier than
> Rainer is talking about a 3rd problem where the overlays disappear
> completely after a commit.
> Is it possible (and a good idea) to make the overlay update
> automatically after a commit?
Funny though and oh Stefan you will really hate me for this, but-:
Today after installing yesterday's nightly 4924? then opening the
E:drive root folder containing scattered revisioned folders (by
alphabetic name) the process of displaying overlay icons to revisioned
folders *seemed to stop about half way through* , coming to grief on a
very small WC, not like it was off in huge WC recursing land.
It got ignored, so the opportunity to gather clues was lost, with me not
Tonight I installed rev 4939. The problem manifested itself again, even
though over an hour elapsed, between the install and opening the E:drive.
Looked at Task Manager and TSVNCache was dormant. Killed it and
everything came good.
Tried repeating the process by doing an uninstall-and re-install then
watching carefully but it all worked perfectly, (as it would).
So, something to think about. What might pause or halt the trolling and
then inhibit it from re-starting -or- if the trolling completed, what
might be needed to "refresh" the icon status.
Initially it looked like TSVNCache stopped trolling on discovering the
first no revisioned folder after scanning a sequence of revisioned folders.
But is the folder search order alphabetic anyway.? The get feeling from
the scan clues could be way off the mark.
And no, I didn't think to press F5. Funny how one gets out of the habit
so fast now it's not so needed.
Vely solly for not being a better tester today.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Nov 14 12:36:39 2005