On 6 Oct 2010, at 11:29, Quincey Morris wrote: > > This all means that anything you choose to configure in #1 may or may not > still be in effect by the time you get to #2, but that's an implementation > detail on which you cannot rely, because there's no API contract that > anything is kept. > This seems to be an inescapable conclusion. I can configure certain aspects of the cell in #1 but seemingly not others. Perhaps the cell copying on edit/tracking that Corbin referred to has an influence here. But as you say, it's all dependent on the opaque detail of the implementation.
> > In many cases, #1 and #2 will be called in lockstep pairs, so it might seem > that you could configure your cell in either place. However, because the > delegates have separate purposes, configuration should be reserved for #2 > only. > I agree. Identify the cell type in #1. Configure it in #2. Thanks for taking the time to help clarify my murky thoughts on this. Regards Jonathan Mitchell Developer Mugginsoft LLP http://www.mugginsoft.com_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
