On 06/10/2007, Alex Hogan <alex.hogan@n-space.com> wrote:
> I am wishing that there was a way to see the lock status easily in the
> overlay - i.e. I wish to be able to see if another user has locked an
> item in the repository.
>
> I know this has been mentioned on the FAQ on the website, but I believe
> that was in the "constantly updating" overlay status that gets changed
> when you change a file yourself. The FAQ says that the lock status
> cannot be shown because then there would be constant connections to the
> server for each file in a folder to check the lock status.
Correct. The icons only reflect the local working copy status. They
will never reflect changes in the repository.
> I am wondering if the 'last known' lock status could be stored when one
> uses Tortoise to update his working copy - at that point I think all the
> files are being checked anyway, right? Or does Subversion provide
> Tortoise with a "changes" list that does not include the lock status?
> (I'm not a programmer by any means, so please forgive me if this is
> flamboyantly wrong.)
I'm not exactly sure myself, but even if an update did get the latest
lock information it would only be valid at the point of getting the
update, and would very quickly become stale. Displaying stale
information is not something we would want to do.
The best place to get the current status is the Check for
Modifications dialog, click on the check repository button, or in
settings->dialogs 2 make sure the 'check repository at startup' box is
checked.
> Right now I am trying to ensure that we don't lose any work by having
> the "requires lock" parameter set to on, but it is not as nice as seeing
> which file is locked or not, and certainly not easy for me to check a
> tree to see which files are 'in use.'
If you have binary non-merge-able files then you *must* use the
svn:needs-lock property to avoid lost work. Otherwise you can check to
see if a file is locked, and right after you check, someone else takes
out a lock. Now each of you thinks that he alone is working on the
file.
> For a bit of context - I am trying out Subversion with Tortoise for an
> art tree, not for code, so it's all binary files with no possibility of
> merging, and most of the users are artists and aren't all that technical.
This is certainly not an uncommon (double negative?) scenario. And
that is what the svn:needs-lock property was designed for. It requires
a change to your workflow, but it is much safer.
> Anyway, just firing of a few questions - I'm afraid I do not know too
> many other places to ask questions about Subversion with Tortoise.
This is the right place to ask questions, although it should really be
on the users mailing list, to ask for solutions rather than wading
right in with a feature request ;-)
Simon
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat Oct 6 23:28:08 2007