Comments on: NSIndexPath and row method http://iPhoneDeveloperTips.com/objective-c/nsindexpath-and-row-method.html Tips and Tricks for iPhone developers Sun, 05 Sep 2010 15:32:31 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: julian skidmore http://iPhoneDeveloperTips.com/objective-c/nsindexpath-and-row-method.html/comment-page-1#comment-18570 julian skidmore Fri, 02 Jul 2010 15:01:05 +0000 http://iPhoneDeveloperTips.com/?p=66#comment-18570 Yep, I was confused as well! Very helpful information :-) -cheers from julz @p Yep, I was confused as well! Very helpful information :-)

-cheers from julz @p

]]> By: LostOne http://iPhoneDeveloperTips.com/objective-c/nsindexpath-and-row-method.html/comment-page-1#comment-47 LostOne Sat, 20 Sep 2008 18:45:49 +0000 http://iPhoneDeveloperTips.com/?p=66#comment-47 Thanks for helping me find the documentation for "row". This may be a great example of categories, but only if you know the secret. IMO, it demonstrates a real problem with the reference documentation. The UITableViewDataSource Protocol Reference (and others) lead me to the un-extended class and no idea why "row" is missing. It took a google search and this page for me to find out about UIKit Additions and "row". As an Objective-C newbie, I'll ask why this is so much better than subclassing. If every Table View related use of NSIndexPath is going to use "row" and depend on it, why not just subclass NSIndexPath? Should I write my DataSource to expect NSIndexPaths that may or may not support row? Thanks for helping me find the documentation for “row”.

This may be a great example of categories, but only if you know the secret. IMO, it demonstrates a real problem with the reference documentation. The UITableViewDataSource Protocol Reference (and others) lead me to the un-extended class and no idea why “row” is missing. It took a google search and this page for me to find out about UIKit Additions and “row”.

As an Objective-C newbie, I’ll ask why this is so much better than subclassing. If every Table View related use of NSIndexPath is going to use “row” and depend on it, why not just subclass NSIndexPath? Should I write my DataSource to expect NSIndexPaths that may or may not support row?

]]>