Re: Best way to implement calling another controller/class? [SOLVED]
Re: Best way to implement calling another controller/class? [SOLVED]
- Subject: Re: Best way to implement calling another controller/class? [SOLVED]
- From: Chad Armstrong <email@hidden>
- Date: Wed, 28 Jan 2004 15:23:28 -0600
I finally figured out how to solve this problem. Last night I
considered the use of delegates, but after reading more about
delegates, those weren't quite what I was going for. So I did a bit of
searching and (re)discovered the notification. I've already been using
notifications, just not between different classes. So I just used a
[[NSNotificationCenter defaultCenter] postNoficationName: object] call,
and this worked out great.
Chad Armstrong
On Tuesday, Jan 27, 2004, at 11:41 America/Chicago,
email@hidden wrote:
I'm trying to determine what would be the best way to implement some
functionality in one of my programs. My program has three class
controllers. One operates the functionality of the window and which
tab window should be in front. Then I have two other class controllers
which manage the functionality of each of the tabbed windows.
I want to be able to drop files onto my application, and the window
controller will take in the files, decide what to do with them, and
then send them off to the proper controller. Will I need to call a new
class instance, or can I send the information some other way, or
perhaps just make the information global between all three of the
classes?
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.