On Wed, Apr 7, 2010 at 11:25 PM, Jens Alfke <j...@mooseyard.com> wrote: > That may be true, but it's not directly related to the Finder graying out the > source file. As I said, it grays out the file when it itself starts copying > it. It has no way of telling when some other process is doing the copy.
Unfortunately my theory is not true. Part of the file is written while Finder is copying the file and there is no swap. Is there anyway for my app to see that the file is being written to? I was thinking of looking at 'fuser' or trying to open the file in write mode as a test. I haven't tried looking at kMagicBusyCreationDate, is that recommended? _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
