更新

根据 Tim 的回答，我在每个 View Controller 中实现了以下内容，该 Controller 具有作为我的自定义容器一部分的 ScrollView (或子类):

- (void)didMoveToParentViewController:(UIViewController *)parent
{
    if (parent) {
        CGFloat top = parent.topLayoutGuide.length;
        CGFloat bottom = parent.bottomLayoutGuide.length;

        // this is the most important part here, because the first view controller added 
        // never had the layout issue, it was always the second. if we applied these
        // edge insets to the first view controller, then it would lay out incorrectly.
        // first detect if it's laid out correctly with the following condition, and if
        // not, manually make the adjustments since it seems like UIKit is failing to do so
        if (self.collectionView.contentInset.top != top) {
            UIEdgeInsets newInsets = UIEdgeInsetsMake(top, 0, bottom, 0);
            self.collectionView.contentInset = newInsets;
            self.collectionView.scrollIndicatorInsets = newInsets;
        }
    }

    [super didMoveToParentViewController:parent];
}

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

我有一个名为 SegmentedPageViewController 的自定义容器 View Controller 。我将其设置为 UINavigationController 的 rootViewController。

SegmentedPageViewController的作用是让一个UISegmentedControl，设置为NavController的titleView，在不同的 subview Controller 之间切换。

这些 subview Controller 都包含 ScrollView 、表格 View 或 Collection View 。

我们发现第一个 View Controller 加载良好，正确定位在导航栏下方。但是当我们切换到一个新的 View Controller ，导航栏不受尊重， View 设置在导航栏下方。

我们正在使用自动布局和界面构建器。我们已经尝试了所有能想到的方法，但找不到一致的解决方案。

这是负责设置第一个 View Controller 并在用户点击分段控件时切换到另一个 View Controller 的主要代码块:

- (void)switchFromViewController:(UIViewController *)oldVC toViewController:(UIViewController *)newVC
{
    if (newVC == oldVC) return;

    // Check the newVC is non-nil otherwise expect a crash: NSInvalidArgumentException
    if (newVC) {

        // Set the new view controller frame (in this case to be the size of the available screen bounds)
        // Calulate any other frame animations here (e.g. for the oldVC)
        newVC.view.frame = self.view.bounds;

        // Check the oldVC is non-nil otherwise expect a crash: NSInvalidArgumentException
        if (oldVC) {
            // **** THIS RUNS WHEN A NEW VC IS SET ****
            // DIFFERENT FROM FIRST VC IN THAT WE TRANSITION INSTEAD OF JUST SETTING


            // Start both the view controller transitions
            [oldVC willMoveToParentViewController:nil];
            [self addChildViewController:newVC];

            // Swap the view controllers
            // No frame animations in this code but these would go in the animations block
            [self transitionFromViewController:oldVC
                              toViewController:newVC
                                      duration:0.25
                                       options:UIViewAnimationOptionLayoutSubviews
                                    animations:^{}
                                    completion:^(BOOL finished) {
                                        // Finish both the view controller transitions
                                        [oldVC removeFromParentViewController];
                                        [newVC didMoveToParentViewController:self];
                                        // Store a reference to the current controller
                                        self.currentViewController = newVC;
                                    }];
        } else {

            // **** THIS RUNS WHEN THE FIRST VC IS SET ****
            // JUST STANDARD VIEW CONTROLLER CONTAINMENT

            // Otherwise we are adding a view controller for the first time
            // Start the view controller transition
            [self addChildViewController:newVC];

            // Add the new view controller view to the view hierarchy
            [self.view addSubview:newVC.view];

            // End the view controller transition
            [newVC didMoveToParentViewController:self];

            // Store a reference to the current controller
            self.currentViewController = newVC;
        }
    }

}

最佳答案

您的自定义容器 View Controller 将需要根据您已知的导航栏高度调整第二个 View Controller 的 contentInset，尊重 subview Controller 的 automaticallyAdjustsScrollViewInsets 属性. (您可能还对容器的 topLayoutGuide 属性感兴趣 - 确保它在 View 切换期间和之后返回正确的值。)

UIKit 在应用这个逻辑的方式上非常不一致(并且有问题)；有时您会看到它通过到达层次结构中的多个 View Controller 自动为您执行此调整，但通常在自定义容器切换之后您需要自己完成工作。

关于ios - 嵌入自定义容器 View Controller 时，内容位于导航栏下方。，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/19038949/