Hi
This is a inconsistent behaviour I have noticed. Maybe others have already noticed this.
Assume you have a file on your iMac and a file with the same name on a server. And decide to replace the file on the server with the file on your iMac.
So you press [cmd] and drag the file to the server to "move" the file to the server.
OSX will then ask if you want to "replace", "keep both" or "stop".
Assume you select "replace", the file on the server will be overwritten by the file from your iMac desktop.
Now for the interesting part, on your iMac select "Finder/Edit/Undo of ..."
Here you find yourself with a different final situation than the initial setup because the file on the server that was replaced by the move will not be re-instated, but the file moved to the server will return to the iMac desktop.
Basically, the "undo" actually results in a file remaining deleted.
(for information; I am using MAV iMac and SL server).
I found this out the hard way and went to the TC to recover the file, but it does leave the feeling that the "undo" is not a full "undo".
Hope this helps others avoid problems...
This is a inconsistent behaviour I have noticed. Maybe others have already noticed this.
Assume you have a file on your iMac and a file with the same name on a server. And decide to replace the file on the server with the file on your iMac.
So you press [cmd] and drag the file to the server to "move" the file to the server.
OSX will then ask if you want to "replace", "keep both" or "stop".
Assume you select "replace", the file on the server will be overwritten by the file from your iMac desktop.
Now for the interesting part, on your iMac select "Finder/Edit/Undo of ..."
Here you find yourself with a different final situation than the initial setup because the file on the server that was replaced by the move will not be re-instated, but the file moved to the server will return to the iMac desktop.
Basically, the "undo" actually results in a file remaining deleted.
(for information; I am using MAV iMac and SL server).
I found this out the hard way and went to the TC to recover the file, but it does leave the feeling that the "undo" is not a full "undo".
Hope this helps others avoid problems...