XYplorer Beta Club

ADMIN EDIT: This thread was called "Custom copy doesn't work with drag'n'drop" and located in the Bug Reports section. However, it turned out that there wasn't a bug but the user simply was missing something that was planned anyway: Custom Move. So I hereby move this topic to the Wishes section.

I have set the following settings: But, when I drag'n'drop files I still get the 'There is already a file with the same name' dialog box.
The whole point of setting the 'OnNameCollision' settings is to prevent this.

iycgtptyarvg wrote:I have set the following settings:

Code: Select all

[CustomCopy1]
OnNameCollision=3
OnNameCollisionAsk=0
OnFailure=0
OnFailureAsk=0
RenameFoldersOnCollision=0
AskOnReadonly=0
RemoveReadonly=1
PreserveItemDates=1
ShowProgress=1
KeepProgressOpen=0
Logging=0
LogToDefaultLocation=1
Log=<xydata>\Log\CustomCopy_<date yyyy-mm-dd_hh-nn-ss>.txt
PopStats=0
SkipJunctions=0
SafeOverwrite=1
Verify=0

But, when I drag'n'drop files I still get the 'There is already a file with the same name' dialog box.
The whole point of setting the 'OnNameCollision' settings is to prevent this.

Your setting for On name collisions (Suffix increment to copy) works for me when copying through drag-and-drop. Stupid question, but you do have Configuration > File Operations > Custom Copy Operations > Use Custom Copy for all copy operations, enabled?

Yes, I do have that option set.

iycgtptyarvg wrote:Yes, I do have that option set.

1. What are the attributes of the destination file?

2. You simply drag-and-drop with the left button?

I just now realize I drag'n'drop the files on the same partition. This does a move operation.
Don't the settings work on move operations?!?

iycgtptyarvg wrote:I just now realize I drag'n'drop the files on the same partition. This does a move operation.
Don't the settings work on move operations?!?

*That* I forgot to ask...

Custom Copy currently only works for copy and backup; move was planned for 10.10 but didn't make that version. I assume it shouldn't be too long.

That is fantastic news, thank you so much.

nas8e9 wrote:Custom Copy currently only works for copy and backup; move was planned for 10.10 but didn't make that version. I assume it shouldn't be too long.

Hijacking the thread: Should Custom Move have its own independent configuration, or should it be just a clone of Custom Copy with deletion-of-sources-after-successful-copy?

Choice is always better than no choice. There are bound to be proponents of both ways.

.

admin wrote:Hijacking the thread: Should Custom Move have its own independent configuration, or should it be just a clone of Custom Copy with deletion-of-sources-after-successful-copy?

For me, one set of settings for both copy and move would work. The one thing I can imagine for others, is that they'd want to employ verification for one but not the other (e.g. because move affects the only copy of the file).

I think intra-volume moves should not be handled by Custom Move at all, since they are in fact rename operations and do not involve any copying of bytes.

admin wrote:I think intra-volume moves should not be handled by Custom Move at all, since they are in fact rename operations and do not involve any copying of bytes.

Custom Copy has other advantages (custom collision handling, preserving all item dates) that the Windows Shell routines don't offer. I do agree that verification is the one thing that's useless for intra-volume moves.

nas8e9 wrote:

admin wrote:I think intra-volume moves should not be handled by Custom Move at all, since they are in fact rename operations and do not involve any copying of bytes.

Custom Copy has other advantages (custom collision handling, preserving all item dates) that the Windows Shell routines don't offer. I do agree that verification is the one thing that's useless for intra-volume moves.

Oh yes, right!

admin wrote:I think intra-volume moves should not be handled by Custom Move at all, since they are in fact rename operations and do not involve any copying of bytes.

Please don't!

My use scenario is this:
I download comicbooks, and there are multiple people who scan them. So, comicbook xyz.cbr could be scanned by, say, 3 different people. When I move the files, I want them to be named xyz.cbr, xyz_01.cbr, xyz_02.cbr. Even though I move the files, I still have use for the renaming part.