It's actually a bug in WinMerge's command-line parsing. "C:\Program Files\WinMerge\WinMerge.exe" /r tested it in a few different locations, it seems to work ok, but I’m just wondering if removing the “ is going to cause me some problems in certan situations? This is the code I’m using in my WinMerge button. I’ve had this problem intermittently with WinMerge and wasn’t sure what was causing it, but after some testing I’ve found the procedure above causes the problem every time. If I close the lister and then navigate back to folder 1 and folder 2 and click the WinMerge button again WinMerge pops up with the correct paths and works ok. Left: D:\testfolder\folder 1" D:\testfolder\folder These are the paths that winmerge is getting. WinMerge pops up and says both my paths are invalid. Now I display folder 1 on one side and folder 2 on the other side of opus and click the WinMerge button. Then create a file or folder in each of the subfolders, anything will do. The subfolders must contain a space in their name. The bug can be reproduced by creating an empty folder and then creating two subfolders within that folder. I’m trying to pass the paths of a dual lister to the WinMerge software but I’ve come across a bit of a bug.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |