When copying or moving files from on pane to another, sometimes the queue is very big. Stopping the transfer to resume later (not pausing) is not a very good idea because we don't know where it stopped last time. And we do have to restart Windows sometimes, maybe after an update. This is specially common after reinstalling our OS, replacing hard drives, when we have to move 300GB+ of files: it will also be the time when Windows nags us with updates.
Besides, there is the inconvenience of forced shutdown/restart that catches us with the low guard, which sometimes breaks the transfer in the middle. Other times we just have to stop and shut down, and the file being transfered is already allocated on the destination location, but not entirely transfered, so it will take the space like it was in it's whole, opening the door for confusion: the user will think the file is ok, but it's actually corrupted.
So, there could be the option inside the file transfer job window: "stop after current". When clicked, x2 would wait until the current file finishes transfering and possibly would remember where the user stopped. AND/OR, at the time we clicked that button, a sort of a log file would display with two lists: files transfered ok and pending files.
It would be nice to resume the transfer in the future!
