Quote:
Originally Posted by coondog
The only place I can think to put that code (so it will be global) is in the AppDelegate, but, is that bad form?
|
Well, Chris, I came here to ask almost the exact same question!
Many controllers need to access the same object instances. From what I've seen online, it seems everyone just puts these instances in their AppDelegate. This doesn't really sit well with me, but the only other solution I can think of is to make my classes instance-aware, so that I can grab the appropriate instance via static methods on my classes. But THAT also seems like an ugly solution. (Though I like it a little bit better than relying on AppDelegate.)
So if someone out there would enlighten us as to best practices, I think it would be valuable for everyone who happens across this thread.
Thanks.
