Uploaded image for project: 'Sourcetree For Mac'
  1. Sourcetree For Mac
  2. SRCTREE-3910

No Preview Available in side-by-side diff for binary files

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • Next minor release
    • 2.3.1
    • None
    • None

      A long, long time ago, SourceTree would show both the old version and new version for binary files with a valid QuickView (eg. images). Now, it only shows the After, and the Before always displays "No Preview Available". There is a button labeled "Open" underneath it that does nothing.

          Form Name

            [SRCTREE-3910] No Preview Available in side-by-side diff for binary files

            Thank you for the report, we've addressed this for our next beta and its subsequent release.

            Brian Ganninger (Inactive) added a comment - Thank you for the report, we've addressed this for our next beta and its subsequent release.

            Summer added a comment - - edited

            I am also seeing this issue, had no issues in an older version (really old version cant remember the number). My team uses enough binary files that this becomes extremely inconvenient real quick.

            Summer added a comment - - edited I am also seeing this issue, had no issues in an older version (really old version cant remember the number). My team uses enough binary files that this becomes extremely inconvenient real quick.

            Ed Marty added a comment -

            Note: viewing the history (Right-click->Log Selected...) allows me to view the state of an image at each commit in the "After" section (but the "Before" section is still empty)

            Ed Marty added a comment - Note: viewing the history (Right-click->Log Selected...) allows me to view the state of an image at each commit in the "After" section (but the "Before" section is still empty)

            Ed Marty added a comment -

            We're using a locally-hosted Git repository.

            Ed Marty added a comment - We're using a locally-hosted Git repository.

            That usually means there was a problem resolving the revision-specific path to get information (no preview or file size available) Are you using Git or Mercurial?

            Brian Ganninger (Inactive) added a comment - That usually means there was a problem resolving the revision-specific path to get information (no preview or file size available) Are you using Git or Mercurial?

            Ed Marty added a comment - - edited

            All binary files, including all image formats, exhibit this issue for every commit where they have changed. I have attached a screenshot.

            Ed Marty added a comment - - edited All binary files, including all image formats, exhibit this issue for every commit where they have changed. I have attached a screenshot.

            Supported/identified images are shown, including those managed by Git LFS. The 'binary details' view is the default case otherwise. We have not used "quick look" style that I'm aware of. Please attach files that are exhibiting the issue. Thanks.

            Brian Ganninger (Inactive) added a comment - Supported/identified images are shown, including those managed by Git LFS. The 'binary details' view is the default case otherwise. We have not used "quick look" style that I'm aware of. Please attach files that are exhibiting the issue. Thanks.

              Unassigned Unassigned
              fd6da39e13dc Ed Marty
              Affected customers:
              2 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: