When comparing some files are not detected

Get help for specific problems
Posts: 12
Joined: 16 Sep 2017

kdaej

Hello,

When comparing some files are not detected in the left directory but they do exist.

How can it be ?

Thanks
User avatar
Posts: 4056
Joined: 11 Jun 2019

xCSxXenon

Check filters in the settings and also check the filters at the bottom of the compare screen. This can show/hide different items/actions.
Posts: 12
Joined: 16 Sep 2017

kdaej

There are no filters, only the standard ones
\System Volume Information\
\$Recycle.Bin\
\RECYCLE?\
*\thumbs.db

The files which are not detected are pdf, jpg or png files, some of them, not all

Whatever the filter, for each file listed on the right side, I should see the matching one on the left side.

Update or mirror, it's the same, but if I synchronise with the mirror mode, then undectected files on the left side will be replaced by ones on then right side which should'nt be (more recent on left side)
User avatar
Posts: 2451
Joined: 22 Aug 2012

Plerry

By default, files that are considered equal (as per the selected Compare criteria) are not shown in the Compare result window (because no action is normally required). If you want to see all files, make sure that all categories files are shown, using the icons mid below the compare results, including the "="-icon (equal).

> ... but if I synchronise with the mirror mode, then undectected files on the left side will be replaced by ones on then right side which should'nt be (more recent on left side)

If you run a Mirror or Update sync, the sync direction is always left-to-right, never right-to-left.
You can see that clearly in the FFS GUI Synchronization Settings window when selecting a sync variant and then view the different Compare result Categories and associated actions.
Only when using the Two-way sync variant or when specifying a Custom variant the sync direction may be right-to-left. For the Custom variant you may even specifically specify that newer files are to be overwritten by older files.
In the Two-way variant, only in very specific conditions "newer" files may be overwritten by "older" files, but only if those "older" files represent the most recent change to said, files. And from a sync perspective, that is then the correct behavior. See e.g. here.
Posts: 12
Joined: 16 Sep 2017

kdaej

Ok Thanks