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

Re: [TSVN] RFE: Lock_and_open as a single command

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2005-09-08 19:12:48 CEST

Kalin KOZHUHAROV wrote:

> Ideas - plenty of them :-)
>
> In 5 seconds thoght, after all being in windoze, Ctrl+DoubleClick,
> Ctrl+Enter
> on a selected file or any other probably not used similar combination.
> Ctrl+DoubleClick - select and lock the file then normal Enter or one
> more DoubleClick to open it?

Well, that's not really possible. TSVN is a shell extension, yes, but
the shell doesn't provide a mechanism to interfere with the doubleclicks
on files (at least not without registering *all* filetypes and put TSVN
as the default application to open that filetype - and that's something
users would kill me for if I did that). We only have the context menu
where we can add our entries for *all* filetypes.

> I also find the long menu not too convinient, but I like the idea of a 2
> level menu.
> What about 3 level? If I can move Branching and related, merge, and
> probably some others
> (on my Gentoo machine now, I cannot check) to L3 I'll be happy.
> update, log, commit, lock/unlock are used 80% of the time; diff, browse
> - 15% of the tiem in our team.

That's an idea we should talk about further. Just providing a three
level menu isn't a problem. But how should the settings dialog look like
in that case? (the page where you can set which entries appear on the
top menu).

> BTW, while on locking and menus, will it be possible to have a single
> menu for lock/unlock?
> It is a context menu, so it should work as a toggle (be unlock if file
> is locked, lock otherwise).
> If a bunch of locked/unlocked files is selected, default to lock (the
> unlocked files).

We need both menu's (unfortunately). You see, it's not a requirement to
have the svn:needs-lock property set on files to actually lock them. So
the 'lock' entry must be on all files. If a file is already locked, the
'lock' entry is necessary because in that case it will steal the lock.
And you can 'unlock' a non-locked file because the file might be locked
in the repository but not in your working copy - in that case you will
'break' the lock.

Stefan

-- 
        ___
   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 Thu Sep 8 19:13:10 2005

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