I mount a HDD to drive letter O:. I create a new folder at the root of O drive O:\Test. I then copy a file from a different drive called Test1.mkv to the root of O drive and then pause it. I then copy another file from another different drive called Test2.mkv to the folder O:\Test. The file is queue as expected. I now mount the HDD to a folder at C:\Mounts instead. I repeat the copy operations as before. It's not properly queued and both ends up running simultaneously. I don't think that's the intended behavior.
The automatic copy queue is based on drive letters.
It's also not clear what the queue should do of the target has multiple mount points below it, pointing to different drives. Which drive would it use to queue then? There is no right answer there.
There's a script event if you want more complex queue logic. e.g. If you want copies below a certain path to be queued together, you can do that.
Ah that makes sense. I have now modified the hotkey for Paste with Clipboard PASTE COPYQUEUE=MyQueue,quiet,shift,none. So I can completely ignore the queue when I hold the shift and for every other time, force queue it. To confirm something, if I were to use Clipboard PASTE COPYQUEUE=MyQueue,quiet,shift, does that mean that if I were to hold shift, I'm leaving it to the algorithm to determine whether it should queue the operation or not? Also is there any way to apply that COPYQUEUE to the drag and drop?
I don't know what that will do, to be honest. Try it and see. 
You could always use @keydown instead to make the button/hotkey run completely separate commands based on the shift key state.
If we are talking about a hotkey (e.g. Ctrl-V) then you'd probably want to set up a separate hotkey for the Shift state (e.g. Ctrl-Shift-V).
Yes, drag & drop actions can be edited via Settings > File Types. You'd normally want to edit All Files & Folders if you want to change how everything behaves.
1 Like