Hi, I don't have an older version readily available to check if something has changed recently... but could have sworn from memory that the behavior I'm seeing is 'unexpected' compared to have done similar things in the past:
Source folder for both copy ops = D:\movies\ - and contains several large files I want to copy to several different folders on the same external USB drive
Dest folder 1 = F:\movies[b]dir1[/b]
Dest folder 2 = F:\movies[b]dir2[/b]
...start the copy to dir1, it runs. Start copy to dir2, it runs instead of being auto-queued. Expected? If I send the second copy to the SAME folder (dir1), then it's auto-queued as I'd expect. I guess those two results are explained by the manual description:
But it seems odd that this scenario of copying to different destination folders on the same (slow) external device wouldn't trigger auto-queuing. I know I can manually queue (and I probably will do so), it's more a curiosity about why it works this way and what difficulty there would be in 'making' auto-queue work as I'd have expected (and really, THOUGHT had previously been the case).
...HOWEVER, that a similar thing worked for you made me go back and check myself. There was indeed something I omitted because I just didn't see it making a difference, but this is what caused the failure to auto-queue:
Copy 1 == RMB Drop Menu from src-to-dest using the following drop menu action code: dopusrt /cmd copy here createfolder "{Rs|COPY to new folder...|{d}}"