SelfMan wrote:(even if I remember right I already requested this feature)
True story,
http://forum.altap.cz/viewtopic.php?f=3&t=2952, sorry I didn't look it up first.
It is said there that:
Jan Rysavy wrote:We have two problems here:
1. The Delete operation doesn't need to have confirmation dialog box or this dialog box could come from Windows (Recycle Bin). So we have no place where place the queue option.
2. The proposal is potentially dangerous. Imagine situation when first Copy/Move operation will fail (out of space, overwrite confirmation, other error, or just cancel). The queued Delete operation will delete your only data
1) Oh. I don't know anything about this, but the Win dialog box could be replaced, could it not? Is it hard to detect Recycle Bin usage? Is there a hidden technical problem behind this making it a lot more complicated than it seems to be on the first glance?
2) Okaaay. Seriously, the action queue is already NOT being paused/canceled when one of the Move/Copy actions failed? Well it should be, it's a chain of actions (likely to be connected) and every single fail could be a problem... +1 for throwing an interruption in when there's a fail.
EDIT: And if somebody's going to point out that the Move/Copy/Delete actions might not be connected to each other and therefore the Cancel on the entire queue could be a problem, well, detect it then. It should not be a hard thing (nor a very easy one too) to detect whether a new Copy/Move action would affect one of already existing action chains (shares a destination or target path with some of the actions in there) multiple Copy/Move chains. Every new action in the queue would be assigned to some of the already existing chains (or to two or more of them - then they would have to be merged carefully). And if there's a fail somewhere, there still would be actions possible to perform, since it is certain that they can't be affected by the fail.
example:
Let's have drives C:, D:, E:, F: and G:.
Copy a file from C: to D: -> creates a queue with one request (1 chain)
Copy a file from F: to G: -> inserts a request into the queue and because the new action does not affect any directory from the first Copy action, it creates a different chain ... it would be NOT performed immediately but in the case of the first action failing, it could be safely done. And vice versa - if this actions fails, the following one could still be performed:
Copy a file from D: to E: -> request into a queue, connects to the first chain since the first action involves D: drive.
Um, did I say it understandably or should I make an example image?