Skip to main content

NavigationControllers and UITabBar



I have my app like this : a navigationBar in the app delegate with have a Controller1(UIViewController) like a rootController, in the controller1 i push controller2 ( UIViewController), the controller2 have 3 UINavigationController, and a Custom tabBar, each navigationController have a root controller, and finally i put all the navigationController in the CustomTabBar.





My question is : is this clean( good) to do like this ? If no how i can organize my project ?







MyAppDelegate.h

@property (strong, nonatomic) UIWindow *window;

@property (strong, nonatomic) UINavigationController *navigationController;

@property (strong, nonatomic) CustomTabBar *tabBarController;



MyAppDelegate.m {

UIViewController *controller1 = [[UIViewController alloc] initWithNibName:nil bundle:nil];

self.window = [[UIWindow alloc] initWithFrame:[[UIScreen mainScreen] bounds]];

// Override point for customization after application launch.

self.window.backgroundColor = [UIColor whiteColor];

navigationController = [[UINavigationController alloc] initWithRootViewController:controller1];

self.window.rootViewController = navigationController;

}



controller1.h

UIViewController controller2;

UINavigationController *navigationController2;



UIViewController controller3;

UINavigationController *navigationController3;





UIViewController controller3;

UINavigationController *navigationController3;



controller1.m

-(void)viewDidLoad{



viewController1 = [[UIViewController......

navigationController1 = [[UINavigationController alloc] initWithRootViewController:controller1];

....



AppDelegate *apDelegate= [UIApplication sharedApplication].delegate;



apDelegate.tabBarController = [[CustomTabBar alloc] initWithNibName:nil bundle:nil];

[apDelegate.tabBarController setViewControllers: [NSArray arrayWithObjects:navigationController1,navigationController2,navigationController3,nil]];

}




Comments

  1. This is an excerpt from the apple documentation:


    When deploying a tab bar interface, you must install this view as the root of your window. Unlike other view controllers, a tab bar interface should never be installed as a child of another view controller.


    From my point of view it's a bit tricky from the start to sort out how to use UITabBarController class, so in this case the better approach is to see some good manual. For me this one helps always when I start to mess around with this UI thing :)

    Good luck.

    ReplyDelete
  2. Set the tabBarController as rootViewController of window object:

    self.window.rootViewController = tabBarController;


    Or you can set tabBarController.view as subview of window object:

    [self.window addSubView:tabBarController.view];

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex