I just finished watching Marcus Zarra's NSFetchedResultsController presentation from iDeveloper.tv . At about 25 minutes into the presentation, Marcus says the NSFetchedResultsController only works well with table-view controllers. I had planned to use it with a collection-view, which is why I reviewed the presentation in the first place.
What I'm looking for is more information on why it is not a good idea to mix these two classes. What are the issues or pitfalls, in combining the two? I did find think link to a project on GitHub where the author points out that: > The trick is to queue the updates made through the > NSFetchedResultsControllerDelegate until the controller finishes its updates. > UICollectionView doesn't have the same beginUpdates and endUpdates that > UITableView has to let it work easily with NSFetchedResultsController, so you > have to queue them or you get internal consistency runtime exceptions. Is this the only issue or are there other reasons to avoid combining these two types of controllers? -Michael _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
