On Mon, 01 Nov 2004 21:58:21 +0000, Will Dean <svn@indcomp.co.uk> wrote:
> Anyway, I decided to have a look at SVN::UpdateShell, and see how it worked.
>
> Here's what I found: (Don't fix anything until you've read it...)
[snip]
> After a bit of Googling around, I tried adding
>
> SHChangeNotify( SHCNE_ASSOCCHANGED, SHCNF_FLUSHNOWAIT, 0, 0);
>
> at the end. This didn't work either *UNTIL*, I took the other
> SHChangeNotify calls out.
[snip]
> I am currently running with ShellUpdate just containing the one
> SHChangeNotify line. But this is not a panacea - here are my doubts:
>
[snip]
> 3. Can it cause huge folder updates (or even desktop icon redraws, which
> are so tedious). I don't see this here, but I might just be being lucky.
As it turns out, you're just being lucky. I found that the huge icon
update we force with that can block my shell for more than 5 seconds,
depending on the LAN connection and how busy the server is. I guess
the shell tries to update _all_ icons here, even those from items
located on the server.
Since this is very bad (hey, even I'm getting annoyed by this) I made
this an option (as of revision 1994). The default is off, which means
the old way is used (with some corrections/fixes). If the user turns
it on, this 'brute force' method is used - but then the user might
experience a blocked shell sometimes...
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Nov 29 10:23:41 2004