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

SV: Re: AW: Minor feature request: move "Get Lock..." up in context menu for file with needs-lock

From: Hans-Emil Skogh <Hans-Emil.Skogh_at_tritech.se>
Date: 2006-09-19 10:52:23 CEST

>>> I'd say "Get Lock..." is the most used function on a file
>>> like this and it would save time if it wasn't in a sub menu.
> Therefore this request makes sense to me, because on a
> needs-lock file getting a lock is really the most used function.

What I understand it would be a quite big change if we want to change
anything in the way the "Look and Feel" dialog works. I think it will
eventually be necessary as SVN grows, but when the time comes I think we
should add multiple levels of sub-menus as a first step.

However I think it could be reasonable to add an exception for the lock
(without changing how Look and Feel works). As both you and Maurice has
pointed out, Get Lock is absolutely the most needed operation for files
that needs lock, but at the same time (hopefully) the least needed
operation for files without this property.

I do not know how readily available the needs-lock status is in the
Shell-extension, but assuming that we can get that information fast, a
possible implementation could look something like this:
Add a check box to the Look and Feel dialog with a text something like
"Promote Get Lock on files that need locks". A new registry key is added
to the registry indicating if this checkbox is checked or not. In the
shell cache, a check is added (where the context menu is created), that
will move "Get Lock" to the top level if both the file(s) selected need
locks and the reg-key is true.

Hans-Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Sep 19 10:51:44 2006

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.