Re: Triggering UITableView's -didSelectRowAtIndexPath: delegate callback
Re: Triggering UITableView's -didSelectRowAtIndexPath: delegate callback
- Subject: Re: Triggering UITableView's -didSelectRowAtIndexPath: delegate callback
- From: Jens Alfke <email@hidden>
- Date: Sun, 28 Feb 2016 22:05:36 -0800
>> On Feb 27, 2016, at 4:27 PM, Keary Suska <email@hidden <mailto:email@hidden><mailto:email@hidden <mailto:email@hidden>>> wrote:
>>
>> This results in a much more reliable and extensible decoupling since no other object should know those internal signaling mechanics and should have confidence that any other object interested in the selection will be dutifully notified. In fact, this is how NSTableView works. Why UITableView doesn’t, seems worthy of a radar.
NSTableView doesn’t work that way. Changing the selection programmatically does not trigger a selection-changed notification / delegate callback.
—Jens
_______________________________________________
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