iphone - Fetched Results Controller with NSPredicate vs. Core Data NSSet -
OK, so I have a UITableView hierarchy top level controller, for categories, that for category unit The results obtained with the specific definition are chosen by the controller.
When a user taps a cell, those items are advanced to the table view controller.
At this point, I was assuming that I should use a result controller with the prospectus so that the results are not found to filter the results.
However, I have many difficulties to explain what it does for all the examples search string for comparative properties are looking for. Corunda is not comparing the rationale.
So is it a better practice to use this method, or simply get the NSSet of items passed in the class managed object? Your second level view controller should be in the selected category through dependency injection as the asset.
To do this, when a category is selected in your top level controller, you get a pointer through the NSFetchedResultsController
, the new view controller Set up an immediate, category property, and then press the new view controller.
This will give you solid loopholes and separation between your view controllers.
Comments
Post a Comment