Re: Strange NSManagedObjectContextObjectsDidChangeNotification behavior
Re: Strange NSManagedObjectContextObjectsDidChangeNotification behavior
- Subject: Re: Strange NSManagedObjectContextObjectsDidChangeNotification behavior
- From: Karolis Ramanauskas <email@hidden>
- Date: Wed, 25 Feb 2009 11:42:31 -0600
> Is locationY the model attribute which you "have to" change? If so, I
> suggest that this is not rightfully a model or managed object attribute.
> Obviously, it's more of a 'view' thing than a 'model' thing. Remove it
> from your data model. Make it a regular instance variable instead or,
> better yet, remove it entirely from your model class and calculate it in
> your view class when you need to draw. Thousands of apps do it that way --
> it will work for your app too!
All this time thinking, concocting amazingly elaborate schemes how I
will make this work using several notifications, etc... This never
occurred to me! Thanks! It's true, I always dynamically calculate
this... Thanks again.
_______________________________________________
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