Problems when split views are pushed onto "More..." tab

[underbjerg]

First of all, thanks a lot for making this solution available. I'm in the process of integrating it into our app, and so far your solution is much cleaner than our old hack, and has fixed a number of bugs were having trouble with.

One problem I have run into though, is that when the number of tabs increases beyond capacity of the tab bar, forcing entries onto the "More..." tab, we can no longer open the entries containing split views. When we try, we get an error similar to:

"Split View Controllers cannot be pushed to a Navigation Controller <UIMoreNavigationController: 0x93b6950>"

I believe it happens because the "More..." tab wraps each entry in a navigation controller, so that the user get's a nice "back" button to the "More..." tab after selecting an entry. And of course, the default UISplitViewController doesn't like that.

Have you found a solution to the problem, or do you have any suggestions for making it work?

Thanks again.

[grgcombs]

Oh crap. That is something no one (to my knowledge) has tried yet untl now. The way I've set it up will fully fly smack into the face of the More tab. I think it would take significant hacking to overcome this issue due to the way Apple implemented the UIMoreNavigationController.

I think you may need to try out a few third party tab bar controllers or do a custom one. Hear me out, if you check out Tweetbot, you'll see how they have a popup menu in place of a More tab. Something like that might suit your needs. That way you can bypass the navigator controller hacking to fix the problem you described. This popup would work if you had a relatively small number of items in the menu. Customizing the list, like changing in/out tabs would have to be a separate process ... No more dragging tabs around like in the UIMoreNav ...

Or, with the new view controller containment methods in iOS 5, it may be possible to build a custom tab bar controller that does the right things without even needing the IntelligentSplitViewController class at all.

Outside of these possibilities, there may be a modernized fork of MGSplitViewController that behaves more appropriately.

Greg

Sent from my iPhone.

On Feb 9, 2012, at 3:24 AM, "Erik L. Underbjerg"reply@reply.github.com wrote:

First of all, thanks a lot for making this solution available. I'm in the process of integrating it into our app, and so far your solution is much cleaner than our old hack, and has fixed a number of bugs were having trouble with.

One problem I have run into though, is that when the number of tabs increases beyond capacity of the tab bar, forcing entries onto the "More..." tab, we can no longer open the entries containing split views. When we try, we get an error similar to:

"Split View Controllers cannot be pushed to a Navigation Controller <UIMoreNavigationController: 0x93b6950>"

I believe it happens because the "More..." tab wraps each entry in a navigation controller, so that the user get's a nice "back" button to the "More..." tab after selecting an entry. And of course, the default UISplitViewController doesn't like that.

Have you found a solution to the problem, or do you have any suggestions for making it work?

Thanks again.

---

Reply to this email directly or view it on GitHub:
#11

[underbjerg]

Yeah, we investigated a little, and it seemed to required substantial hacking to get it to work. We will try a recent fork of MGSplitViewController to see if that fixes it. If not, we will probably have to re-design our app. Controller containment is definitely one of the things we should investigate.

Thanks for the tips, and taking the time to answer!