From 6db9a27ef4be220d03d7c9bf4848f788081aefd5 Mon Sep 17 00:00:00 2001 From: Luke Parham Date: Mon, 25 Apr 2016 12:42:25 -0500 Subject: [PATCH 1/2] fixed swift initializer --- _docs/containers-ascollectionnode.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_docs/containers-ascollectionnode.md b/_docs/containers-ascollectionnode.md index a08c5e71..0fd7923c 100755 --- a/_docs/containers-ascollectionnode.md +++ b/_docs/containers-ascollectionnode.md @@ -43,7 +43,7 @@ An `ASCollectionNode` is assigned to be managed by an `ASViewController` in its SwiftObjective-C
-- (instancetype)initWithCoordinates:(CLLocationCoordinate2D)coordinates
+- (instancetype)init
 {
   _flowLayout     = [[UICollectionViewFlowLayout alloc] init];
   _collectionNode = [[ASCollectionNode alloc] initWithCollectionViewLayout:_flowLayout];
@@ -59,7 +59,7 @@ An `ASCollectionNode` is assigned to be managed by an `ASViewController` in its
 
+This works just as well with any node such as an ASTableNode, ASPagerNode, etc. + ##Accessing the ASCollectionView## If you've used previous versions of ASDK, you'll notice that `ASCollectionView` has been removed in favor of `ASCollectionNode`. @@ -79,7 +81,7 @@ If you've used previous versions of ASDK, you'll notice that `ASCollectionView` `ASCollectionView` (an actual UICollectionView subclass) is still used as an internal property of `ASCollectionNode`. While it should not be created directly, it can still be used directly by accessing the .view property of an `ASCollectionNode`. -**Do not forget that anything that accesses a view using AsyncDisplayKit's node containers or nodes should be done in viewDidLoad or didLoad, respectively.** +
Do not forget that anything that accesses a view using AsyncDisplayKit's node containers or nodes should be done in viewDidLoad or didLoad, respectively.
The LocationCollectionNodeController above accesses the ASCollectionView directly in viewDidLoad