Probably a very basic solution

[jhockman]

I have 3 UIViewControllers. Both need to have access to the same information and be able to run the same Method.

So my main view controller handles all the info and passes it as an argument to either view controller through a common function.

so I don't have to continually check which view is active (because for the purposes of this application it doesn't matter. All I'm doing is displaying the same info two different ways) i have a separate UIViewController object that I do not initialize and instead just assign the active view controller to it.

So I have MVC, VC1, and VC2. VC1 and 2 are initialized and are their own subclass of UIViewController. MVC is of UIViewController but not initialized. When I switch views I assign MVC = VC1 or 2.

The method I need to use is not a UIViewController method so it gives me a warning saying that MVC may not respond to selector. It works fine, but I just want to get rid of the warning. How can I go about doing this if both VC1 and VC2 are their own separate subclasses of UIViewController.

The only thing I can think of is to create another subclass of UIViewController that has the method I need to use. Make both VC1 and VC2 a sublclass of that and then make MVC that class. But I'm just trying to see what other options are out there so I might learn something more.

Also if the way I am handling the separate views is way off key, dangerous, or just bad practice please help me out and suggest something better.

Thanks!

[tychop]

Why not just subclass 2 UIViews & add them to the VC (self.view = ) when needed?

"The method I need to use is not a UIViewController method so it gives me a warning saying that MVC may not respond to selector."

You need to add the method signature to the header.

[jhockman]

That's actually something I will keep in mind for the future, but for the purposes of this app I don't think that would be the most efficient way. Both views are displaying the same info but one is a map and the other is a list so they both need a completely separate set of methods to get their data to display properly. I could still do it that way, but from my understanding and how I've done it so far the VC would taking on so many protocols that it would (for me anyway) be far too cluttered to really keep track of. Correct me if I misread what you were saying. Or if you have any advice.

Thanks for the suggestion

[JDave]

Create a delegate that all 3 UIViewControlllers 'talk' to ... or manually send the data back and forth using usual class communication methods. I use a delagate when I have 3 or more viewControllers, just to simplify the code...

[jhockman]

Originally Posted by JDave

Create a delegate that all 3 UIViewControlllers 'talk' to ... or manually send the data back and forth using usual class communication methods. I use a delagate when I have 3 or more viewControllers, just to simplify the code...

Ah okay. I will try that out. Thanks!