Conflict? What conflict?

[JimboDimbo]

Me being a lazy bones, I like an easy life. [Syncovery 6.71c on Windows 7 SP1 & Windows 8.1, awaiting v7 patiently (beta 42 is a world record, isn't it?)].
I do my work in the day and sync my files to USB at hometime.
I often download some system logs at work ready for off-line review, and transfer them gzipped to my PC.
I unzip them with WinRAR, always forget to delete the default directory, so the file I want unzips into it's own directory (defaulting to the same name as the file).
Sync the files at night to my USB. No problem.
At home I realise I have an extra directory so I rename the unwanted directory to <whatever>.dir, copy the file of the same <whatever> name into the parent directory, then delete the <whatever>.dir directory. No problem.
Then sync back to the USB ready to go to work. Oops. Syncovery has a CONFLICT?
What?
I have a file on one side and a dirrectory of the same name on the other.
Yes. Well, I just copied the file I wanted into the parent directory and deleted the directory I didn't need. Why is there a CONFLICT?
Can Syncovery just handle it please? It recognises when I move stuff about without a quibble, tells me how many files are moved, deleted, whatever.
But cannot handle my moving a file into the place where a directory of the same name used to exist?
It happens loads of times because WinRAR defaults to creating a new directory, but probably also happens to loads of people who move stuff around. Unzipping often creates unwanted directories.
Isn't moving files up or down directories, just a move?
I looked for an Option in Advanced Settings/Folders for 'Warn only if a file overwrites a folder of the same name', but I don't see that option.
Conflict? What conflict?

[superflexible]

No, it can't handle that case. You need to resolve the issue manually. It's an extremely rare occurrence, and may point to some fundamental issues in your file system or naming policies if it occurs, so it's better to alert the user.

[JimboDimbo]

I don't agree that it's an "extremely rare occurrence".
Anyone who regularly zips and unzips files and folders will come across this. Especially if they use WinRAR or transfer files from unix systems.
You can still alert the user, but you don't have to force them to resolve it manually?
I totally understand that normally you do not want a single file to overwrite a directory. A file called windows being written to the C:\ folder might be a tad unwelcome.
I suppose I am asking if you could look at the smartTraking feature to see if it could detect that the file has been moved? Since it already does a good job of detecting moved files, this seems on the surface to be an easy additional check (file is replacing a folder of the same name containing the same file).
Thanks.

[superflexible]

I will think about it and put it on my list.

[superflexible]

•In Exact Mirror Mode, Syncovery can now replace files with folders and vice versa. Previous versions would not handle such cases and report them as a conflict only.