WxFileName::Normalize follows links on windows if flags contains wxPATH_NORM_SHORTCUT (by calling wxFileName::GetShortcutTarget) I don't know if you have any maintenance releases planned for the near future, but if so, I think that's something you should fix.Īt least DiffMerge 3.2.0 and 3.3.0 are affected Workaround: enter "lnk" in the file suffix filter list. Took me some time to figure out what was causing it. Since my computer doesn't have a V drive, I got the circle-with-X-in-it icon, which was quite irritating, since I had no clue what was going on. I have encountered this while comparing two versions of a directory-tree, which - by accident - both had a link to some directory V:\. Double-clicking that entry yields an error message "Cannot compare items. It doesn't seem to matter if the actual folder exists, just as long as the drive is there.Ģ) If the drive of the target does not exists, DiffMerge will display an entry with a "red circle with X in it" icon. When displayed in the folder diff window, the path shown is something like ".\.\target-folder", or even "Z:\target-folder" if the link and the target are on different drives. lnk file as an empty folder with the path of the link-target.
lnk Windows Explorer link-files.ġ) If the drive where the link-target is located exists, DiffMerge seems to treat the. I have noticed that, when doing a folder-diff, DiffMerge does some strange things when you have links to folders in one or both of the compared folders.īy links I mean the normal.
0 kommentar(er)
