Re: How to keep view and audio unit aware of each other
Re: How to keep view and audio unit aware of each other
- Subject: Re: How to keep view and audio unit aware of each other
- From: Brian Willoughby <email@hidden>
- Date: Fri, 30 Jan 2009 23:38:52 -0800
The word is that you should write your audio code and view(s) as
completely independent. You have to do everything with listeners and
properties. You cannot even be certain that there aren't multiple
views open at the same time.
On Jan 30, 2009, at 20:19, Brent Lehman wrote:
Sorry if this question is answered all the time. I searched for it
but couldn't find it.
What is the best way for an audio unit and its associated view to be
notified of each other's constructions and destructions? In some
cases it looks like GarageBand kills and reconstructs the unit but
keeps the view, and it's causing problems in the code base I'm
maintaining. Maybe I could figure something out with listeners and
properties, but if there's a more elegant way I'd rather use it.
If there's a way for the unit to query whether or not an associated
view exists, that would work too.
_______________________________________________
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