Thread: [Winmerge-support] wrong compare behavior: file vs. folder in 2.10
Windows visual diff and merge for files and directories
Brought to you by:
christianlist,
grimmdp
From: Richard M. <ric...@pi...> - 2008-10-22 13:57:24
|
Hello, I just updated from 2.8.x to 2.10. and to my (negative) surprise I have to assert that the compare behavior changed: in 2.8 one could choose a file first (with the explorer integration, right click -> Compare to), then a folder (right click -> Compare) and then WinMerge automatically compares the first file with a file in the 2nd folder, which has the same filename (very smart!). Unfortunately this doesn't work anymore in 2.10 instead the "Select Files or Folders" Dialog appears with the error message: "Cannot compare file and folder!". :-( In the settings dialog I couldn't find any option to change this behavior. Do I have to install 2.8 again or is there any other option? Thank you Richard |
From: Kimmo V. <ki...@wi...> - 2008-10-22 14:25:16
|
Hi, > I just updated from 2.8.x to 2.10. and to my (negative) surprise I have > to assert that the compare behavior changed: > in 2.8 one could choose a file first (with the explorer integration, > right click -> Compare to), then a folder (right click -> Compare) and > then WinMerge automatically compares the first file with a file in the > 2nd folder, which has the same filename (very smart!). > > Unfortunately this doesn't work anymore in 2.10 instead the "Select > Files or Folders" Dialog appears with the error message: "Cannot compare > file and folder!". :-( this was an unfortunate regression in the 2.10 release. The has been reported to our bug tracker as: #2138560 WinMerge 2.10.0 can't compare a file with a folder http://winmerge.org/bug/2138560 There is a fix for the bug, and the fix has been included in the latest experimental (2.11.1.5) for testing it. The fix will be included in the stable branch soon and I hope to release 2.10.2 stable release within two weeks. With this bug fixed. Right now, if you depend on this feature you can: a) try the latest experimental release b) switch back to 2.8.x until the 2.10.2 is released I'm sorry for the trouble, and that we didn't catch this bug until it went to the stable release. Regards, Kimmo |