Does the NavigationController work only when placed in appDelegate?

Question

I am trying to build application that has a tab bar controller with two view and the first view contains a segmented control.
Based on the decision of the segmented control, I load the tableview. The table view has an instance of navigation Controller in which I have assigned the tableview controller as a rootview controller. When I click on any row of the table view, a new controller gets pushed on the table view. In my case, the new view does not show up on the screen, once the row is clicked. I used NSlog and checked that the views pushed on the stack are correct.
I read many threads here and saw that all of them use tabBarController and then it directly uses the navigationController and viewcontroller. Is this the only config that works ?
What if I want to have a tabBarController->tableViewController->NavigationController, isn't it possible? Can anyone please help?

Answer 1

WitchKing wrote:
So, if I understand this fully, I can initialize the navigation controller as soon as the any row is clicked and put the tableView I am on as my rootView for the navController. and also push the next view controller I want to see, on its stack. and present the navigation controller's view.
The usual way to implement a table view drill-down would be to make the first table view (or the content view which includes it) the root view of the nav controller. I.e. the table view's controller would be the root controller. When you do it that way all the objects will do what they were designed to do, and the code to push and pop subsequent views will almost write itself.
However there's no reason you can't do what you described, which (if I understood) would be to attach the nav controller's view to the hierarchy only after a row in the table is selected. Note however, that you couldn't then expect the nav controller to make that first transition from the parent table view. You would have to provide your own transition to the nav controller's view.
You bring up a good point in any case. I never explicitly answered the question in the Subject line of this thread.
does the NavigationController work only when placed in appDelegate?
No, there is no requirement to create a nav controller in any particular position of the view hierarchy. Unlike a tab controller, a nav controller need not be the root of the hierarchy (i.e. added directly to the key window). In fact you'll find several examples in the docs which show one or more nav controllers under some other controller.
there might be some problem with adjusting bar heights and etc though.
I'm not sure you proposed anything that would make it difficult to configure a table view. One nav controller issue that will impact table view position and size is the attempt to hide the nav bar which would otherwise appear above the table. I walked, unsuspecting, into this problem when I tried to help with another, currently ongoing thread that might interest you: [http://discussions.apple.com/message.jspa?messageID=9606805#9606805].
While I'm pasting links, this one is also relevant to your post: [http://discussions.apple.com/message.jspa?messageID=9607946#9607946].
Thank you for the very kind words about my posts. For some reason, this past few weeks I've been spending most of my forum helper time writing about table views and nav controllers. I sure hope I've been dispensing correct information. It's not like I have any knowlege of the internals. These puppies are black boxes to me, so I'm just going by the same docs you have and my own (growing!) collection of test beds.
\- Ray