Re: 2 AUCocoaView implementation questions: How to deal with uninitialized AU, and restrict Host to single view.
Re: 2 AUCocoaView implementation questions: How to deal with uninitialized AU, and restrict Host to single view.
- Subject: Re: 2 AUCocoaView implementation questions: How to deal with uninitialized AU, and restrict Host to single view.
- From: Paul Davis <email@hidden>
- Date: Mon, 19 Jul 2010 10:23:40 -0400
On Mon, Jul 19, 2010 at 10:16 AM, Robert Fehse <email@hidden> wrote:
> As i remember that the hard seperation of view and engine was not mandatory.
> An AU should not be regarded as broken if you ask me, just as an AU which is
> not able to live in different address spaces.
[ ... ]
> And pure parameter remoting is anyway possible via parameter communication.
That's really the whole point. GUI<->View communication is supposed to
be mediated by this API, not done directly via "special access".
And yes, the file chooser example you mentioned is hard.
_______________________________________________
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