[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: intl3_svn.dll & another TSVN dlls

From: Daniel Posey <daniel_posey_at_hotmail.com>
Date: 2007-05-23 15:46:43 CEST

From: "Stefan Küng" <tortoisesvn@gmail.com>
Subject: Re: intl3_svn.dll & another TSVN dlls
>

> On 5/23/07, George Hazan <george.hazan@gmail.com> wrote:
> > I don't think that this option does anything with these DLLs. At least I
> > can't see any visible difference.
>
> http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/src/TortoiseShell/IconOverlay.cpp
> right at the top we check whether the process name is "explorer.exe"
> and bail out if it isn't.
> Ok, that of course means the dll's are already loaded, but they're not
> used.
> Problem is: the *shell* loads our dll, and we can't tell the shell not to.

I tested this with Notepad. When using File | Open, TSVN loads the same
regardless. You also still show your normal context menus. Of course, this
setting is about overlays. But you, Stefan, did bring it up.

This is where a small (8-20k) dll would be useful. It could check a
setting, probably a new one, before using true dynamic linking with
LoadLibrary() to load your main dll. Preferably, this small dll would have
no reference even to c libraries. With Notepad, on WinXP, having TSVN
installed adds about 1800k of additional "Mem Usage" to File | Open. I
don't know how much of this is true memory consumption and how much is
actually shared code with the same dlls in other processes. Any idea which
columns in taskmgr or procexp make this distinction?

While certainly not urgent, it might be nice. I would do it myself, but I
can't get to it right now.

DP

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Wed May 23 15:46:45 2007

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.