Re: AU Cocoa UIs that open further windows
Re: AU Cocoa UIs that open further windows
- Subject: Re: AU Cocoa UIs that open further windows
- From: Brian Willoughby <email@hidden>
- Date: Fri, 11 Jun 2010 20:38:17 -0700
On Jun 11, 2010, at 18:35, Paul Davis wrote:
On Fri, Jun 11, 2010 at 8:47 PM, Brian Willoughby
<email@hidden> wrote:
As briefly as possible: Every NIB has a File's Owner object which
must see
+alloc and -init before the NIB is opened. That object is
responsible for
it's NIB, receives -awakeFromNib as well as set<OutletName> and other
callbacks. Some coders will open multiple NIBs with the same
object, making
it difficult to follow the paradigm correctly. But the correct
way is to
create a new object before each load.
Also, component services has no Cocoa knowledge, so far as I know.
so you're saying that the component (the plugin view) itself must
load/open its own NIB?
Not necessarily an NSView class, but it must be an Objective C
class. I use a controller class which is distinct from the view
classes, but it does load its own NIB, yes.
It's really helpful to understand Cocoa application development
before you attempt to load Cocoa UI from a NIB. Otherwise the ideas
can be quite foreign and perhaps seem unnecessary.
Brian Willoughby
Sound Consulting
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden