Re: Accessing NSTimer object added to NSRunLoop object
Re: Accessing NSTimer object added to NSRunLoop object
- Subject: Re: Accessing NSTimer object added to NSRunLoop object
- From: Dragan MiliÄ <email@hidden>
- Date: Mon, 15 Mar 2004 13:48:00 +0100
Hi,
Louis, you're right. How stupid of me! I actually made comparisons when
using NSTimer approach, before I realized that I need some way to
cancel them (before I saw how the app behaves). Since there wasn't any
cancelation at that time of my writing, I needed to make comparisons.
That need disappeared when cancelation entered the game, but I didn't
switched my mindset as fast as I should have. THANKS.
Milke.
Hello...
As long as your window controller only controls one of these
tableViews, you shouldn't need to store the selected row in an
instance variable, since you probably don't need to make that
comparison.
Anytime the user clicks on a different row, any previous rows that had
been selected do not matter since you cancel the previous perform
request. The delayed selector will only be called after the currently
selected row has been selected for 1.5 seconds.
For example:
Time 0.00 -- user clicks on row 5. Your controller recieves the
tableViewSelectionDidChange: notification. You call
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.