You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 2, 2023. It is now read-only.
We can't prevent UIKit from calling these methods on self but users should virtually never call methods like these on ASTableView/ASCollectionView, and we shouldn't override them.
-selectRowAtIndexPath:animated:
-scrollToRowAtIndexPath:animated:
-rectForRowAtIndexPath: // !! Needs to be added to ASTableNode
-cellForRowAtIndexPath: // !! Needs to be added to ASTableNode
-indexPathForSelectedRow // !! Needs to be added to ASTableNode
-indexPathForRowAtPoint: // !! Needs to be added to ASTableNode
-indexPathsForRowsInRect: // !! Needs to be added to ASTableNode
-indexPathsForVisibleRows: // !! Needs to be added to ASTableNode
It will be a bummer for developers, but the index paths just won't line up – it's part of the asynchronous nature of table node and collection node. @george-gw Would you be willing to implement the methods above, using convertIndexPathFromTableNode:?
We can't prevent UIKit from calling these methods on self but users should virtually never call methods like these on ASTableView/ASCollectionView, and we shouldn't override them.
It will be a bummer for developers, but the index paths just won't line up – it's part of the asynchronous nature of table node and collection node. @george-gw Would you be willing to implement the methods above, using
convertIndexPathFromTableNode:
?Thoughts @appleguy @maicki @garrettmoon ?
The text was updated successfully, but these errors were encountered: