Possible two Bugs

Open discussion about WinMerge.

Possible two Bugs

Postby MrWinMerge2019 » Sat Apr 20, 2019 9:27 am

I have been using WinMerge for a long time.

BUG 01:
This was fine in version 2.14 but when I upgraded to version 2.16, this started to error out.

Here is an example of a directory name with ampersand in it. C:\zTest1 & Test2\
When I save the project as "Test.WinMerge", it save the above folder correctly in the XML.
<right>C:\zTest1 &amp; Test2\</right>

However, when opening the "Test.WinMerge" file, it cannot detect that directory because it dropped the space before the ampersand. When it opens, it some how converts to "C:\zTest1& Test2\" with no space before the ampersand. If I manually insert the space before the ampersand, then it works.

BUG 02:
When I did a folder comparison and sync a huge file (gb), WinMerge instance would freeze after the copy is completed. This happens with 2.16 64 bit version. It works fine with the 2.16 32 bit version.

These could be bugs or they could be me but I have been spending the last 5 hours looking into it.
MrWinMerge2019
 
Posts: 2
Joined: Sat Apr 20, 2019 9:17 am

Re: Possible two Bugs

Postby MrWinMerge2019 » Sun Apr 28, 2019 2:39 am

The new beta fix has some what fixed these but not all.

Hi,

Issue 01: The XML issue has been resolved for the 64 bit version but there are no compiled version for 2.16.3 (32 bit version).

Issue 02: When copied a 15 GB file, after it is done, still cannot access Winmerge as it gives the "thinking" icon. Works fine with the 32 bit version but still not the new 2.16.3 (64 bit version). I am on Windows 7 64 bit. Update: after 2nd attempt, 2.16.2 (32 bit version) takes only 1.5 minute while 2.16.3 (64 bit version) takes 5 minutes. 64 bit version finally give access back to WinMerge but takes a very very long time.

Thank you for fix!
MrWinMerge2019
 
Posts: 2
Joined: Sat Apr 20, 2019 9:17 am


Return to Open Discussion

Who is online

Users browsing this forum: Google [Bot] and 11 guests

cron