Re: [TSVN] Branch / tag and revision log dialog problems

Simon Large wrote:

> I see the branch / tag dialog now has 3 options:
>
> (*) Branch/Tag directly on the server (HEAD revision)
> ( ) Branch/Tag the working copy
> ( ) Branch/Tag from the revision ____
>
> I assume the 3rd option is also directly on the server, but it doesn't
> say so. Also, the order of radio buttons is server, WC, server. It seems
> more logical to put the 2 server options together. Another problem I
> have with the wording is that branches are always made on the server;
> it's the source that changes. Putting these 3 complaints together, maybe
> we could use something like this:
>
> Create Branch/Tag on the server from:
> (*) HEAD revision on the server
> ( ) Specific revision on the server ____
> ( ) Working copy
>
> It would be nice to have a Show Log button as a way of filling in the
> revision number.

Please file an issue about this. I don't have much time to work on TSVN
the next two or three days, so...

> Another problem I just found occurs when you try to create a branch
> directly from the Show Log context menu. It comes up with the exact same
> dialog box (that's good), but the selected revision number is not filled
> in and the radio button is on HEAD.

Wow! That's bad. In that case, we should even hide those options and
just show the revision instead!

Another issue please.

> In the revision log dialog, edit author and log message are looking good
> in the context menu. If I shift double-click on author, I still get the
> old edit author dialog. If I shift double-click on log I get nothing. If

Nothing? It should work as before. I'll have a look...

> I shift double-click anywhere else, I get compare with WC. IMHO shift
> double-click should do nothing, regardless of where you click.
>
> The edit-author and edit-log dialog both come up with 'Input' on the
> title bar. It would be useful to remind the user what (s)he is editing.

Good point. Another issue please ;)

> It might also be good to include a warning about changes to revprops
> being unversioned. It didn't matter before because the access was harder
> to find, but now it's easy for anyone to do. I know you have to set up a
> pre-revprop-change hook, but all the same ...

Oh no, please not. I really hate such warnings, because users tend to
just "click them away". The 'guard' against such changes is in the
repository itself, since you have to install a hook-script to make this
work. I think that should be enough.

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