So, I'm trying to create an application in which you can scroll through three views, which are the screen size, each of which has its own UITableView. At first I did this using a UIScrollView, but it seemed too heavy for memory, so I decided to change the structure for the PageViewController with three child view controllers.
The problem I am facing is that I get a delay in passing: when I first come to the mid-view controller (which the application should do), if I scroll left or right, I like half the second freeze, and then it works fine. From there, if I scroll back and forth between this view controller and the central one, it works fine since the ViewControllerBeforeViewController and ViewControllerAfterViewController have already returned viewControllers.
But when I try to move on to the third, I again get the backlog. Basically, if my pageViewController had two child controllers, that would be nice, but the fact that there is a third means that at some point I should return a new one, which takes time.
I think I should preload the controller, but did not defeat the goal of switching from UIScrollView to UIPageViewController? How do applications do when they have a tutorial with more than two pages, or how to do snapchat?
source
share