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

Re: compare properties changes

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Fri, 20 Apr 2012 21:40:09 +0200

On 20.04.2012 10:21, Oto BREZINA wrote:
> Dear Stefan,
>
> On commit dialog (may be in CfM and other too) you can see all changed
> files and dir. You can see that poperty has been changed.
> You can double click to see thoses changes what is great however:
> * when that file have lot of changed properties and file is changed
> too double click open lot of T-Merge window. It should be better to
> choice what you really want to see

It only shows the changed properties.
What would you suggest the UI should look like for this?
Maybe a new dialog with a list of changed properties where doubleclicks
then open TMerge?

> * you can double click on greyed external files to see diff, but even
> context menu apears on right click 'compare with base' do nothing.

Fixed in r22816.

> * file compare is open even there is change only in property - I
> expect to open only changed properties

Yes, that's by design. The same way you can double click on unversioned
files and TMerge opens.

> * when T-Merge is open with property, property can be edited, but not
> saved
> I expect either set right panel as readonly or allow changing
> properties on the fly

We had that once. But people complained: they still want to edit the
files, because they still can save the files to somewhere else.

> BTW- can you add switch readonly to ribbon (for every/active view)? I
> would like to implement edit for both/all views.
> I tried to find way how to add it, but I use VS only for TSVN so I'm not
> very familiar with it.
>
> I guess there should be three states.
> Readonly not changable RO-disabled - propeties, base, remote revision,
> other temp
> Readonly but can be changed RO - comparing two files left one default
> Writtable WR - right default
>
> Not sure about tripane view, but probably only one would be editable as
> is now.

Do we really want this?
If we do, we have to make some way to still allow editing, maybe via a
new button/menu (e.g., "make editable").

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2950280
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-04-20 21:46:08 CEST

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