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
This is because the method -collectionView:viewControllerForCell:
and therefore [self.collectionView indexPathForCell:cell]
gets called inside of -collectionView:cellForItemAtIndexPath:
before the collectionView knows about the cell.
One solution would be to add a third parameter indexPath to collectionView:viewControllerForCell:
Someone has a better idea? Pull request will follow
The text was updated successfully, but these errors were encountered:
stefreak
pushed a commit
to stefreak/TLIndexPathTools
that referenced
this issue
Jun 4, 2014
This makes multiple viewcontroller classes possible in
TLCollectionViewController.
Changes:
- change signature of collectionView:viewControllerForCell: to
collectionView:viewControllerForCell:atIndexPath:
- update View Controller Backed example
This makes multiple viewcontroller classes possible in
TLCollectionViewController.
Changes:
- Fix implementation of viewControllerForCell to get correct indexPath during cellFor*AtIndexPath
- update View Controller Backed example
This is because the method
-collectionView:viewControllerForCell:
and therefore
[self.collectionView indexPathForCell:cell]
gets called inside of
-collectionView:cellForItemAtIndexPath:
before the collectionView knows about the cell.
One solution would be to add a third parameter
indexPath
tocollectionView:viewControllerForCell:
Someone has a better idea? Pull request will follow
The text was updated successfully, but these errors were encountered: