Move existing copy/move job to queue

tha_man · Post by *tha_man » 2007-06-17, 21:06 UTC

Many times I begin to copy some big file, but a minute later I need to copy another one. So I would like to put it in queue, because starting two such jobs at the same time is not a very good idea, performance-wise (especially from DVD). But since I didn't put the first job in the queue, I now only have two options:
1. wait for the first job to finish
2. cancel it, and start it again in queue

So I would really like to be able to put the existing file operation job in the queue. Any chance for this option?

Post by *Hacker » 2007-06-17, 21:40 UTC

Why not copy / move in the queue by default?

Roman

MacQ · Post by *MacQ » 2007-06-21, 17:15 UTC

Is this now possible?

Post by *petermad » 2007-06-21, 19:28 UTC

Is this now possible?

04.04.06: Added: wincmd.ini AlwaysCopyInBackground=2 -> Always try to copy in background transfer manager with F5-ENTER. F5-F2 will copy normally then (button is changed)

see also:
AlwaysPackInBackground=2
AlwaysUnpackInBackground=2

wanderer · Post by *wanderer » 2007-06-21, 20:39 UTC

tha_man wrote:So I would really like to be able to put the existing file operation job in the queue. Any chance for this option?

Sorry i don't think its possible. Someone else had asked the same thing in the past (maybe me, i don't remember) and if i remember correctly, Christian had said that it can't be done because the two ways of copying (queue and background copy) are two different threads so the operation cannot be transfered from one thread to the other. Search the forum a little, you may find the post...

I'd suggest petermad's way too. I use it.

StatusQuo · Post by *StatusQuo » 2007-06-23, 21:49 UTC

How about a new option for the queue:

Code: Select all

[ ] Wait until running copy actions are finished before starting this queue.

(Probably better as value in the INI.)
This would have the same/requested effect, wouldn't it?

MacQ · Post by *MacQ » 2007-06-24, 09:56 UTC

How about using the same shortcut for adding to queue as for the operation.

Example: F5 once for copy dialog, then once again for queue (instead of F2).
For F6 it would change correspondingly (F6 for queue).

This would be much faster as you would only have to press F5 or F6 twice, instead of going all the way to F2.

StatusQuo · Post by *StatusQuo » 2007-06-25, 21:50 UTC

MacQ wrote:press F5 or F6 twice, instead of going all the way to F2.

You mean F5 <ENTER> F5 (or the same with F6), don't you? Because repeatedly pressing F5 or F6 is already in use for selecting parts of the target name in the dialog.
To avoid confusing myself (or accidentally adding something to the queue), I consider F2 as "to background" shortcut to be not that bad.

Yuta · Post by *Yuta » 2007-06-29, 17:11 UTC

IMHO I think the bottomline is that noone really cares the difference between background a queue modes. Except that on background you have a progress bar (which I love).
Why not giving the queue mode a progress bar as a per job basis?. I'd really like to have it.

Now comes my big suggestion:
If there is a running copy operation, the background button actually can put it on the queue.
This way background and queue copy modes would be the same thing.
It would be nice also that once the queue is open, the following copy operations should go to the queue by default.

What do you guys think of this solution?

Total Commander

Move existing copy/move job to queue

Move existing copy/move job to queue

Re: Move existing copy/move job to queue