gistfile1.txt

@laumania

I'm having a bit of trouble following the thread (might be to do with it being 36deg outside and I've just done a Bikram Yoga class in a 41deg + humid room, so my body is a bit in shock!)

In general, you can't (or shouldn't) have a UITabBarController inside... well, anything. It needs to be the top, so:

UITabBarController
  + UINavigationController
    + DialogViewController / UITableViewController / Whatever
  + UIViewController
  + Whatever else

I THINK it causes problems if you dont have it like this.

I think the Master of Cheese is onto something with the UISegmentedControl (which is 100% styleable with UIAppearance BTW) however there are other ways


One of them is:
You have your UITabBarController at the bottom, with the three tabs of Politikredse, twitter and info on them (As normal, each is a UINavigationController with a DialogViewController in it)

Once someone taps on (eg) Kobenhaven, you either use PresentModalViewController (so it slides up a whole new, modal layer) and you put another tab bar controller hierachy (like the previous one) in there

or

you push something normally (which is what you are doing) and add a section + custom cell in, which changes the content based on a segmented control (use the UIViewElement, and just put a UISegmentedControl in there. When it changes, change the content of one of the sections (most likely, section[1], as section[0] is the UISegmentedControl)

Downside of the first one: you block the twitter/info buttons until its dismissed, but then it's quite close to your current model, because you are trying to replace them anyway. That might be your intended result.

Downside of the second one is, it's a bit weird for the user....