Announcement

Collapse
No announcement yet.

184141 Why no Size?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • 184141 Why no Size?

    I have

    . Folder handling
    . [x] Automatically scan subfolders in background

    of which Help says

    Automatically scan subfolders in background causes folders to be read in the background when a comparison is loaded. This way, folders can be colored appropriately before you open them. Top-level orphan folders can usually be colored and filtered without scanning, since they can only contain other orphans. Automatically scan top-level orphan subfolders causes these orphan folders to be scanned anyway, so that the folder's size is accurately reported
    yet my (non-orphan) folders have blank Size:



    What's up?

    PS Could you fix this forum's failure of leading spaces, some time? Thanks.

  • #2
    In Addition to checking "Automatically scan subfolders in background", you also need to check "Automatically scan top-level orphan subfolders" to display sizes for the orphan folders.

    From the help text you just quoted, "Automatically scan top-level orphan subfolders causes these orphan folders to be scanned anyway, so that the folder's size is accurately reported".

    If "Automatically scan subfolders in background" scans subfolders enough to generate a comparison. Top-level orphan subfolders can be marked as orphans without scanning their contents, so their contents are not scanned to improve comparison performance.

    "Automatically scan top-level orphan subfolders" forces the contents of top-level orphan subfolders to be scanned, this reduces performance but should display folder sizes. Even with this setting checked, folder sizes will sometimes not be displayed if the folder contains subfolders that Beyond Compare can't read due to permission restrictions.
    Chris K Scooter Software

    Comment


    • #3
      Originally posted by Chris View Post
      In Addition to checking "Automatically scan subfolders in background", you also need to check "Automatically scan top-level orphan subfolders" to display sizes for the orphan folders.
      Surely some mistake. These folders are not orphan folders - as the photo makes clear.

      Comment


      • #4
        The yellow color indicates the folder status is "unknown, open to scan".

        This can happen if BC doesn't have permission to list the contents of the folder or some of it's subfolders. Because not all of the folder contents are known, BC won't display a folder size.

        Are folder sizes displayed if you use the "Edit > Expand All", then "Edit > Collapse All" commands?
        Chris K Scooter Software

        Comment


        • #5
          Originally posted by Chris View Post
          The yellow color indicates the folder status is "unknown, open to scan".
          Help: "A folder will be yellow if auto-scan is turned off and you haven't opened the folder yet."

          Originally posted by Chris View Post
          This can happen if BC doesn't have permission to list the contents of the folder or some of it's subfolders. Because not all of the folder contents are known, BC won't display a folder size.
          It has permission.

          Originally posted by Chris View Post
          Are folder sizes displayed if you use the "Edit > Expand All", then "Edit > Collapse All" commands?
          Yup. Hence that I'm particularly keen to know why "[x] Automatically scan subfolders in background" is failing.

          Comment


          • #6
            Chris,

            This is a good puzzle to try to figure out. Please send a copy of your current Beyond Compare settings (Help > Support and Export button), along with a screen shot showing the full application window with the problem comparison to support@scootersoftware.com and I'll keep investigating this issue.

            Please include a link to this forum thread in your email.

            Also, it might help to know what type of drive s: is from your screenshot and what type of drive the other side is (internal drive, usb drive, network drive, etc).
            Chris K Scooter Software

            Comment


            • #7
              Thanks. YHM.

              > Also, it might help to know what type of drive s: is from your screenshot

              Network drive and local drive show the same.

              > and what type of drive the other side is (internal drive, usb drive, network drive, etc).

              The same drive - S: . The full screenshot is: http://i.imgur.com/z1yo5m2.png

              Comment


              • #8
                Chris,

                Thanks for the additional information, it explains what is happening.

                Beyond Compare treats comparing a folder to itself as a special case. If the same path is loaded on both sides, Beyond Compare will not scan subfolders until they are expanded. This is a performance optimization because if you load the same path on both sides, it is inherently a match.

                If you want to display folder sizes in Beyond Compare, make sure "Automatically scan subfolders in background" and "Automatically scan top-level orphan subfolders" are checked in session settings. Then load s:\ only on one side (leave the other side blank) and BC will build all folder contents and display sizes.
                Chris K Scooter Software

                Comment


                • #9
                  Originally posted by Chris View Post
                  If the same path is loaded on both sides, Beyond Compare will not scan subfolders until they are expanded. This is a performance optimization because if you load the same path on both sides, it is inherently a match.
                  Oops. Did someone forget about Size?

                  Originally posted by Chris View Post
                  If you want to display folder sizes in Beyond Compare, make sure "Automatically scan subfolders in background" and "Automatically scan top-level orphan subfolders" are checked in session settings. Then load s:\ only on one side (leave the other side blank)
                  Thanks for the workaround.

                  Comment

                  Working...
                  X