Actually, I just made a reference to the table here because that seems a lot cleaner and I'm not currently managing multiple tables. So I'll simply use that reference for now, however I am still including it with the indexPath in that dictionary I am sending just in case I want to change that in the future. Eric
On Tue, May 12, 2009 at 10:54 AM, I. Savant <idiotsavant2...@gmail.com>wrote: > On Tue, May 12, 2009 at 10:49 AM, Graham Cox <graham....@bigpond.com> > wrote: > > > Normally the object receiving the timer callbacks is a controller that > > already knows about those objects, or has direct ways to get them. If > not, > > you may have a design problem... > > I'd considered that in my response, but considered also that he > might be managing multiple tables and needs the timer code to be more > dynamic. If not, you're right that he could just send the index path > itself since he probably already has a reference to the table handy. > > NSIndexPath is already an object, so that's the prime candidate if > you already have a reference to the table. > > -- > I.S. > -- http://ericd.net Interactive design and development _______________________________________________ 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
