Re: NSTimer with userInfo
Re: NSTimer with userInfo
- Subject: Re: NSTimer with userInfo
- From: "Eric E. Dolecki" <email@hidden>
- Date: Tue, 12 May 2009 11:06:15 -0400
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 <email@hidden>wrote:
> On Tue, May 12, 2009 at 10:49 AM, Graham Cox <email@hidden>
> 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 (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