Copying stops on questions instead of continuing with other files

[axeld]

When Tracker detects that a certain file already exists when copying, it should continue to copy the other files in the background, and silently collect other conflicting files.

Instead, it waits forever on user input.

Alternatively (though the file system may change at any point), it could also extent the preflight to the target, to check for those problematic files upfront (and still already start the rest of the copy in the background).

[andreasf]

You assume that is what the user wanted to do. But it could also be an indication she chose the wrong target folder, in which case a blocking question whether to cancel is good.

[axeld]

If I copy 30 items, and it asks this question after 20, I think it's pretty clear what should happen.

Also, if you actually put something in the wrong folder, you can always revert that. That is only problematic for the case of deletion where no conflicts can occur.

And yes, if the user does something, you can assume it's what the user wanted to do. For the cases where this might be fatal, you usually ask (like when you delete files).

Only a preflight check could alert you that something is wrong, and I think waiting at that point would be an acceptable compromise.

[waddlesplash]

Moving Tracker enhancement tickets out of R1 milestone -- Tracker's source code comes from BeOS R5, so it already has all the features it did on R5.