Then again, maybe it would be best to simply use binary mode, and I'll have to give that a try with some test comparisons, but there are problems with that, mainly that it requires using not only a non-default, but also non-recommended mode to get good performance, which means most users aren't going to know to use it or won't know if they even should, just as I'm still unsure.
So it still seems it would be best to simply skip said files and leave those columns blank for them, with an option to alternate this behavior, in which case it would seem best to default it this way, and allow advanced users who actually have a need for this and therefore are willing to accept the performance hit to manually set it to the current behavior. Personally, I can't imagine why one would want to see that info on a file when there's no corresponding file, since the whole point is to check differences, and if there's no file to compare to, the difference is the entire file. While I don't think I've ever used those columns, requiring the user to hide them to speed this up means two things: they have to re-show them any time they want to use them (and possibly waste time running a scan again if they ran it with the columns hidden then realized they wanted to see them) and it would mean it would run slow by default unless the user knew to hide those columns.
I suppose that could be a solution, but I see a couple issues with it. in the ListView column of the folder comparison window. Probably the purpose is to display EOL-type, etc. What purpose is there for checking all that in full compare if there's nothing to compare against. Is "Ignore carriage return differences" applied Is "Ignore codepage differences" option applied? Modified date is used to determine the difference? Methodįile size is used to determine the difference? It also does not apply line filters, comment filters, or plugins.īelow is a table showing the characteristics of each comparison method. "Ignore case" option and "Ignore spaces" option are not applied. What's the downside to using binary compare
0 kommentar(er)
