It would be useful to know before (and maybe also after) starting Sync,
the "bottom line"/ resume/ balance of doing sync:
Bytes added - bytes deleted.
(Including the difference of the (to be) replaced files' size).
Benefit:
Before Sync:
I can tell if free space on destination suffices.
After Sync:
General useful, but also to assess how quick destination will be filled in future.
[REQUEST] Show resume (bytes added vs. deleted) after Compare run
- Posts: 36
- Joined: 30 Jun 2025
-
- Posts: 4866
- Joined: 11 Jun 2019
+1
I know you can use filters to show bytes per category, but, hiding 'updates' to avoid counting 'renames'/'moves' in the data usage will also hide updated files that are smaller/larger than the original, thus being inaccurate. Filter/showing just the additions and deletions will provide accurate numbers respectively, but then you have to do math and being more verbose would be a nice quality of life feature
I know you can use filters to show bytes per category, but, hiding 'updates' to avoid counting 'renames'/'moves' in the data usage will also hide updated files that are smaller/larger than the original, thus being inaccurate. Filter/showing just the additions and deletions will provide accurate numbers respectively, but then you have to do math and being more verbose would be a nice quality of life feature
- Posts: 36
- Joined: 30 Jun 2025
2 additions to my suggestion:
If a Compare run should reveal that the "bottom line" of syncing
would exceed free space on dest: Pop a message box and...
If a Compare run should reveal that at some point of the Sync process
(replacing small files by larger ones, generating tmp files etc.)
there will be an "overflow" of dest: Pop a message box and...
If a Compare run should reveal that the "bottom line" of syncing
would exceed free space on dest: Pop a message box and...
If a Compare run should reveal that at some point of the Sync process
(replacing small files by larger ones, generating tmp files etc.)
there will be an "overflow" of dest: Pop a message box and...