checked-out file still showing as read-only in DiffMerge

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
Kirk Marple

checked-out file still showing as read-only in DiffMerge

Post by Kirk Marple » Sun Aug 08, 2004 5:20 pm

i've checked out a file from within VS.NET, and updated it, and then when i perform "Compare Versions" it pops up the DiffMerge tool.

it shows the baseline and edited versions of the file, but the right-hand file still shows as "read-only".

i've checked the actual file and it definitely doesn't have the read-only bit set in the file system, and i checked the Vault Client and it's definitely checked-out to me.

any ideas? is the cached state of the file munged somehow in Vault?

thanks!
Kirk

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Sun Aug 08, 2004 6:17 pm

By default, the diff tool brings up the files in read-only mode, even if they are writable on disk. There are /ro1 and /ro2 command line arguments in Tools->Options->Diff / Merge that you can remove to make the left or right files honor the read-write flag of the file itself.

Also note that our Diff Tool does not currently allow you to hand edit the file - you can only select a block of differences in the one pane and apply to the other pane.

Post Reply