To begin with I built a test core data project utilising an
NSArrayController bound to an NSTableView.
This showed no performance issues at all so, surprise surprise, the
problem was of my own creation.
Looking at the Shark traces reveals an implementation change in the
way that model
On Fri, Oct 16, 2009 at 2:49 PM, jonat...@mugginsoft.com
jonat...@mugginsoft.com wrote:
[self addObserver:self forKeyPath:@message options:0 context:(void
*)MGSContextMessage];
[self addObserver:self forKeyPath:@date options:0 context:(void
*)MGSContextDate];
[self addObserver:self
I am using an array of simple NSManagedObject subclasses bound to an
NSArrayController.
The object graph is shallow with a tiny number of objects (500).
All objects are loaded into the NSArrayController MOC using an
NSFetchRequest with setReturnsObjectsAsFaults:YES.
Therefore no faulting
The following is correct:
All objects are loaded into the NSArrayController MOC using an
NSFetchRequest with setReturnsObjectsAsFaults:NO.
Jonathan Mitchell
Developer
http://www.mugginsoft.com
___
Cocoa-dev mailing list
