Thanks for your reply Martin, as always very clear :)
No need to think too much about it - for me it works now and anyway I usually use the portable version so my hacked compare script won't get overwritten on update. Creating a link is a good idea though.
Maybe a solution would be to have it in the ini, by default blank, and uses either Program Files or WinSCP sub-directory. Then let advanced users edit if they want.
Oh, and won't most compare tools behave the same? I.e. "tool.exe %file1% %file2%" ? So what tool used should not matter, just the path to a compare binary.
No need to think too much about it - for me it works now and anyway I usually use the portable version so my hacked compare script won't get overwritten on update. Creating a link is a good idea though.
Maybe a solution would be to have it in the ini, by default blank, and uses either Program Files or WinSCP sub-directory. Then let advanced users edit if they want.
[Configuration\CustomCommandOptions]
commonext\CompareFiles\Tool=WinMerge
commonext\CompareFiles\ToolPath=d:\bin\winmerge
Oh, and won't most compare tools behave the same? I.e. "tool.exe %file1% %file2%" ? So what tool used should not matter, just the path to a compare binary.