queuing transfers
Moderators: fgagnon, nikos, Site Mods
queuing transfers
hi to all,
when copying and moving sometimes i wish to copy a file to several places, then move / delete the original file in the last command.
is there a way for the queue to:
1) treat copy and move jobs as part of the same queue, i.e.
copy (F5 robust) file to location
copy file to another location using F5 again (using queue)
and lastly use F6 to move the same file to end location (using queue)
-
or have all copy, move, delete jobs as part of the same queue (robustly?).
or can this be done already and i've missed it?
regards,
Osei
At the moment it seems Robust copy and Move are separate when it comes to queuing
when copying and moving sometimes i wish to copy a file to several places, then move / delete the original file in the last command.
is there a way for the queue to:
1) treat copy and move jobs as part of the same queue, i.e.
copy (F5 robust) file to location
copy file to another location using F5 again (using queue)
and lastly use F6 to move the same file to end location (using queue)
-
or have all copy, move, delete jobs as part of the same queue (robustly?).
or can this be done already and i've missed it?
regards,
Osei
At the moment it seems Robust copy and Move are separate when it comes to queuing
Live life...
the queue operates on a fifo basis, so if you queue the move last, it will be last. To copy the same file(s) to multiple folders perhaps you are better off using the multi paste command (see paste special menu). This won't help you with your current question but it is easier than pressing F5 many times
thanks for the response.
is multi paste robust?
and the queuing idea could be looked at. yea there could be errors (i.e. trying to copy something that's already been moved to a different location earlier in the batch process), but that's what robust is for right? and of course if it was something urgent then you wouldn't use the queue.
a tick box somewhere would be nice
regards to all,
Osei
is multi paste robust?
and the queuing idea could be looked at. yea there could be errors (i.e. trying to copy something that's already been moved to a different location earlier in the batch process), but that's what robust is for right? and of course if it was something urgent then you wouldn't use the queue.
a tick box somewhere would be nice
regards to all,
Osei
Live life...
Huh, who put that there? :oops: Ok, so you win this time - but I'll get you yet Dr. Evil Developer! :twisted:nikos wrote:...if you tick the relevant box
(That said, it's still a bit naff that you covered your lazy arse by inserting an overwrite prompt even when it's not needed, just because you weren't in the mood to actually finish the routines properly - you do have a penchant for misusing MsgBox modals don't you? :roll:)
keeping robust and 'plain' paste separate is a good idea e.g. for UAC purposes
that's why drag=drop always remains 'non robust'
that's why drag=drop always remains 'non robust'
if you've already started copying or moving, would be nice to pause/add the #job to a queue.
from time to time i forget to press the queue button and have a load of jobs starting all at once. then i have to pause them and resume them manually. since the #job is in memory would be good to add to the queue system.
from time to time i forget to press the queue button and have a load of jobs starting all at once. then i have to pause them and resume them manually. since the #job is in memory would be good to add to the queue system.
Live life...