Sven Probst wrote:
> Dear Stefan, dear users,
>
> as I followed this discussion I just want to add an idea, because I see
> the principle problem whether to trust in the status icon overlays or not:
> What about an overlay "don't know" ? This could give the user an
> impression, if the icons are reliable. As Windows offers file change
> notification (unfortunately I don't know details about this) it should
> quickly be possible to know, that the icon overlays are not reliable.
The problem with *every* status indication is that as soon as it's
fetched and shown, it can already be outdated again. Even during the
status fetching, another app can modify files. So while we crawl the
working copy file by file, as soon as we did a file, another app can
change that same file. Then when we show the "check for modifications"
dialog, that file would show up as "normal" (i.e. not modified), while
it actually got modified just before the dialog was shown.
Depending on the size of a working copy, fetching the status can take
several seconds, so it's not that unlikely of something like this to happen.
So, we would *always* have to show "unknown" or "don't know".
About the file change notifications: the cache already uses those. As
soon as it detects a change, it starts crawling that directory again.
But since the folder overlays indicate the status recursively, it then
also crawls all child dirs to update that recursive status.
So, for 'normal' sized working copies (I take the TSVN working copy as a
reference here), the overlays won't be off more than 1-5 seconds.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Thu Feb 2 21:41:04 2006