The foolproof way to do it is to have the transient attributes recalculated each time they are accessed. In other words, they are simply getter methods. But if they are expensive to compute, this might not work well. If you are using bindings or KVO, you then have a class method + (NSSet*)keyPathsForValuesAffecting<AttributeName> that ensures observers of the transient attribute are notified when underlying non-transient attributes change.
On 2013-06-18, at 10:08 PM, Rick Mann <[email protected]> wrote: > > On Jun 18, 2013, at 19:07 , Laurent Daudelin <[email protected]> wrote: > >> Just a wild guess but what about awakeFromInsert? > > Well, I think that only gets called when you first create the object. In my > case, objects already exist. > > -- > Rick > > > > > _______________________________________________ > > Cocoa-dev mailing list ([email protected]) > > 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: > https://lists.apple.com/mailman/options/cocoa-dev/dave.fernandes%40utoronto.ca > > This email sent to [email protected] _______________________________________________ Cocoa-dev mailing list ([email protected]) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
