3 ms·

Would it tell me beforehand that not enough space is available instead of failing midway? Also, I can see a use case for this pause item here: not enough space?

by lloeki 15y ago

Would it tell me beforehand that not enough space is available instead of failing midway? Also, I can see a use case for this pause item here: not enough space? we paused the transfer so that you can free up space and resume, or cancel at will. The "use pause to prioritise the thing I'm not interacting with" part is egregious at best. Let me drag/drop the activities to prioritise them: "I want THAT one to complete faster, so I move it to the top" seems much more pertinent UX. Besides, having ten parallel copies is a sure performance killer on a single disk. Certainly having a queue with a bunch of worker slots per (read+write) device could be a nice design. A new copy task from disk A to disk B could thus be delayed because there are already a network transfer to disk A and a copy from USB key to disk A in progress. Number of per disk workers could be dynamically adjusted according to IO wait times on a given disk, so that a non-copy task (like starting an application or opening a file) would get priority. Raising/lowering priorities would automatically start/pause transfers according to available workers.