I have used WinMerge for years programming in several languages for several employers, it has become an invaluable part of my toolkit.
BUT . . .
With my current employer, we have several programmers maintaining the same (relatively small number of) projects written for the most part in VB6. Visual Sourcesafe is used for control, and I have implemented a 'safe' procedure for merging differences between my working version and the sourcesafe version. The projects, whilst few are massive. and a recursive folder compare of the project takes some time. I'm not worried about that, it's expected on a large folder tree. However what I find so irritating is, having spent some time checking file differences to see which way, or whether to merge, I click on the icon to close window. This is so close to the 'close application' icon on the form titlebar that a slight misplacement of the mouse means that the application closes (without warning), meaning that the scan has to be redone!
PLEASE provide at least the option to be warned when exiting the application, so that fumble fingered users can say WHOOPS!
Whilst I'm at it, feature request 1647433 from zamescurran has my vote.
When comparing VB6 source, Winmerge has a habit of insisting that a file has several differences at a po1nt where the only difference is that a new function or sub has been added. This has the knock on effect of offsetting file positions, and causing erroneous differences to be reported in the remainder of the file. Ideally some means of telling the diff engine that comparison should restart at a stated point in each file would be brilliant. (obviously this should cater for multiple such points in the file(s). I don't see it being necessary to 'remember' these file offsets between comparisons, because further changes will have been made by then.
Thanks for reading this epic (if you did)