nsnotifications

I found that as predicted when I was writing an image to file that my UI was blocked for the duration, which was not acceptable. When I write the image to file I then post an NS Notification so that I can do some other specific jobs related to that completion. Original working but UI blocking code: -(void)saveImageToFile { NSString *imagePath = [self photoFilePath]; BOOL jpgData = [UIImageJPEGRepresentation([[self captureManager] stillImage], 0.5) writeToFile:imagePath atomically:YES]; if (jpgData) { [[NSNotificationCenter defaultCenter] postNotificationName:kImageSavedSuccessfully object:self

Is there an NSNotification we can observe for when the device is on/off the phone? The NotificationCenter doesn't send out any notifications abou this, but take a look at the CTCallCenter class introduced in iOS 4. It has a callEventHandler property that you can assign a block of code to, and gets called with call state info. There is a limitation in that the handler only gets called when your app is in the foreground (or being taken out of the foreground when a call comes in), but it tells you if the user is dialing ( CTCallStateDialing ), receiving a call ( CTCallStateIncoming ), answering

I have a view with keyboard notifications such as keyboardWillShow and keyboardWillHide All the codes handles with the notification I use is taken from Apple's sample code "KeyboardAccessory" When I first enter this view, everything works fine. But when I return to this view from its subviews, every time I tap a button that says: [myTextField becomeFirstResponder]; the keyboardWillShow and keyboardWillHide methods will be called twice every time. It's really confusing, Could anyone helps me with this? really appreciate! You might want to post your code. If your methods are being called twice,

I am trying to pass an object from my main view class to other notification receiver in another class. I want to pass an object named country, that loads all the cities from an SOAP Request in the Main Controller and i want to send it to my next view. country = [[Country alloc] init]; Country header: @interface Country : NSObject { NSString *name; NSMutableArray *cities; } @property (nonatomic,retain) NSString *name; - (void)addCity:(Cities *)city; - (NSArray *)getCities; - (int)citiesCount; @end I found a way to pass data with NSNotificatios is using a NSDictionary in UserInfo. But its not

Are the new notifications not currently working in Swift 3? I am doing: NotificationCenter.default().post(name: DidTouchParticleView, object: self.particle as? AnyObject) In a custom view's touchesBegan() and I need to send the particle object to the view controller if there is one. So I do this: NotificationCenter.default().addObserver(forName: DidTouchParticleView, object: self, queue: OperationQueue.main(), using: presentParticleDisplayView(notification:)) In a view controller's viewDidLoad() . I am certain that that particular view controller is the one presented when I tap my custom view,

I am interested in knowing whether I can expect the observing object's method to be pushed onto the stack before the posting object's method has been completed and removed. Jarret Hardie The short answer is yes... "Regular notification centers deliver notifications on the thread in which the notification was posted. Distributed notification centers deliver notifications on the main thread". However, Apple has docs on this very subject that you may find helpful, and from which the above quote was pulled: Notification Programming Topics: Delivering Notifications to Particular Threads Just