Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.3.X, 2020.1.X
Votes
14
Found in
2017.4.1f1
2018.3.0a1
2019.1.0a1
2019.1.0a12
2019.2.0a1
Issue ID
1112495
Regression
No
[Collab] Unable to Compare Files or Folders when using WinMerge without choosing 3rd option
To reproduce:
1. Open a project from Collaboration
2. Make sure Revision Control Diff/Merge is set to WinMerge
3. Click "See differences" of any file from changes list
4. See that you can't compare since 3rd File or Folder options isn't set even though it's optional (3rd field contains "C:\e")
Actual result: Compare button isn't available because 3rd option
Expected result: It should be allowed to compare even without choosing 3rd File or Folder
Reproducible with: 2017.4.20f1, 2018.3.5f1, 2019.1.0b3, 2019.2.0a5
Comments (4)
-
AlanMattano
May 16, 2021 03:23
-
AlanMattano
Mar 12, 2020 17:55
As a workaround, in Winmerge, you need to clean one of the forms inputs to make it work before hitting enter. Delete 3rd path (string should be completely empty)
-
infernala1d
Nov 27, 2019 12:49
Just delete 3rd path (string should be completely empty)
-
DiegoWw
Sep 21, 2019 15:30
This is such a simple fix, to be this old. It is making a huge difference, my team is basically working around any conflicts for the lack of better diff tools.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Assigned font's bold/font-weight styles render using Default Font's assets when Default Font has corresponding style assets defined in TMP Settings
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
- Images are missing from the "Open the sprite editor" documentation for 6.0, 6.1 and 6.2
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a3