Note that there are some explanatory texts on larger screens.

plurals
  1. POIs there any way that I can manipulate the parent view controller so that the subviews will be underneath the UIPageControl?
    primarykey
    data
    text
    <p>I'm implementing horizontal scrolling in an app by making use of an UIPageViewController which I set the navigation property to 'Horizontal' and the Transistion Style to 'scroll'. Everything works fine, I can add some subviews that are presented properly. I also want to make use of the built in UIPageControl that UIPageViewController has by making use of these two methods:</p> <pre><code>-(NSInteger)presentationIndexForPageViewController:(UIPageViewController *)pageViewController -(NSInteger)presentationCountForPageViewController:(UIPageViewController *)pageViewController </code></pre> <p>This is actually showing what I'm looking for: dots that indicates which subview is shown. But, as you can see in the image, the UIPageControl is set at the bottom of the parent viewcontroller (the UIPageViewController). You can imagine that this is not the way I had in mind to present my UIPageControl. Is there any way that I can manipulate the parent view controller so that the subviews will be underneath the UIPageControl? Or is there any other good practice to achieve this? I know I could implement horizontal scrolling by using a scrollView instead of an UIPageViewController, but this seems much more efficient by me. </p> <p><a href="http://i48.tinypic.com/2hd03ev.png" rel="nofollow">http://i48.tinypic.com/2hd03ev.png</a></p> <p>For the clarity: The gray part is my subview and the red part is the underlaying UIPageViewController that I'm using. </p> <p>Thanks in advance for any answer!</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload