Now this may sound like my earlier problem/question but I\'ve changed and tried a few things that were answered in my other questions to try to make it work, but I\'ve still got the same problem.
I have loaded item from core data in an NSMutableArray. Each item, when created, is given a due date, that the user choices.
So I\'m working on a clone of CoreDataBooks. It\'s a little different. When the \'+\' button is pushed, it launches a navController, containing 2 views. The first (AddPatientVC) asks for name of the P
I\'m newbie in coredata and still learning. I have an application which need to fetch number of records which fulfill given criteria.
I am trying to implement a Core Data backed UITableView that supports indexing (eg: the characters that appear down the side, and the section headers that go with them). I have no problems at all impl
I have an app, using Core Data with a SQLite store. At some point I\'d like to remove all objects for a few entities. There may be close to a thousand objects.
I have an application that will use Core Data. I\'ve added the Core Data framework to the linked library list in XCode.
I\'ve got an NSFetchedResultsController as my data source and and I implement NSFetchedResultsControllerDelegate in my custom UITableViewController.I\'m using sectionNameKeyPath to break my result set
I\'ve built a simple iPhone app that parses data from a remote XML feed, converts the information into objects (they\'re videos), and displays the videos in a standard table view->detail view->\"Play
Should I make a single NSLock instance in the application deleg开发者_开发知识库ate, to be used by all classes? Or is it advisable to have each class instantiate its own NSLock instance as needed?
加载中,请稍侯......