Deletes old files instead of Overwriting

[b2man63]

I have installed version 9.3. The OS is Windows 7.In the synchronization operation the old file is deleted and new file is placed in the backup folder. Instead I want the old file to be over written/updated with the new file to avoid heaping up of deleted files in the Recycle Bin.
Some improvements may be incorporated in your software in identifying the actually deleted file and a modified file. Then only it is easier to retrieve the accidentally deleted file from the Recycle Bin.
____________________________________________________________
|08/19/17 - BatchRun: Synchronization completed successfully
|
| Items processed: 3 (113 KB)
| Total time: 00:00:02
|___________________________________________________________

[09:38:31] Info: Synchronizing folder pair: [＜– Two way –＞]
D:\RSM
Z:\RSM
[09:38:31] Info: Updating file "D:\RSM\AFC plant wise\AFC plant wise.xlsx"
[09:38:31] Info: Moving file "D:\RSM\AFC plant wise\~$AFC plant wise.xlsx" to the recycle bin
[09:38:31] Info: Updating file "D:\RSM\STATUS OF PENDING ISSUES.pptx"
[09:38:31] Info: Synchronization completed successfully

[Plerry]

Apparently, "delete files" in your sync-settings (F8) is presently set at "Recycle bin".
If you have no need to have the option to recover your previous version, you can change that setting to "Permanent".

[b2man63]

Apparently, "delete files" in your sync-settings (F8) is presently set at "Recycle bin".
If you have no need to have the option to recover your previous version, you can change that setting to "Permanent".

If your suggested option is chosen, I will loose the inadvertently deleted files forever. So the software should be in such a way that, deleted files only should go to recycle bin and not the modified files.

[Plerry]

For FFS there is essentially no difference between the two.

If an existing file needs to be "modified" (in your words),
the existing file in the target location is renamed,
and the "modified" file is copied over from its source- to its target-location.
Upon successful completion of this copy action, the original (now renamed) file in the target location is deleted
according to the "delete files" setting, just like any file that "only" is to be deleted.

After all: what is the sense behind wanting/needing the ability to recover accidentally deleted files, but not accidentally modified files ...?

[b2man63]

I hope the developers of FFS might have got to my point what I am trying to emphasize.

[Plerry]

I expect your "point" is understood.
But you did not answer my (bottom) question about the sense behind your "point".
And in order to potentially trigger SW changes, at least the sense needs to be made clear.