SteveKing <steveking@gmx.ch> wrote on 04/13/2005 01:44:05 PM:
> While trying out the locking feature I gathered some more information.
> And a 'locked' overlay seems more and more something we shouldn't do:
>
> - the working copy only has the information if a file is locked by the
> working copy itself. No information about a file locked by someone else!
> - if the svn:needs-lock property is set, the file get's the readonly
> flag set, i.e. apps can't save such files anymore (as long as the
> working copy doesn't have the lock on such a file).
>
> The only thing what such an overlay could show is:
> - file is readonly
> But we don't really need an overlay for that - the explorer already has
> a built-in column provider to show the file attributes.
>
> So what do you guys think? Should we implement a 'locked' overlay at
all?
I do not really care if we do not have an overlay, especially in the first
version. But I have been following your discussions on the dev@ list and
I do not see what the problem is . IMHO, the overlay you would want to
see is if you held a lock on the file. This info is available in the
structure you get back, so you do not really need anything else. It would
be nice to know if someone else held a lock but that really isn't feasible
without a persistent server connection.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Apr 13 19:58:56 2005