Re: CoreData, Object/Array Controllers and KVO

2008-08-15 Thread Negm-Awad Amin
Am Do,14.08.2008 um 07:46 schrieb Jeff Hellman: Hi Folks- Hi as already said, KVO is not the right place to do that. If this is a real important property, you should think about a model user interface (update button, sheet) to handle it. You can use notifications or maybe "bindings throu

Re: CoreData, Object/Array Controllers and KVO

2008-08-14 Thread Quincey Morris
On Aug 14, 2008, at 13:49, Jeff Hellman wrote: As soon as I bind the text field value to a key path (self.title or just title) in the ObjectController, then the below methods are called for each and every key in my ManagedObject. It sounds like your object is being fetched with its properties

Re: CoreData, Object/Array Controllers and KVO

2008-08-14 Thread Jeff Hellman
Ok...So a bit more detail: I am setting the content of the NSObjectController (which is an IBOutlet) to a managed object that I've fetched in the WindowControllerDidLoadNib method of my application. I have one NSTextField in my NIB. If I don't bind a value from the ObjectController to the TextFi

Re: CoreData, Object/Array Controllers and KVO

2008-08-14 Thread I. Savant
On Aug 14, 2008, at 1:46 AM, Jeff Hellman wrote: - (void)willChangeValueForKey:(NSString *)key is called. So is - (void)didChangeValueForKey:(NSString *)key Why is this? I'm not actually changing the object values, am I? If you know that, you should be able to see what key changed. From

CoreData, Object/Array Controllers and KVO

2008-08-13 Thread Jeff Hellman
Hi Folks- I've got a document based CoreData application. When I open a file and add some of my NSManagedObject subclass objects to either an NSArrayController (bound to an entity in my NIB) or NSObjectController (-setContent) the - (void)willChangeValueForKey:(NSString *)key is called. So is