Re: Bindings: is there a better way to observe when an object changes?
Re: Bindings: is there a better way to observe when an object changes?
- Subject: Re: Bindings: is there a better way to observe when an object changes?
- From: mmalc crawford <email@hidden>
- Date: Mon, 10 Sep 2007 12:54:59 -0700
On Sep 10, 2007, at 12:02 PM, Simone Tellini wrote:
I wouldn't say you're "doing the *only* possible thing at the
moment" -- per Shawn's and my earlier replies, it may be that you
can "future-proof" your implementation by defining dependent
properties for attributes affecting drawing.
err... unless I've misunderstood you, what you were suggesting is
exactly what I'm doing.
As I said, all of the attributes of the entity affect drawing
(everyone of them flags a bit of graphic content that needs to be
rendered) and my "hasChanged" property encapsulates them. The
dependancies are set in +initialize in the entity object, so the
view doesn't need to know much about it, except how to render it.
Oh, understood. I was trying to emphasise "defining dependent
properties for attributes *affecting drawing*" -- 'hasChanged' is
generic, and although at the moment all your attributes affect drawing
there's a chance that in the future this may not be the case.
Disambiguating from the outset may therefore be beneficial...
mmalc
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden