One feature of Objective-C I find highly annoying and error-prone is the silent failure of calling a method on a null object. After your first line in the setupToolBar method, check if the navigationController is null.
One feature of Objective-C I find highly annoying and error-prone is the silent failure of calling a method on a null object. After your first line in the setupToolBar method, check if the navigationController is null: NSLog(@" navigationController is 0x%x", self. NavigationController); Is the navController created in the same manner for the restart case as in the regular case?
Thanks for the lead Mike - tried it - unfortunately it seems to be OK (i.e. It doesn't seem to be the problem in my case) - I got "navigationController is 0x553e780" in the case where the toolbar is not there – Greg Apr 16 at 13:58 In your 2nd view controller, look for hidesBottomBarWhenPushed and NSLog that value. If it's not there at all, set it in your init method and try both URL1 may be defaulting to an unexpected value.
– Rayfleck Apr 16 at 14:25 thanks - unfortunately this didn't help (if it had of I would never have found it through) – Greg Apr 16 at 21:26.
I worked out how to fix this through process of elimination, but I don't understand why :) So what fixed it was changing the following line in the application delegate's "didFinishLaunchingWithOptions" method: // OLD Entry - Did not work //self. Window addSubview:navigationController. View; // NEW Entry - Fixed it self.window.
RootViewController = self. NavigationController; Any ideas why?
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.