Re: FSCopyObjectASync callback handler
Re: FSCopyObjectASync callback handler
- Subject: Re: FSCopyObjectASync callback handler
- From: Rosyna <email@hidden>
- Date: Sun, 6 Aug 2006 14:35:51 -0700
Aside from the issue Mike Ash pointed out, you haven't scheduled the operation.
FSFileOperationScheduleWithRunLoop(fileOp, [[NSRunLoop
currentRunLoop] getCFRunLoop], (CFStringRef)NSDefaultRunLoopMode);
Ack, at 8/6/06, Mike Abdullah said:
Well here's my test class:
#import "Controller.h"
@implementation Controller
static void statusCallback(FSFileOperationRef fileOp, const FSRef
*currentItem, FSFileOperationStage stage, OSStatus error,
CFDictionaryRef statusDictionary, void *info)
{
printf("statusCallback called");
}
- (IBAction)doCopy:(id)sender
{
OSStatus err;
FSRef sourceFileRef, destinationDirectoryRef;
// Build the parameters
FSFileOperationRef fileOp = FSFileOperationCreate(kCFAllocatorDefault);
FSPathMakeRef((UInt8 *)[@"/Users/dev/Desktop/"
fileSystemRepresentation], &sourceFileRef, NULL);
FSPathMakeRef((UInt8 *)[@"/Users/dev/"
fileSystemRepresentation], &destinationDirectoryRef, NULL);
OptionBits options = kFSFileOperationDefaultOptions;
// Do the copy
err = FSCopyObjectAsync(fileOp,
&sourceFileRef,
&destinationDirectoryRef,
(CFStringRef)@"Desktop 2",
options,
statusCallback,
1.0,
NULL);
}
@end
I click a button in my interface which calls the IBAction method.
Everything seems to work just fine, and the folder (about 2 gigs) is
copied. However, the callback is never actually called. Any ideas?
--
Sincerely,
Rosyna Keller
Technical Support/Holy Knight/Always needs a hug
Unsanity: Unsane Tools for Insanely Great People
It's either this, or imagining Phil Schiller in a thong.
_______________________________________________
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