If MOVE should move a file, which is locked by another process, two things seems to happen:
(1) The file is being copied to it's destination. This is unnecessarily time-consuming, if the destination-drive is the same one as the source-drive and might fail, if there is not enough space on the destination-drive (for these two files).
(2) If succeeded, the original file is tried to be deleted, which does not work, because it is locked. So an error-message is displayed, which makes sense. Unfortunately the copied file is not tried to be deleted, so there is an unwanted/unexpected duplicate file in the destination-directory.
So it would be nice, if a failure occurs (1) no copying would happen, if the original file could not be removed or at least (2) the file-state would be the same as before (= no duplicated file)
Thanks a lot,
Michael
(1) The file is being copied to it's destination. This is unnecessarily time-consuming, if the destination-drive is the same one as the source-drive and might fail, if there is not enough space on the destination-drive (for these two files).
(2) If succeeded, the original file is tried to be deleted, which does not work, because it is locked. So an error-message is displayed, which makes sense. Unfortunately the copied file is not tried to be deleted, so there is an unwanted/unexpected duplicate file in the destination-directory.
So it would be nice, if a failure occurs (1) no copying would happen, if the original file could not be removed or at least (2) the file-state would be the same as before (= no duplicated file)
Thanks a lot,
Michael