Comment 22 for bug 306630

my 2 cents, what about this?

Every copy operation initiated (after the first one) starts in a paused state (its queued), so you see the list of copying operations (or pending ones), but you put a play/pause button next to each operation, so in the standard case everything gets queued, but you press play in the file(s) that you want to want to do concurrently and its done.

Theres no checking for destination, size or any other "intelligent" feature, just autoqueue with the possibility to force parallel copying/moving at the users discretion.

i think we wont have neither of the 2 problems on this case, later it would be cool to arrange the order inside the queue but its out of this scope i guess.