![]() ![]() Comparing the directory status per the last sync with the present status allows a straight forward way to detect not just added, modified or deleted files, but can also easily detect moved files. I am not the developer, but I'll give it a shot.ġ) sync.ffs_db files are not 'differences files', but database files, primarily used for bi-directional syncs and contain information about the directory and file status as per the last FFS sync. Why we can't we use the same settings (from "Comparison (F6)" tab: "File time and size", "File content", "File size") which we are currently using to compare files to be used also to detect file moves (instead of sync.ffs_db file)? ![]() What technical problems are causing that we are forced to use 'differences file' (sync.ffs_db) during sync to use file move detection feature?Ģ. I think that default one ("File time and size") won't make many false detections compared to just mistakenly recognition two different files as equal in normal mode (without file move detection)ġ. If files are considered equal due to for example "File size" selected in settings then there can be false positives in both scenarios: comparing file from internal/file1.txt vs external/file1.txt (because we could rename the same size file2->file1) and in detecting moved files from internal/file1.txt vs external/file2.txt (because they can coincidentally be the same size).but it is only a matter of user preferences when selecting which "file equality" variant user will select in settings. I expect that if the files are equal, so they have the same time and size (like selected in "Comparison (F6)" tab) then they shouldn't be copied and should be moved internally instead. 12_55_09-_FreeFileSync 10.7 – Folder Comparison and Synchronisation.png (52.81 KiB) Viewed 2442 times ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |