Quote:
Originally Posted by coondog
Thank you for the advice.
Question: Why then wouldn't you simply have an instance of your model in the app delegate and have each controller access it via the delegate pointer?
Chris.
|
If the app is simple, you could do that. But once the app grows a bit, I think you'll find the app delegate has taken on too much at that point. Especially when model data is really being loaded from disk or the net. Then loading that model data (and checking for errors, timeouts, etc.) is a fair amount of code that sits better in its own controller.
