Change of case of letters breaks automated synchronization [SOLVED]

[Synchronizator]

So I had these two folders synchronized

D:\test sources\Change Of Case
E:\test copies\Change Of Case


and they were monitored in real time by RealTimeSync, i.e. I had the one from drive D mirrored to drive E. But then I changed the name of first one from

Change Of Case


to

change of capitals


and as a result I got this pop-up message

The following items have unresolved conflicts and will not be synchronized:

Folder pair: D:\test sources synchro <-> E:\test copies
change of case: Items differ in attributes only
<- "change of case"
-> "Change Of Case"

You can switch to FreeFileSync's main window to resolve this issue.

So now in order to make them in sync I have to go to FreeFileSync and make a manual intervention. With one folder this could be doable- but what if at some point I will perform a mass change of capitalization of dozens of folders in multiple locations with conjunction with other changes? Am I suppose then, after starting temporarily turned off RTS , to go manually thorough them on a one-by-one basis, carefully reading and evaluating? Apparently yes, as a simple trick of just re-generating FFS_BATCH file and opening it in RTS does not work, as I still get the same error

And even it this trick would work, then a bigger question arises: what is the point of having RealTimeSync being run in the background, if it cannot deal with such simple change of letters from upper to lowercase? My goal is to have an automated mirror copy of [some] folders from D stored on drive E - so having to manually intervene on such account is just absurd. After all: in FFS I had chosen

D:\test sources


[i.e. its whole content] and not just

D:\test sources\Change Of Case


specifically. So what gives?

[Zenju]

Apparently you're using the "Update" sync variant. Folder names that differ in case are considered a "conflict", which is not overridden by a sync direction (like it is for "Mirror" or "Two way").

[Plerry]

If you are using the Update variant you can resolve above issue by using a Custom sync variant instead.
See here.
But note that that action then will apply to all conflics.

[Synchronizator]

Yes, that was the cause, it works for me now how I wished for

Thank you both

[Zenju]

There's a proper solution to the issue of renamed folders and the "update" variant in the next FreeFileSync version: The "update" variant will be based on "changes" in the same way "two way" is. Thous, FreeFileSync will detect which side was renamed and propagate this change without a conflict:
viewtopic.php?t=10594