[Table and collection views] Consider content inset when calculating (default) element size range (#525)

* Table and collection views to consider their content inset when calculating element size range

* Update CHANGELOG

* Address comments

* -[ASPagerNode currentPageIndex] to use pageSize instead of bounds

* Update documentation in ASPagerNode

* Minor change
This commit is contained in:
Huy Nguyen
2017-08-22 22:14:01 +01:00
committed by Garrett Moon
parent 359b5f0b5b
commit 884a4f56f1
6 changed files with 23 additions and 8 deletions

View File

@@ -75,6 +75,9 @@ NS_ASSUME_NONNULL_BEGIN
@end
/**
* A horizontal, paging collection node.
*/
@interface ASPagerNode : ASCollectionNode
/**
@@ -84,6 +87,8 @@ NS_ASSUME_NONNULL_BEGIN
/**
* Initializer with custom-configured flow layout properties.
*
* NOTE: The flow layout must have a horizontal scroll direction.
*/
- (instancetype)initWithCollectionViewLayout:(ASPagerFlowLayout *)flowLayout;