It’s details like the following that sometimes make me stop and realize how fined tuned a software Mac OS X really is.
Tonight, I did the following, sequentially:
- Moved a folder to the trash, not realizing that a subfolder contained a file being written to.
- Tried to empty the trash. The Finder told me those files were still in use.
- Took the directory out and dropped it on my Desktop (not the original location)
- Inspected the files and dropped them back into their original location
Where things get interesting is that the process which was writing to the said file never crashed or in any way gave an error. It happily followed the files as they moved around, keeping on keepin’ on. Everything was handled cleanly by the Finder and abstracted from the process. Classy.
It’s also worth noting that the said process was not an Apple app, so no unfair advantages.
tekArtist 
Hmm, I have to say I prefer how Windows does it. It would have deleted everything but the files that were in use and all parent folders of those files. It then would have popped up a dialog box saying unable to delete file XYZ because it is in use by ABC.
Why do you prefer being able to move files that are in use into the trash? That seems like it could very easily cause lots of problems, say if the program tried to open up files in a relative location to the file.
LikeLike
Same behavior on deleting all the files but the ones and parent folders. Didn’t tell me what was using the files though.
I wouldn’t say I prefer having it that way, I just find that it handled my doing it well. :)
LikeLike
s/delete/trashed
LikeLike