Re: Is KVO really as complicated as I think?
Re: Is KVO really as complicated as I think?
- Subject: Re: Is KVO really as complicated as I think?
- From: mmalcolm crawford <email@hidden>
- Date: Tue, 27 Apr 2004 15:09:18 -0700
On Apr 27, 2004, at 2:24 PM, Steve Sims wrote:
mmalc, your idea seems fairly sound and should work, so thanks for the
suggestion. However I have a lot of UI elements that affect the
derived parts of my data model, so this idea would seem to mean that
I'd need to write a whole load of setters to do the nulling thing. In
fact I may as well not bother with nulling but just do the
recalculation. I'd hoped to be able to do without a big mess of
setters and accessors by using bindings and KVO.
I'm not sure again how this will be more complicated than the problem
seems to inherently demand? If there are interdependencies between
values, then you have to track those. You should probably be writing
getters and setters anyway. You may need to add a little logic to
those, and perhaps an initialize method to tell KVO about the
dependencies, but I don't think this should constitute a "big mess"?
Is there something I'm missing?
mmalc
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.