Re: FSCopyObjectAsync: useless and crippled
Re: FSCopyObjectAsync: useless and crippled
- Subject: Re: FSCopyObjectAsync: useless and crippled
- From: Kevin Callahan <email@hidden>
- Date: Sun, 15 May 2005 20:48:28 -0700
On May 15, 2005, at 8:12 PM, Steve Gehrman wrote:
On May 14, 2005, at 6:47 PM, Creed Erickson wrote:
I would rather the app fail with reasonable and responsible error
reporting. Whatever happened to "pre-flighting" an operation to
see if you can do it successfully?
That's the core of my complaint. The API has a built in preflight,
which is cool, but, but the operation can only be set to fail, or
skip files. There's no way to ask or warn the user that the
operation will skip files. All it needs is a simple call back, 10
lines of code added to this API and it would be acceptable.
-steve
When I did a clean install of Tiger (release) on my PB, I grew very
disconcerted while using Finder to copy my data from an external FW
drive to restore my system. The numerous -36 errors part way through
the copy were new to me with this drive. No information relating to
the file(s) that failed was given. I spent an inordinate amount of
time figuring out which files were causing the copy failure. In my
case, the bad files weren't skipped. The copy operation simply
failed. I can imagine the average user would have been left in a
sorry state.
I wouldn't mind a copy feature where the copy continues, based on my
response, and then I'm given a report as to which files failed, and
why they failed (beyond -36 ).
Should I file a request to Radar?
Kevin
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden