Create a Paging Scroll View using NSLayoutAnchor and UIStackView

Today I wanna show you how to implement a Paging Scroll View programmatically using some cool AutoLayout APIs. You might be asking “Why do this programmatically?”. Truth is, you could do a mix of storyboard or completely in storyboard and get the same result.The reason is that in my next tutorial Adding a Parallax Effect to a UIScrollView using NSLayoutAnchor I create a parallax effect with the header and paragraph text that is easier when done all programmatically. It’s also surprisingly simple! Let’s get going!

Before we get started you should grab the starting project here on GitHub. You’ll also want to take note of the versions I’ve used to create this project.

Xcode 8.3.3

Swift 3.1

If you have all those things then let’s get started. This is what you’ll have by the end of this post.

Paging Scroll View

Setup the ScrollView

This is where we need to start because this is where all the subviews will go. Open up the project and go into ViewController.swift and scroll down to the setup() method. You should see a comment stating where we’ll be doing the setup. Just below the comment, we’ll add the following code.

Here you can see some pretty self-explanatory changes to scrollView. The oddest piece has to do with .translateAutoresizingMaskIntoConstraints and that just tells our scrollView to assume nothing and let us tell it where to go and how to size itself.

Here I add the scrollView to our ViewController view and use NSLayoutAnchor to perform some AutoLayout magic. If you’re unfamiliar with how this works you should go check out my post on Getting Started with NSLayoutAnchor and then head back over.

If you run the simulator now you’ll see a very unimpressive black screen. Let’s keep going.

Setup the Stackview

If you’re unfamiliar with UIStackView that’s okay. UIStackView was introduced in iOS 9 and provide an incredibly easy way to create basic layouts. You essentially just add objects and it’ll do its best to guess how you want them laid out. You’ll typically need to tweak a few settings but overall makes for a lot less code than other methods of AutoLayout. You can read up on it here in Apple’s documentation. Add this code below the code we just added.

Here we’ve made sure again that the stackView will only use our directions to size itself. We’ve also told it to give .equalSpace when distributing things. That has to do with the subviews it’ll be arranging later when we add them.

We’ve added the stackView as a subview to our scrollView. The cool thing about all of this is based on the content we add to stackView later our scrollView will dynamically size itself to fit stackView because of these constraints.

There’s one last thing to do before we get to see some amazing scrolling action. We need to add our pageViews to the stackView and set their constraints. I added each view to an array called views that will help us avoid repeating code. Below the part where we initialized all the PageViews we need to add this code.

Calling the method .forEach on the array equivalent to performing a for-in loop on the array. Either will work but I like using this method.

To add our views to the stackView we need to call .addArrangedSubview and add the view. If you use the vanilla .addSubview you won’t get the desired result of the stackView arranging the views for us.

Build and run the project. Colors! We finally have some scrolling going on. You might’ve noticed an issue. When we scroll it doesn’t snap to one whole page when we quit.

Luckily, this is a really easy fix. Go back up to where we set up the scrollView and add the following line of code.

Enable Paging

Swift

1

scrollView.isPagingEnabled=true

Build and run the project again and the problem should be fixed. We’ve officially got some nice paging action. We’re done with the main feature but it’s not polished. To make it a better experience scrolling we should add margins between our views. We’ll do that next.

Add Margins between the Views

Alright, so we need to make three different changes.

Adjust the scrollView leading and trailing anchors so that they extend an additional 10 points on either side.

Since we set out stackView anchors equal to the scrollView anchors we need to counter those changes by bringing the stackView anchors in 10 points. This is important because otherwise our views would end over the edges too.

Tell the stackView to put a 20 point spacing between the views to match the 10 point margin we put around each view.

The first changes we’ll make will be where we set up the scrollView. Jump into the array of NSLayoutConstraints and we’ll add a couple constants to extend 10 points to the left and 10 points to the right.

To move the constraint 10 points to the left we need to subtract 10 points. That’s because the coordinate system starts in the top left and extends down and to the right.

We add 10 points here to move our trailing edge to the right 10 points.

We need to do the exact opposite to the stackView constraints because we want it to be fully in view the entire time. Take a look at the stackView array of NSLayoutConstraints and see if you can figure out what the changes need to be.

That’ll do it for adjusting the constraints. The last thing we need to do is tell the stackView to put 20 points of spacing between our views. It needs to be 20 points because each view gained a 10 point margin meaning that when they’re put together it becomes a 20 point gap. Add the following single line of code to where we setup the stackView.

Add this to the stackView setup

Swift

1

stackView.spacing=20

With that last line of code, you can run the project and see the new margins. We’ve gotten a lot done. There’s one last thing that the Paging Scroll view is missing though and that’s a page control. You typically see a little indicator at the bottom indicating what page you’re on. We’ll add that next.

Adding a Page Control

The starter project included a property called pageControl that’s ready to setup. Find the comment at the bottom of the setup() method and add this code.

We set the .numberOfPages property to the views.count so it knows the number of views that will be displayed.

Here we’re connecting an action to the pageControl so we can do something when we tap the control. We haven’t added the pageControlTapped function yet so we’ll take care of that next.

You should see an error right now that says use of unresolved identifier ‘pageControlTapped(sender:)’. That’s because we haven’t added it yet. Just below the setup() method, we’ll add this new method to pacify the error for now.

Add Action for the pageControl

Swift

1

2

3

funcpageControlTapped(sender:UIPageControl){

print("Tapped")

}

We’ll come back to that method shortly. We need to next give our pageControl the ability to calculate what the current page is. We’ll do that by setting our ViewController as the UIScrollViewDelegate and using the scrollViewDidScroll method. First, add this line of code to where we set up the scrollView.

Set the ViewController as the delegate

Swift

1

scrollView.delegate=self

This means that our ViewController is now the delegate for our scrollView. Next, we’ll add an extension and add a few variables to calculate what the current page is depending on our scrollView content offset. Add this code to the bottom of ViewController.swift and outside of the class declaration. Heads up, you’ll need to make pageControl public by removing the private accessibility from the declaration at the top.

Swift

1

2

3

4

5

6

7

8

extensionViewController: UIScrollViewDelegate{

funcscrollViewDidScroll(_scrollView:UIScrollView){

letpageWidth=scrollView.bounds.width

letpageFraction=scrollView.contentOffset.x/pageWidth

pageControl.currentPage=Int((round(pageFraction)))

}

}

You can see that we grab the pageWidth of our scrollView and use it to divide the contentOffset on the X axis. The contentOffset is just the distance we’ve scrolled from the starting point. Imagine the pageWidth is 100 and our contentOffset is 200. That gives us 2 as the outcome meaning the currentPage would be assigned 2. To make sure our current page isn’t some crazy floating number we round it and then type cast it to an Int. These calculations will occur every time the scrollView scrolls meaning when we scroll over a half page the pageControl will update to show we’re on the next page.

The last thing we’ll do is revisit the pageControlTapped method. When we tap on the pageControl the goal is to animate to the page we’ve tapped on. Replace the print statement with the following lines of code.

Animate clicks on the pageControl

Swift

1

2

3

4

5

6

7

// [1]

letpageWidth=scrollView.bounds.width

letoffset=sender.currentPage*Int(pageWidth)

// [2]

UIView.animate(withDuration:0.33,animations:{[weakself]in

self?.scrollView.contentOffset.x=CGFloat(offset)

})

Here we’ve calculated the distance we need to animate to display the page that was tapped on.

Lastly, we animate using this animation method and closure. To do that we set the scrollView.contentOffset.x equal to the spot we need to be displayed. The wonky “[weak self]” syntax is a capture list I’ve used to avoid a strong reference cycle.

With that final piece of code, you’re finally done! You should be able to run the project and click on the pageControl to change the currently displayed page. Pretty cool huh? That’ll be it for this post. To make it more fun though I’ll show you next week how to add a fun parallax effect to really wow users.