Aqua Taskforce

ion wrote on August 10, 2008, 8:19pm

Added new image attachment.

ion wrote on August 10, 2008, 8:20pm

Added new image attachment.

ion wrote on August 10, 2008, 8:23pm

Changed problem description.

bailey_ca wrote on August 12, 2008, 6:02am

Hmmm. Interesting, I never noticed that! Okay, this one is pretty much a gimme: This should be fixed.

abitgone wrote on August 21, 2008, 1:30am

Technically speaking, a move operation is a copy followed by a delete.

Just playing Devil's Advocate.

divinenephron wrote on August 30, 2008, 12:55pm

I didn't even know that there was a move dialogue, surely moving an infinitely large file from one location to another on the same disk just involves telling the filesystem to pretend it is in a different place.
But apparently there is a dialogue and it should be fixed....

vbtwo wrote on September 1, 2008, 3:19pm

Yes, moving files on the same disk just tells the filesystem to pretend it's in a different place, so it's almost instantaneous, but this dialog is for when moving files to a different disk.

This bug is probably because all copy/move operations get grouped into the same one dialog on the Mac instead of opening up a new dialog for each copy/move operation as is done on Windows and they didn't want to bother changing the title (what happens when you move and copy something at the same time?).

polycat33 wrote on September 11, 2008, 4:47am

There's no "moving" something to another drive, it's a copy operation if you drag a file to another drive. If you want to "move" it then you have to delete the original once you've copied it over. So it makes perfect sense to me that it says copy. And when you're really just moving something on the same disk I've never seen a dialog talking about how long it's going to take... since it doesn't have to write anything to a disk.

ion wrote on September 12, 2008, 3:40pm

oh, polycat33... such a patriot. Then please tell me why does it say
"Moving filename.ext" to destination"
in the dialog however the title shows "Copy".

kiodane wrote on May 20, 2009, 11:54pm

"Move" means to "copy" then "delete". If the move failed midway and the progress bar said "Moving" then you'd have a load of users who would be paranoid that their data was broken in half on both sides. "Copying" speaks more to what is actually happening, except that "Deleting" takes so little time because all it has to do is remove the file's hierarchy data from the file system tables.

linuxforever wrote on May 25, 2009, 7:42pm

I conclude that we all agree: The title does not tell the average consumer the whole truth. Therefore, I do not understand why there is no help button/icon of any sort explaining what is actually going on and what would happen to the original files and the "new" ones on a user initiated abort of the running procedure. For this reason, I recommend a short explanation pressing an info-button and additionally showing a table listing of the paths of the "original" and the "new" files also indicating the progress by color encoding the data already processed.
I definitely disagree with polycat33 tending to generalize that such action is short enough to neglect the presentation of extensive information because I consider it mandatory, especially to debug operations involving network connections or two different storage devices. For example pulling out a flash drive while moving files onto it should make the OS show up a notification suggesting to re-plug the drive to continue and informing the user that the flash drive currently contains a corrupted/incomplete copy of the original files which are still untouched and not even partly (re)moved.