Featured iPhone Development Resources,iOS Development Libraries,Objective-C,Open Source iOS Libraries And ToolsBlocks have been a nice addition to iOS Objective-C programming, but unfortunately the blocks-based API added to NSNotificationCenter brings about a number of potential issues.
Here’s a library from Nick Lockwood called FXNotifications that provides an NSNotificationCenter category that provides an easier to use blocks based API but allows you to avoid memory leak and retain cycle bugs that can occur when simply using the official API.
Here’s an example from the readme showing the method added with FXnotifications in action:
forName:NSSomeNotificationName
object:nil
queue:[NSOperationQueue mainQueue]
usingBlock:^(NSNotification *note, __weak id observer) {
NSLog(@"self: %@", observer); // look, no leaks!
}];
Notice that you must specify an observer for the method to work.
You can find FXNotifications on Github here.
You can read more about the issues when using blocks and NSNotificationCenter without FXNotifications on the Sealed Abstract blog.
A handy category making NSNotificationCenter easier to use while avoiding some major issues.
- Library Providing An NSNotificationCenter Alternative For Handling Multiple Delegates
- Objective-C UIControl Category Inspired By JQuery Adding Many Blocks-Based Events
- Libraries For Easier Drawing Of Custom UI Elements, CoreImage Filter Enhancements And More
- Open Source Library That Makes Working With Store Kit Easier
- Tutorial: Debugging Objective-C Memory Leaks For Beginners
Original article: NSNotificationCenter Category Providing An Easier Blocks Based API Without The Memory Issues
©2013 iOS App Dev Libraries, Controls, Tutorials, Examples and Tools. All Rights Reserved.