nsobject

What is the significance of WaitUntilDOne in performSelectorOnMainThread ? IN what way the YES or NO set to WaitUntilDone can have on the App? UPDATE: My Question should have been: In what scenarios do they make difference? Sergio's answer was the one I was expecting. From Apple docs about waitUntilDone : A Boolean that specifies whether the current thread blocks until after the specified selector is performed on the receiver on the main thread. Specify YES to block this thread; otherwise, specify NO to have this method return immediately. If the current thread is also the main thread, and you

i'm working on a iOS5+ project (xcode 4.4.1 SDK 5.1) i have this code inside a unit test: [_appDelegate application:nil didFinishLaunchingWithOptions:nil]; UITabBarController *tabBarController = (UITabBarController*)_appDelegate.window.rootViewController; NSArray *viewControllers = [tabBarController viewControllers]; UINavigationController *nc_1 = [viewControllers objectAtIndex:0]; UIViewController *vc_1 = nc_1.topViewController; STAssertTrue([vc_1 isKindOfClass:[ScheduleViewController class]]==YES, @"UITabBarController first tab should be a ScheduleViewController class"); If i run the test,

I need a save way to say: "iOS, I want this method to be executed a.s.a.p., but NOT in THIS run loop iteration. At the earliest in the next, but please not in this one. Thank you." Right now I am always doing it like this: [self performSelector:@selector(doSomethingInNextRunLoop) withObject:nil afterDelay:0]; [self doSomeOtherThings]; With the assumption that -doSomeOtherThings will always be performed BEFORE -doSomethingInNextRunLoop . The documentation says: Specifying a delay of 0 does not necessarily cause the selector to be performed immediately. The selector is still queued on the thread

Property 'Latitude' is a scalar type on class 'LatitudeLongitude'. Cannot generate a setter method for it. When I generated codes for my managed object, I got a message whether I want scalar properties for primitive data type. should I use it? I want to make this application compatible with iPhone 3 - 5 is there any issues with this problem? When you use scalar properties you have to provide implementations of getters and setters for those properties by yourself, as described in documentation: "You can declare properties as scalar values, but for scalar values Core Data cannot dynamically

I am writing a framework and I have an object with a custom init method: @implementation OSDatabase @synthesize database; // MEM - (void)dealloc { sqlite3_close(database); [super dealloc]; } // INIT - (id)initWithDatabasePath:(NSString *)path error:(NSError **)error { if (self = [super init]) { if (!sqlite3_open_v2([path UTF8String], &database, SQLITE_OPEN_READWRITE | SQLITE_OPEN_CREATE, NULL)) { error = [NSError errorWithDomain:@"OSDatabaseErrorDomain" code:1 userInfo:nil]; [self dealloc]; return nil; } } return self; } @end Is it safe to call dealloc inside of an init method if an error