Robert Roessler wrote:
> Stefan Küng wrote:
>> Simon Large wrote:
>>>> "TSVNCache.exe also uses these paths to restrict its scanning. If you
>>>> want it to look only in particular folders, disable all drive types
>>>> and include only the folders you specifically want to be scanned."
>>>> would be in order... or you could always make the software work that
>>>> way, of course. ;)
>>> Stefan, can you clarify how the drive types and exlude/include are
>>> supposed to interact. Something sounds wrong here.
>> If a path is in the include list, it shows overlays, no matter what is
>> If a path is not in the include list, then the path is checked whether
>> it is on an allowed drive-type. If it is not, no overlays. If it is on
>> an allowed drive-type, the exclude list is considered.
> Thanks for verifying that the *intended* behavior and the documentation
> agree, Stefan.
> But this does confirm (I think) that the *observed* behavior as reported
> in the first post of this thread represents a failure.
> To recap (I am getting good at this), a freshly-started copy of
> TSVNCache fails to display the overlays for folders containing SVN WCs
> in the "no drive types enabled but Include path(s) specified" case, but
> the overlays on contained files are present.
> Also, *disabling* all drive types and doing, say, a Refresh leaves the
> [project folder] overlays in place - only a fresh copy of TSVNCache
> exhibits the problem.
A few more details on this: I use the "DesktopProcess=1" registry
setting to cause Windows Explorer to run one process for the Desktop
and a separate process that handles all other Explorer instances (this
is sometimes useful when you are developing Shell Extensions).
I notice that the "normal" case of selecting at least one drive type
to have overlays results in TSVNCache starting up along with system
startup (or login), and being owned by the desktop explorer.exe.
However, when NOT selecting any drive type for overlays (relying
solely on Include paths), no TSVNCache instance is started until the
first Explorer window is displayed that includes an Included path. As
this type of startup yields the same results as killing the TSVNCache
instance after disabling all overlay drive types (TSVNCache being
started "late" and not being owned by the top-level Windows Explorer),
perhaps there is a connection?
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sun Jun 17 22:04:02 2007