Simon Large wrote:
> Stefan Küng wrote:
>> Sven Brueggemann wrote:
>>> I still have trouble with overlay icons not reflecting the WCs state
>>> Yesterday evening, I killed TSVNCache, deleted it's cache file,
>>> checked out a new WC (without nested WCs this time) and changed two
>>> files in a subfolder. Then I switched off my monitor and left the
>>> machine alone.
>>> Coming back from work, I saw that the icon of the folder I checked out
>>> into is green, although "Show overlay icons recursively" is checked.
>> Even after you pressed F5?
> Before you added the status monitor, the overlay status would update
> automatically after TSVN operations (no need to press F5), but if files
> changed deeper down, even pressing F5 didn't work.
> Now the overlay status is always (I think) correct after you press F5,
> but it doesn't update automatically.
For me, this is only true *sometimes*. There are certain WC's that are
never right no matter how many times I press F5. For example, if I take
one of the problematic WC's and navigate to the root folder holding the
checked out WC (The non-versioned folder directly above the WC),
right-click the WC folder and select Commit I can then press F5 until my
fingers are raw, I'll never get the icon to go green; it will show the
modified icon. Running Cleanup won't even cause the icon to show as
green. I have to navigate into the directory and then back out before
it'll turn green.
That sounds so simple to reproduce, but the problem is, it doesn't do it
on other repositories. Most of my repositories have their overlay
update just fine when I press F5 after a commit performed in the same
manner. I've been unable to find any reason for the behavior which is
why I've never mentioned it before; I only mention it now since others
are also reporting mysterious problems. It seems to fairly consistently
affect the same repositories on my system, though. I've pretty much
given up on worrying about it since I can't find any reproducible recipe
for it. I admit, though, that I haven't done much investigating,
perhaps I should if I remember to do so and see if I can figure out why
some repositories do this while others don't.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Sep 2 23:55:59 2005