Re: Bindings + Trapping Changes
Re: Bindings + Trapping Changes
- Subject: Re: Bindings + Trapping Changes
- From: Keary Suska <email@hidden>
- Date: Sun, 18 Jun 2006 10:23:13 -0600
on 6/17/06 10:04 PM, email@hidden purportedly said:
>> I thought perhaps I could just observe the dict, but I don't recall
>> whether
>> NSDictionary triggers notifications on element changes (or I am
>> just brain
>> farting here).
>>
> Given that bindings work with dictionaries, it's not clear why you
> would think that they wouldn't?
> You simply observe the relevant key.
Sorry, I wasn't explaining myself well. I meant observing changes *without*
having to observe every possible editable key, since there may be many. As
long as the suggestion of overriding setValue:forKey: (of non-managed
objects ;-) works and doesn't break KVO, that seems like a good solution.
Your suggestion of registering a dependent key sounds like another option,
as long as I register to observe the dependent key. This would certainly be
more succinct, but I think I prefer the transparency of setValue:forKey: as
that also allows me to use different data representations in the model and
not have to make accessors for every key--also allowing me to use the model
object for a number of various data collections.
>> No core data-based suggestions, please. It is not an option.
>>
> It's not clear why Core Data would be relevant here?
Because I have to target 10.3. I suppose I could have made that explicit...
Thanks,
Keary Suska
Esoteritech, Inc.
"Demystifying technology for your home or business"
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden