📖 A lightweight, paging view solution for SwiftUI

Hello, I am trying to make a TikTok style UI.

I have tried this:

struct ContentView: View {
     @State var index: Int = 0
   var body: some View {
            Pages(currentPage: $index, navigationOrientation: .vertical) {
                Image("ModelX")
            }
        }
    }

However I get this error:Cannot convert value of type 'Image' to closure result type '[AnyView]'

I have also tried doing this:

struct ContentView: View {
     @State var index: Int = 0
   var body: some View {
            Pages(currentPage: $index, navigationOrientation: .vertical) {
                NewsView()
            }
        }
    }

struct NewsView: View{
    var body: some View {
        Image("modelX")
    }
    
}

However I get the same error but lightly different: Cannot convert value of type 'NewsView' to closure result type '[AnyView]'

Anyhelp is appreciated, I am not a noob but I am new to swiftUI

I have follow situation. struct HomeView { ... Pages(currentPage: self.$currentPage) { ChannelsView() PublicationsView() MarkedView() } ... The problem is coming from that in PublicationsView, Im realoading some data and view should be rendered again. Then "controllers" array is updated and refill with newest views. But in the Coordinator the parent reference keep the first "controllers" array. That follow to a bug: in "viewControllerBefore" and "viewControllerAfter" -> "parent.controllers.firstIndex(of: viewController)" is returning nil and the pages cannot be changed. I cannot find a easy solution. Could you help me?

Thanks for a great library!

I am facing a problem where scrolling stops working when the view hierarchy changes. At first, everything works great. However, if I modify the view hierarchy in any way (e.g. by setting a state property that causes a label to change), the page view's scroll just starts bouncing back. The problem appears in both Pages and ModelPages.

Do you have any idea what may be causing this?

UPDATE The problem exists in 0.1.3, but is solved in master. Can you consider making a 0.1.4 version of master?

How do we integrate navigation link with pages? I have tried the code below. The view shows it was clicked (visually), however no desination is actually navigated to.

    var body: some View {
        ModelPages(cars) { index, car in
NavigationLink(destination: DestinationView(car: car)) {
            Text("The \(index) car is a \(car.model)")
                .padding(50)
                .foregroundColor(.white)
                .background(Color.blue)
                .cornerRadius(10)
        }
    }
}

Hi, background colors of the ViewController's.view should be .clear.

PageViewController.swift:52 Pages.swift:105 ModelPages:115

I somehow cannot create a brach....

Hello, I am trying to make a UI like TikTok but the images are behaving weirdly. It works fine on my 11 pro max but not on a screen size smaller, it sort of jumps around. Screenshot

Pages image issue (clipping)

Hi, firstly I wanna say thanks for this package.

I tried to use dynamic page with my ViewModel data but when I tried to run the app, I got to crash with an index out of range error.

Fatal error: Index out of range

View:

struct SliderNewsList: View {
    @ObservedObject var viewModel = SliderNewsVM()
    @State var index: Int = 0
    
    var body: some View {
        ModelPages(viewModel.news, currentPage: $index) { pageIndex, new in
            Text(new.title)
        }
    }
}

ViewModel:

class SliderNewsVM: ObservableObject {
    
    @Published var news = [SliderNews]()
    
    init() {
        fetchSliderNews()
    }
}

extension SliderNewsVM {
    func fetchSliderNews() {
        ApiManager.shared.fetchSliderNews { [weak self] result in
            guard let self = self else { return }
            switch result {
            case .success(let result):
                self.news = result
            case .failure(_):
                print("error")
            }
        }
    }
}

I would be very interested in being able to dynamically remove a page by, say, clicking on a button on said page. Currently, this is not supported and if the data element is removed, PageViewController crashes with index out of range.

When i want to show current index, rightToLeft swipe is not working. If i enter to some text (like Text("Test header"), it's working. Really interesting.

`import Pages

struct WelcomeView: View {

@State var index: Int = 0

var body: some View {
  VStack {
    Text("\(index)")
    Spacer()
    Pages(currentPage: $index) {
         Text("Welcome! This is Page 1")
         Text("This is Page 2")
         Text("...and this is Page 3")
         Circle() // The 4th page is a Circle
    }
  }
}

}`

For example, we open a book, stopped reading at page number 33. The book resumes at page 1 and we have to flip page by page until page number 33. If the book resumes at page 33, it would be great.

The adaptation to SwiftUI works great thanks. I needed this for pageCurl transition and not the scroll transition. However, the transition animation does not work properly. The top page curls up nicely and the next page is visible behind it. However, when the animation is complete the second page curls away too leaving a blank white page. There is an error message shown "Unbalanced calls to begin/end appearance transitions" .

Two things - (1) this problem does not occur when the transition type is scroll -only there for pageCurl type. (2). if I comment out the UIPageViewControllerDelegate method didFinishAnimating finished the problem goes away - the transition works nicely.

I am not sure that the problem is your code, because I get the same problem just using the code in the tutorial from Apple ( https://developer.apple.com/tutorials/swiftui/interfacing-with-uikit ) .

I can send you the complete example if needed. I am hoping that you can figure out a solution.

I'm having an issue with the library, where any time any of my other state variables change on page, the animation triggers.

If I've got a Page 0, and a Page 1, the "moving back to 0" animation triggers anytime a variable changes on page 0 (UX element, etc).

Is there any way to prevent this from happening?

This PR makes the UIPageControl instance know about changes to the number of pages (which seem to be correctly updated on the PageControl instance already).

Hi, this is an amazing package, thanks! Is there a way to modify the code to only allow page turning when swiping? I have views with .onTapGesture{} placed near the edge and it's causing the page to turn instead of performing the function I'm calling. I was looking at the files in this package but can't seem to figure out if this an be done.

I have a menu that changes the content shown on the screen. In two of the different views I used Pages. Showing the first instance of Pages works fine, but when I go to the other view with an instance of Pages, the Pages view flashes and then disappears. Then if I try to go back the other one disappears as well. If I remove one instance of Pages it works fine.