i have a TabBar with 5 ViewControllers. i am using that array of tabBarController to populating a SideBarMenu like in Facebook app.
When i use a viewController to set as RootViewController of UINavigationController, then this viewController gets removed from the array [self.tabBarController viewControllers].
Why is this happening and how can i prevent this?
return [[UINavigationController alloc] initWithRootViewController:
[[self.tabBarController viewControllers] objectAtIndex:0]];
the viewController at objectIndex 0 gets removed and the [self.tabbarcontroller viewControllers] is returning only 4 viewControllers.
A UIViewController can only have one parent. When you add the view controller from the tab bar to the navigation controller, the navigation controller detached the view controller from its previous parent and attaches it to itself. For more information about why this happens, read the Implementing a Container View Controller section of the UIViewController documentation.
Related
i have NavigationController base application but i need TabBar in the bottom only on the Two Scene not for the whole app. Anyone have any idea about it.
Waiting your kind response.
i have found a solution By creating a very simple thing as making a UIView using storyboard and add Button of custom type and then push and pop ViewControllers by using Following button actions
- (IBAction)pushToSecondVC:(id)sender {
UIViewController *tab2vc = [[UIStoryboard storyboardWithName:#"MainStoryboard" bundle:nil] instantiateViewControllerWithIdentifier:#"SecondViewController"];
[self.navigationController pushViewController:tab2vc animated:NO];
}
and for the back button in the second ViewController
-(IBAction)goBackToPreviousController:(id)sender{
[self.navigationController popViewControllerAnimated:NO];
}
To create from code a parent/child relationship between 2 view controllers basically it's just matter of doing something like:
[self addChildViewController:childViewController];
[self.view addSubview:childViewController.view];
where self is the parent view controller.
But, what if I want to create the same relationship completely from Interface Builder?
Or in other words: is there a way to re-create the behavior of the method addChildViewController using Interface Builder?
I didn't find a lot of documentation about that, here is an old unresolved post about the topic: https://devforums.apple.com/message/455758#455758
Without properly setting up the addChildViewController relationship, none of the rotation methods are forwarded to my child view controller, here where my question come from.
This is what I've done in IB:
drag and dropped a "View Controller" object from the "Object Library" panel into the "Objects" panel
in the identity inspector I've changed its class to my UIViewController subclass ("Items View Controller")
connected the view outlet to the controller
connected all the other required outlets to the controller (List name, Table View)
The first "View" object in the picture is the view of my parent view controller, instead the highlighted "View" is the view of the child view controller ("Item View Controller").
The container controller also retain its child instance through an additional IBOutlet:
#property (nonatomic, strong) IBOutlet ItemsViewController *itemsViewController;
Thanks
Update 1: If I manually set the parent/child relationship in viewDidLoad of the container controller, all the rotation methods are correctly forwarded to the child.
[self addChildViewController:self.itemsViewController];
But I don't really know if this is the correct way of doing that, since I would like to do all using IB.
Update 2: Thanks to #micantox for his hint to use the "Container View" in the Object Library, I have converted my xib file to a Storyboard and now the child view controller is added to its parent, so I don't have to add it manually from code with addChildViewController and the rotation methods are forwarded as expected.
"Container View" basically implements the embed segue and is supported only from iOS 6.
This is an updated screenshot from my Storyboard:
The right way of creating container views for child view controllers is through the use of the object "Container View" in the Object Library. Dragging one in your View Controller's scene will create a new scene for the child view controller that can be managed separately from the the parent view controller.
Also, if you're trying to create an embed segue to an existing view controller in your storyboard, control-drag from the container view, not the container VC, to the VC you want to embed.
A very simple way to do it is just instantiate the child view controller by referencing its storyboard ID:
UITableViewController *childViewController = [self.storyboard instantiateViewControllerWithIdentifier:#"childViewController"];
[self addChildViewController:childViewController];
[self.view addSubview:childViewController.view];
That way, you can build both view controllers in interface builder. You can set the storyboard ID in interface builder: select the view controller and you'll see a field for it in the identity inspector.
I'm trying to work out how I can get my UIBarButtonItem named "home" to return back to my first initial ViewController.
I have implemented my button within the viewDidLoad of my ViewControllerSecond:
#property (nonatomic, weak) UIBarButtonItem *homeProperty;
// Create a home button
UIBarButtonItem *homeButton = [[UIBarButtonItem alloc] initWithTitle:#"Home" style:UIBarButtonItemStylePlain target:self action:#selector(homeProperty)];
[self.navigationItem setLeftBarButtonItem:homeButton animated:NO];
Do I need to create an IBAction method for this? Also, is the UIBarButtonItem implemented in the correct method viewDidLoad
So to summarise I need to be able to go back to the ViewController from the ViewControllerSecond but I can't figure out how to do this.
Many thanks
How are you adding the second view controller to the first? Are you calling pushViewController or presentModalViewController? If you're using a UINavigationController, calling pushViewController should automatically create the back button for you on the navigation bar. Create a new project in XCode using the Master-Detail Application too see an example of how UINavigationController should work.
I got a very interesting problem here. My iPhone app has an UITabbarController as rootViewController in the AppDelegate.
If the app is opened the first time, it must be configured basically. For this purpose I create an UINavigationController and tell the tabbarController to present it modally:
firstRun = [[firstRunViewController alloc] init];
navCtrl = [[UINavigationController alloc] initWithRootViewController:firstRun];
[[self tabBarController] presentModalViewController:navCtrl animated:NO];
When the configuration is done, I'd like to get rid of the firstRunViewController. I'm using this technique very often, using -dismissModalViewControllerAnimated:.
But in this constellation this doesn't work. It doesn't matter from what controller I'm calling the dismiss.
I tried it via the tabbarController, the rootViewController, the currently active viewController, of cause self and several other controllers.
EVERY TIME I call -dismissModalViewControllerAnimated: I get this exception:
'UIViewControllerHierarchyInconsistency', reason: 'presentedViewController for controller is itself on dismiss for: <UINavigationController:…
Can anybody help? Thanks in advance, with kind regards, Julian
EDIT
In my AppDelegate I'm using a UITabbarController as rootViewController for the main window:
self.window.rootViewController = self.tabBarController;
[self.window makeKeyAndVisible];
Then I'm creating an UINavigationController and tell the UITabbarController to present the modalViewController:
UINavigationController *navCtrl = [[UINavigationController alloc] initWithRootViewController:firstRun];
[[self tabBarController] presentModalViewController:navCtrl animated:NO];
When I now call -dismissModalViewControllerAnimated: on the firstViewController I'm getting the error from above.
In my opinion you are abusing UITabbarController. This class, even though a subclass of UIViewController, does not really use much of the UIViewController infrastructure.
What you want is a slight extension of what you have now. Create a new UIViewController subclass in your appDelegate, and add it as the single object to an array, and set the tabBar's viewControllers to this array. Set your subclass' hidesBottomBarWhenPushed to YES so it hides the tab bar when it becomes visible.
Now your app will launch and your UIViewController subclass will become the frontmost view. You can make this view the one you wanted to present modally, or you can present that view from your subclass using some kind of animation. Oh, and if you use the launch view as the background image for your subclass, you can really make this a smooth transition - I do this now.
When your modal view is done, then you can instantiate whatever views you want to then display, and set the UITabBarController to use those views with tabBarController.viewControllers (or the animated version). Poof, you UIViewController will get replaces (and under ARC just disappear).
I don't have a chance to test my hypothesis, but I suspect that this issue could depend on the fact that you are presenting the modal view too early, whereby too early means before the main window has had the chance to set up the tab bar controller. So, I would suggest this changes:
create a method to instantiate your navigation controller:
- (void)initializeAndPresentNavigationController {
UINavigationController *navCtrl = [[UINavigationController alloc] initWithRootViewController:firstRun];
[[self tabBarController] presentModalViewController:navCtrl animated:NO];
}
instead of presenting the navigation controller directly from appDidFinishLaunching, call the above method asynchronously:
[self performSelector:#selector(initializeAndPresentNavigationController) withObject:nil afterDelay:0.0];
Here the trick of calling the method as I do in 2 is that the call to initializeAndPresentNavigationController will be simply pushed on the main loop, and executed after your app has had the possibility to build its initial UI.
Hope it works for you.
I finally found the answer myself!
I just couldn't see the wood for the trees! I'm quite happy right now! :)
I did really silly things: In the last viewController of the setup viewControllers I had to change the tabars viewControllers corresponding to whether the user is administrator or not. So I did:
appDelegate.tabBarController.viewControllers = [NSArray arrayWithObjects:appDelegate.readState,
appDelegate.navCtrl,
appDelegate.settings, nil];
You can see that I was adding the AppDelegate's "navCtrl" to the tabbar's viewControllers. So I was trying to dismiss a viewController I just added to the parentViewControllers (UITabbarController) sub-controllers.
Dismissing something I want to present just in the same moment is NOT advisable! :))
I've got a UIViewController that has a modal window which I'd like to present over the entire interface, including the UITabBar.
My application hierarchy is this:
UITabBarController (A) ->
UIViewController (B) ->
UINavigationController (C) ->
UIViewController (D) ->
UIViewController (my modal view)
When I call presentModalViewController on D, the modal view is presented but underneath the UITabBar, or should I say, the UITabBar is still shown.
I've tried setting the hidesBottomBarWhenPushed property to YES on the modal view controller, but to no avail.
Any ideas on why this isn't working for me?
The modal ViewController needs to be a direct child of the TabBarController in order to do what you want.
in ViewController "D", instead of :
[self presentModalViewController:...];
do:
[tabBarController presentModalViewController:...];
how you maintain a reference to the TabBarController is up to you.