Feature Request: Pause file copies

[nandonakis]

I like the feature how you can kickoff various file operation jobs and it stacks them. However you can only stop them (which deletes them).

When you run multiple massive file operations at once, it's very inefficient and they all slow down.

It would be great if you could pause and resume the jobs.

Even better if you could queue them, so they automatically ran one after the other once completed.

[DorothyFan1]

I like the feature how you can kickoff various file operation jobs and it stacks them. However you can only stop them (which deletes them).

When you run multiple massive file operations at once, it's very inefficient and they all slow down.

It would be great if you could pause and resume the jobs.

Even better if you could queue them, so they automatically ran one after the other once completed.

I second this idea. I'm actually surprised nobody mentioned this yet.

[Chris]

Thanks for the suggestions. Pausing and queuing multiple file operations (rather than running them all at once) are both on our wish list for a future release.

[nandonakis]

Has this happened yet?
If not, can you advise on its status?

[Aaron]

This is still on our wishlist, but is not available at this time.

[myarmor]

Reevaluate current selection

I was just about to suggest this..

It would be nice to be able to pause a script (i.e finishing the current file then
halt until resume), but on resume I would want it to (optionally) reevaluate
the current command/selection if it was executing a SYNC or similar command when it was paused.

[Aaron]

Hello,

Are you looking to pause BC3 while it is running in a graphical scripting mode, executing a @bcscript.txt file, or from the graphical interface?

[myarmor]

@Aaron, while it is running a script.. Thats where a pause button would be the most significant
improvement (as cancel is the only option at the moment).
Especially while running some task that takes a while (such as syncing backups or some
other operation which isn't done in a flash).

If you then have to do some minor diskintensive task (or similar) which can't wait and
that has to be done on the same drive BC uses then pausing the sync would be ideal.
2 diskintensive tasks at the same time on the same drive is a bad idea as most probably know
(just starting a larger application from the same drive might take minutes rather than the
few seconds it normally does).

The reason for the reevaluate addition is that the files in the current operation could
have been changed/added/removed while it was paused.

As I see it, the pause should at least finish (and close) the file it currently is working
on before pausing.
Alternatively it could pause at the current position, close the file (so it isn't locked), then if
that file hasn't changed when you resume it should continue from where it left off, otherwise
reevaulate including that file. I would guess the latter would be too timeconsuming though (at least for bigger files).

[Aaron]

Thanks for the details. I'll add these notes.

[Crack]

Any update on queuing file transfers? It would be really useful to have it.

[Chris]

Pausing and queuing file transfers to run serially instead of in parallel are still on our wish list for a future version, but not supported in the current BC 3.3.4.

[DarrenD]

And another 6 months on...

I notice a lot of the user requests end up with "it is on our wish list". Are you able to publish this wish list with expected dates for completion? This pause feature has been asked for since 2009. I don't want to sound too critical but sometimes things do seem simple to implement yet take so long to come to fruition. I would dearly love this pause feature.

While I am on a roll with the move/copy lists (which are brilliant compared to BC2) an even more complicated but flexible thing would be to select multiple lists (will be the children) and drag and drop them on another one (will be the parent) to make them move/copy once the parent has finished its move/copy.

Another one would be a question mark icon (possibly) that when clicked would popup a window showing a list of the files/folders left to move/copy.

Darren .)

[Aaron]

Hello,

Our wishlist is where we collect ideas for future features and enhancements. They are not currently scheduled projects, so we do not have an estimated time to completion. Our internal lists are private; we do not want to show things until they have a sufficient level of polish. When needed, we'll launch a beta to help test larger features and get feedback.

Our current transfer algorithm uses the same basic copy method as Windows Explorer in the Windows version, so any modification here would not be a simple change. Adding the ability to pause/resume transfers is non-trivial, but adding this and other features such as better background task reporting are definitely on our radar.