Otherwise, it can cause incorrect compare results.Īs I needed to check the full files, I wanted to disable these limits. This option should be enabled only when you are sure any differences are in the first part of the file. If no differences are found before the Quick Compare limit is reached, then the files will be marked as identical. If the limit is set to for instance 4 MB, then WinMerge will only read the first 4 MB of a file.
This option sets the limit when WinMerge should stop comparing. This "naturally expected" behavior is also what is stated in the documentation:
I was expecting that with these settings only the first N bytes are compared and if they are equal, the rest of the files are skipped and the files are marked equal. Then, I noticed the "Quick compare limit (MB)" and "Binary compare limit (MB)" settings. I went to "Options > Compare > Folder", and first I changed the compare method to "binary contents", which is faster than "full contents" and "quick contents", and perfect for my use case as I'm only interested in checking byte-equality, and don't need the filters, diffs, etc. Use case: I was configuring WinMerge to compare two mirrored folders by byte-content, to check for data corruption.
0 kommentar(er)
