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

[TSVN] Locking UI questions

From: Simon Large <slarge_at_slarge.plus.com>
Date: 2005-04-26 22:12:21 CEST

Hi folks,

I am just starting a description of the locking UI for the docs, and I
have a couple of GUI queries.

1. Should 'Get lock' be followed by '...' as there is a log entry dialog

2. Stealing and breaking locks seems too easy.
The option to steal a lock is offered immediately. Should it appear only
after an attempt to get a lock normally has failed, ie. Dialog stays
open and 'Steal lock' is enabled for a second attempt? I know it will
waste time if you already _know_ you need to steal a lock, but how often
does that happen? The same could apply to 'Break lock', where it only
appears in the context menu after a 'Release lock' has failed.

3. The lock status and error messages seem broken in places. I did this:

Lock Test.txt in WC1
Break lock in WC2
Check for (local) modifications in WC1 - initially correctly reports a
Contact repository - incorrectly still reports a lock

Attempt to release lock in WC1 and get this error message:
  Unlock failed: Test.txt
  Error: No lock on path '/Test.txt' in filesystem 'c:/temp/Repos2/db'
  Error: If you want to break the lock, use the "Check For Modifiations"

Line 3 (in this instance) should say something like:
  Error: The lock has already been broken from within another working

If the unlock failed because another WC holds the lock, you still want
the original message, but there should be a 'c' in 'Modifications'.


  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 Tue Apr 26 22:11:28 2005

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

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