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
Some places of the sample app have been broken by the swift 3 conversion. Typical issues are dataSource methods that have changed signature, but had a default implementation
There is also a bug that occurs when specifying a large estimated height, but the actual height is much smaller. This causes some bricks to disappear when scrolling
The text was updated successfully, but these errors were encountered:
- Cleanup the sample app. Mainly update protocols that changed function signatures, but had a default implementation, so the compiler didn’t complain
- Fixed a weird behavior when bricks would disappear when the estimated height of a brick was much bigger than the actual brick. This is solved by setting the `invalidateItems` to nil, so the collectionView will fetch the layoutAttributes again
Fixes#142
- Cleanup the sample app. Mainly update protocols that changed function signatures, but had a default implementation, so the compiler didn’t complain
- Fixed a weird behavior when bricks would disappear when the estimated height of a brick was much bigger than the actual brick. This is solved by setting the `invalidateItems` to nil, so the collectionView will fetch the layoutAttributes again
Fixes#142
Some places of the sample app have been broken by the swift 3 conversion. Typical issues are dataSource methods that have changed signature, but had a default implementation
There is also a bug that occurs when specifying a large estimated height, but the actual height is much smaller. This causes some bricks to disappear when scrolling
The text was updated successfully, but these errors were encountered: