FROM : Scott Stevenson
DATE : Tue Nov 30 21:47:47 2004
On Nov 29, 2004, at 6:16 PM, Alex v.Below wrote:
> The question I am about to ask seems to have been asked in the past,
> but I can not find an answer. I am registering as an observer to my
> custom NSArrayController by:
>
> [_listController addObserver:self
> forKeyPath:@"arrangedObjects"
> options: (NSKeyValueObservingOptionNew |
> NSKeyValueObservingOptionOld)
> context:NULL];
>
> Now, observeValueForKeyPath is called, but the change dictionary
> contains nil for both old and new. Also, passing the change up to
> super crashes the app.
Can you give a broader description of what you're trying to do? In most
cases, it makes more sense to observe the source array for changes.
- Scott
--
http://treehouseideas.com/
http://theobroma.treehouseideas.com/ [blog]
DATE : Tue Nov 30 21:47:47 2004
On Nov 29, 2004, at 6:16 PM, Alex v.Below wrote:
> The question I am about to ask seems to have been asked in the past,
> but I can not find an answer. I am registering as an observer to my
> custom NSArrayController by:
>
> [_listController addObserver:self
> forKeyPath:@"arrangedObjects"
> options: (NSKeyValueObservingOptionNew |
> NSKeyValueObservingOptionOld)
> context:NULL];
>
> Now, observeValueForKeyPath is called, but the change dictionary
> contains nil for both old and new. Also, passing the change up to
> super crashes the app.
Can you give a broader description of what you're trying to do? In most
cases, it makes more sense to observe the source array for changes.
- Scott
--
http://treehouseideas.com/
http://theobroma.treehouseideas.com/ [blog]
| Related mails | Author | Date |
|---|---|---|
| Alex v.Below | Nov 30, 03:16 | |
| Scott Stevenson | Nov 30, 21:47 | |
| Alex v.Below | Dec 1, 01:12 | |
| Scott Stevenson | Dec 1, 01:21 | |
| Alex v.Below | Dec 1, 01:29 | |
| Scott Anguish | Dec 1, 07:09 |






Cocoa mail archive

