Skip to content
← Code Compare

How can we improve Code Compare?

Code Compare

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Make the base pane read-only

When comparing a file against its base in version control, it makes sense for the base pane to be read-only. This way it makes it obvious which file is editable. Same with merging - the mine and theirs should be read-only and only the result file should be editable.

28 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Tony shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • George Birbilis commented  ·   ·  Report

    I was just merging a WPF and a Silverlight version of some code together and editing both sides was invaluable to me, so this should be easy to turn off if set by default

  • Tristan Grimmer commented  ·   ·  Report

    All three should be editable... sometimes you want to merge 2 files into the base... sometimes during an integration you may want to 'merge a diff' from one codeline into another. In short, there are some real-world situations where I wouldn't want my tool restricting me. Let perforce / scm decide what files are read-only. The question then becomes how will you deal with the RO attribute. The answer should be a choice between a) allow editing in memory and ask when saving what to do (overwrite/cancel) (that's how I have my VS set) or b) Ask what do do on first edit. Visual Studio puts a little lock symbol by the filename. Please don't restrict editing ability based on the arbitrary 'slot' a file is loaded into!

  • Neolisk commented  ·   ·  Report

    Mr Anonymous, do you seriously believe that adding an option is restricting the capabilities?

  • Anonymous commented  ·   ·  Report

    I would complain if this is removed. Being able to alter the base side of a diff is incredibly useful at times, such as with large, generated XML files. Being able to run the Edit.FormatSelection in Visual Studio is a dream.

    I wouldn't mind seeing this as an option, since clearly some people want it, but I'd like to point out that this is investing effort into restricting the capabilities of the tool.

  • Chad Kittel commented  ·   ·  Report

    Or at least make this an option, which is on by default (meaning read-only by default). I could see someone complaining if the feature is completely removed.