GNOME Bugzilla – Bug 695721
Confirming a move/copy should not block the transfer queue
Last modified: 2018-06-07 23:56:12 UTC
Hi, Here is an example of the behavior I am talking about in a trivial case. I move two files A and B at once to another location where a file named A already exists. The transfer of B is queued and waits until the transfer of A is done. In this case, A is a conflict which has to be resolved by the user via a dialog. B is therefore unnecessarily blocked. The desired behavior IMHO would be: 1. trigger the dialog for A 2. in parallel look through the queue for the next file not in conflict: B and process it (putting it at the front of the queue) 3. once B is done, check on the status of the next file in the queue: A. If the conflict is resolved proceed normally, otherwise, go back to 2. I can't really think of a case where changing the ordering of the queue would be bad. No time would be wasted waiting for the user's response. Especially for long transfers where the user is AFK.
*** Bug 752896 has been marked as a duplicate of this bug. ***
*** Bug 779578 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 339420 ***