Page 1 of 2

Is this how custom copy is supposed to work

Posted: 28 Jun 2011 08:48
by vsub
When you try to make a copy of a folder and the destination is the same as the original folder,custom copy directly tried to put the files from the folder in the same folder as the original

Folder named 123 is located in folder named 1,then copy 123 and paste it in 1...this automatically tried to put the files from 123 there.

I know that there is an option in the context menu to put the files/folders in a new folder with the name you want(Paste Here in New Subfolder)but shouldn't XYP just create a new folder with some prefix(original name with some prefix)if the the source and destination is the same

Normally with those conditions a folder will be create with a name "copy of" but custom copy directly tried to put the files inside the folder and then ask what to do with the files that have the same name.

Re: Is this how custom copy is supposed to work

Posted: 28 Jun 2011 08:53
by admin
Yes, correct. The "on name collision" only regards files, not folders. This is the behavior of XY's backup function (which is the ancestor of Custom Copy) ever since. Up to now nobody ever complained.

Re: Is this how custom copy is supposed to work

Posted: 28 Jun 2011 09:01
by vsub
Ok

Re: Is this how custom copy is supposed to work

Posted: 28 Jun 2011 13:20
by highend
Up to now nobody ever complained.
<- complains about it.

Creating a fast copy of a selected folder to the same basedir (but with the added suffix extension) isn't possible any more (and yes, I'm used to it) with custom copy ;)

Re: Is this how custom copy is supposed to work

Posted: 28 Jun 2011 13:33
by admin
highend wrote:
Up to now nobody ever complained.
<- complains about it.

Creating a fast copy of a selected folder to the same basedir (but with the added suffix extension) isn't possible any more (and yes, I'm used to it) with custom copy ;)
Yes, I think something should be done. I could add a another dropdown "On folder name collision" analog to "On (file) name collision". v10.10 will see this.

Re: Is this how custom copy is supposed to work

Posted: 28 Jun 2011 13:41
by highend
I could add a another dropdown "On folder name collision" analog to "On (file) name collision".
That's probably the best option :)

Re: Is this how custom copy is supposed to work

Posted: 28 Jun 2011 14:01
by Borut
Yes, but maybe the priority of this could be upgraded even more.

Look at it this way: I am so fond of Custom Copy that I have promptly decided to use it for all copy operations. I would expect that a lot of people will be happy to do so at the time the version 10 is out. Therefore such an anomaly from an expected operation is - in my view - an absolute no no for XY.

I share highend's opinion: "On folder name collision" is the way to go.

BTW, the nonexistence of the central logging folder for Backup (I wrote about that already) is for me a show stopper for partially replacing my use of Beyond Compare with the XYplorer's Backup when I do some backup operations.

Re: Is this how custom copy is supposed to work

Posted: 28 Jun 2011 14:43
by admin
Borut wrote:Yes, but maybe the priority of this could be upgraded even more.

Look at it this way: I am so fond of Custom Copy that I have promptly decided to use it for all copy operations. I would expect that a lot of people will be happy to do so at the time the version 10 is out. Therefore such an anomaly from an expected operation is - in my view - an absolute no no for XY.

I share highend's opinion: "On folder name collision" is the way to go.

BTW, the nonexistence of the central logging folder for Backup (I wrote about that already) is for me a show stopper for partially replacing my use of Beyond Compare with the XYplorer's Backup when I do some backup operations.
Yes, I have to agree.

I just wonder if a simpler solution would be enough. I'm thinking of a checkbox "Rename folders on collision" (instead of the big dropdown). If checked then all copies of folders in your selection are auto-renamed (incremental suffix) on collision. Else overwritten. Less hassle for me and the user.

Central logging folder for Backup: yep, I see what i can do...

Re: Is this how custom copy is supposed to work

Posted: 28 Jun 2011 15:01
by Borut
I just wonder if a simpler solution would be enough. I'm thinking of a checkbox "Rename folders on collision" (instead of the big dropdown).
Yes, that would be enough, at least for me. So, for Custom Copy the factory default could for instance be checked and for the Backup unchecked. I think that would mirror the most intended initial usage of these two special copying possibilities.

It is conceivable that there would be users spoiled with your "On (file) name collision"-flexibility, who would like to have the same for folders. But, at least for me, that can wait.

Thank you!

Re: Is this how custom copy is supposed to work

Posted: 28 Jun 2011 15:21
by highend
I just wonder if a simpler solution would be enough. I'm thinking of a checkbox "Rename folders on collision" (instead of the big dropdown). If checked then all copies of folders in your selection are auto-renamed (incremental suffix) on collision. Else overwritten. Less hassle for me and the user.
It depends.

E.g.:
The folder "D:\Temp\abc" has three subfolders (def, ghi, jkl)

If you are in "D:\Temp", select "abc", strg +c, strg +v and set the checkmark for "Rename folders on collision", would this
a.) only rename abc to abc<suffix> and doesn't rename the subfolders
b.) rename all folders (including subfolders) to <foldername><suffix>

or would b.) only happen when the "Do this also for the next collisions" is checked, too?

If a.) is the case I have nothing against the first, quick solution (add checkbox now and a dropdown with 10.x version).

Re: Is this how custom copy is supposed to work

Posted: 28 Jun 2011 15:29
by admin
highend wrote:
I just wonder if a simpler solution would be enough. I'm thinking of a checkbox "Rename folders on collision" (instead of the big dropdown). If checked then all copies of folders in your selection are auto-renamed (incremental suffix) on collision. Else overwritten. Less hassle for me and the user.
It depends.

E.g.:
The folder "D:\Temp\abc" has three subfolders (def, ghi, jkl)

If you are in "D:\Temp", select "abc", strg +c, strg +v and set the checkmark for "Rename folders on collision", would this
a.) only rename abc to abc<suffix> and doesn't rename the subfolders
b.) rename all folders (including subfolders) to <foldername><suffix>

or would b.) only happen when the "Do this also for the next collisions" is checked, too?

If a.) is the case I have nothing against the first, quick solution (add checkbox now and a dropdown with 10.x version).
a) :)

Re: Is this how custom copy is supposed to work

Posted: 28 Jun 2011 15:56
by highend
admin wrote:a) :)
Tested with v9.90.1113 and checkmark set: Works as expected. Are there really cases where a future dropdown field in the progress status would be needed for folders now?

Re: Is this how custom copy is supposed to work

Posted: 28 Jun 2011 15:58
by admin
highend wrote:
admin wrote:a) :)
Tested with v9.90.1113 and checkmark set: Works as expected. Are there really cases where a future dropdown field in the progress status would be needed for folders now?
Probably not. Keep it simple.

Re: Is this how custom copy is supposed to work

Posted: 28 Jun 2011 16:11
by CodeLobster
always wanted such a feature but days are gone when i thought it should be possible.

thank you all guys!!!

Re: Is this how custom copy is supposed to work

Posted: 01 Jul 2011 10:20
by admin
I just rethought this Rename folders on collision feature and I think it's (partly) nonsense.

The OP said it all:
vsub wrote:When you try to make a copy of a folder and the destination is the same as the original folder...
If this condition is met then there is no other reasonable option than renaming the folder! It would be total rubbish to copy a folder into itself. :arrow: So I will change the current behavior: In this case the folder is also renamed when "Rename folders on collision" is not ticked.

If this condition is not met then why would you rename the folder? Normally you would want to overwrite the target folder. At least this is the only option that Windows Explorer offers ever since so everything else is pretty revolutionary for a copy replacement.
CodeLobster wrote:always wanted such a feature but days are gone when i thought it should be possible.
So, what feature exactly did you mean by this? Why is it so exciting?