Drag & Drop from search results copies the full path

[zer0]

Having not found anything in the help file or on the forum about this, I though I would ask...

Why does LMB drag and dropping an item from a search results tab in one pane to a tab in another pane cause the item to copied with its full path of the original location? For example, if search has found the file that I want in X:\BlahBlah\, LMB DnD to D:\Temp\ actually copies the item I want to D:\Temp\X\BlahBlah\. Why is this? I just want to copy the item, I'm not interested in the full path of where it is somewhere else. Is this is the default behaviour and, if yes, why?

[zer0]

Anybody?

[bdeshi]

Did check earlier. Couldn't confirm.
<wildguess>Probably due to a tweak.</wildguess>

[RalphM]

Sounds like there's a rich copy happening but I've got no idea why, wait for Don to chime in...

[admin]

Does not happen here.

Yes, looks like rich copy , but I don't see how this can possibly happen.

[TheQwerty]

Could it be?

Code: Select all

v10.70.0204 - 2012-01-10 14:40
    + Automatic Rich File Operations: From now on, any copy/move 
      operation (drop, paste, to new subfolder, etc.) will check whether 
      its direct sources are "rich" (= come from more than one folder), 
      and then offer to do a Rich Copy or Move instead of the standard 
      flat operation (where things might collide/merge).
      Note that "rich sources" typically come from recursive search 
      results or branch views.
      The rootpath for such a rich operation is the greatest common 
      parent folder of the sources.

[admin]

No, this only sets in when the dragged files are from differing sources, and it pops a prompt first. OT seems to talk about one item at a time only, and no prompt.

[TheQwerty]

I can recreate this in a fresh copy of 14.30.0400 by doing the following:

1. Create the following structure:
   C:\test\src\grue.txt
   C:\test\dst
2. At the command prompt subst 'C:\test\dst' to a drive letter:
   subst D: C:\test\dst
3. Enable 'Use Custom Copy'
4. In one pane navigate to drive you used in step 2.
5. In the other pane search Computer for grue.txt.
6. Once the search completes drag C:\test\src\grue.txt to the other pane.

At this point XY should have copied the file but it will place it at: W:\C\test\src\grue.txt.

[zer0]

Did check earlier. Couldn't confirm.
<wildguess>Probably due to a tweak.</wildguess>

It is not common for me to copy from search results, so I doubt I would have applied a tweak to affect its behaviour.

[bdeshi]

That was a wild guess. Besides I did look into the ini, no tweaks seemed related to the copy behavior you reported.

My wording should have been better. I should've said: "Could it be a tweak?"

[admin]

I can recreate this in a fresh copy of 14.30.0400 by doing the following:

1. Create the following structure:
   C:\test\src\grue.txt
   C:\test\dst
2. At the command prompt subst 'C:\test\dst' to a drive letter:
   subst D: C:\test\dst
3. Enable 'Use Custom Copy'
4. In one pane navigate to drive you used in step 2.
5. In the other pane search Computer for grue.txt.
6. Once the search completes drag C:\test\src\grue.txt to the other pane.

At this point XY should have copied the file but it will place it at: W:\C\test\src\grue.txt.

Cool, got it! Goes back to a feature added in v6.40.0020 - 2007-10-26 13:16 for Backup. It has been wrongly applied to Custom Copy ever since Custom Copy was added.