Closed bradleydwyer closed 13 years ago
same problem.. i try to fix it but i think that is a conceptual problem.
Yes, I believe it has to do with modifying the parentViewController directly (against the rules). In iOS 5, the hierarchy backend changed quite a bit ... there's now something like addChildViewController ... in a sense, the way it's done in CLCascade is the hierarchical opposite of the way it's done in iOS 5
How we can fix it? that problem needs to change the conceptual structure of CLCascade or i can substitute parentViewController with addChildViewController?
chemicalweb: Take a look at session 102 from the 2011 WWDC. It is the start of the answers you're looking for.
The UIViewController class now allows you to define your own custom container view controllers and present content in new and interesting ways. Examples of existing container view controllers include UINavigationController, UITabBarController, andUISplitViewController. These view controllers mix custom content with content provided by one or more separate view controller objects to create a unique presentation for application content. Container view controllers act as a parent for their contained view controllers, forwarding important messages about rotations and other relevant events to their children.
BUT, current documentation is very poor, so I wait until it turns.
On the pre-release apple forums, a few folks have posted some demo code for the container methods.
g
On my fork, I've been playing around with iOS 5 code, and I added [self addChildViewController:viewController];
to the CLCascadeNavigationController in addViewController:sender:animated:
.
Check out my fork and grab the code if you'd like. I'm not quite sure if we need to go about "removing" the child view controllers, or if when they get nil'ed out they stop being children.
in master branch ios5 is now supported ;)
Haven't dug into this, but it appears there is a problem running under iOS 5. The app crashes after attempting to open a 2nd level in the cascade view.