Re: Re: CarbonView newbie
Re: Re: CarbonView newbie
- Subject: Re: Re: CarbonView newbie
- From: <email@hidden>
- Date: Tue, 15 Jun 2004 23:07:09 +0000
>
From: Marc Poirier <email@hidden>
>
Date: 2004/06/15 ti PM 08:36:38 GMT
>
To: email@hidden
>
CC: CoreAudio API <email@hidden>
>
Dmne: Re: CarbonView newbie
>
>
That rephrasing helps, at least for me. :)
>
>
Okay, first a conceptual clarification: Your AUCarbonView does not create
>
a window. The host creates a window and then gives your AUCarbonView a
>
reference to the window. Your AUCarbonView then in turn creates a
>
Carbon "pane" control, which is your root control that you own and which
>
you do all of your stuff within, and then you embed that pane control into
>
the host's window at the offset where the host has asked you to place it.
>
Most of this is handled fine by AUCarbonViewBase, but anyway, that's
>
what's going on.
>
>
To make a window materialize, you do whatever it is in the host app that
>
tells the app to open a window for the AU. I'm not sure what exactly
>
you're doing and where exactly something is going wrong, but if you have
>
gone to that point and then something goes wrong (does the Generic AUView
>
open, or no window, or what?), then I'm going to guess that maybe the host
>
is not opening your custom view because it is not aware that you have one.
>
In order to inform the host that you have one (or more), you need to
>
support the kAudioUnitProperty_GetUIComponentList property. You can do
>
that by overriding the AUBase methods GetNumCustomUIComponents() and
>
GetUIComponentDescs().
>
>
I'm not sure if any of this is the info that you need, but I hope some of
>
it helps...
Well, I think I had this grasped already. My Editor does start up and
happily communicates with the AU it is supposed to control. It also
receives a windowRef from the host and I thought that meant that the
host had opened a window and that the windowRef could be used to draw
stuff and whatever you want to do with a window. But I see no window.
/Olof W
>
>
Marc
>
>
>
>
On Tue, 15 Jun 2004 email@hidden wrote:
>
>
> Let me rephrase the 'question'
>
>
>
> My AudioUnitEditor inherits AUCarbonViewBase. Is that enough
>
> to make a window appear on the screen? What do I have to do
>
> in order for an empty window to actually 'materialize'?
>
>
>
> /Olof W
>
>
>
> >
>
> > From: <email@hidden>
>
> > Date: 2004/06/15 ti PM 03:27:16 GMT
>
> > To: CoreAudio API <email@hidden>
>
> > Dmne: CarbonView newbie
>
> >
>
> > I have some problems with making a CarbonView editor for my
>
> > MusicDevice. I sort of started out with the GenericCarbonView
>
> > sample but the component would not register until I changed
>
> > the entry point specified in the GenericAUView.r. What is that
>
> > 'Shim' at the end: 'GenericAUViewEntryShim' ?
>
> >
>
> > Well, I threw away most of the contents of GeneriAUView
>
> > and now I have something that starts up and communicates
>
> > with it's AU. It also receives a windowRef and it can use that
>
> > to resize and draw without causing errors or crashes.
>
> > However, there is no window ever appearing on the screen,
>
> > no graphics, nuthin!
>
> >
>
> > I am novice when it comes to Macintosh in general not just to
>
> > CarbonViews, btw.
>
> >
>
> > /Olof W
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.