Re: View >> AU communication
Re: View >> AU communication
- Subject: Re: View >> AU communication
- From: "Sophia Poirier [dfx]" <email@hidden>
- Date: Sun, 30 Aug 2009 10:35:55 -0400
You use the GetProperty/SetProperty system. Define your own custom
properties and handle passing the actual data itself in buffers,
rather than references to data (as the previous example of passing
your effect unit's "this" pointer was incorrectly demonstrating). If
it's a property that can change and your view (or anything else) needs
to be aware of the changes, then you use PropertyChanged() from your
effect AU.
If you search the archives, you'll find more info (this has been
covered many times in detail on the list). Also I've made a
relatively simple open source AU that demonstrates some of this stuff
if you're interested in an example:
http://destroyfx.org/extras/#rmsbuddy
- Sophia
On Aug 28, 2009, at 9:36 AM, tahome izwah wrote:
> Bill, so what would be the recommended way of doing this?
NSNotifications?
>
> What if you update your class pointer in -setAU? I guess that should
> be safe since every change to the AU associated with the UI will go
> through this call?
>
> Thanks
> --th
>
> 2009/8/28 William Stewart <email@hidden>:
> > We don't recommend doing this.
> >
> > You should be able to keep the view and the model separate, and by
> > passing addressed between the two, you preclude the capability of
say
> > running in a situation like Logic Nodes
_______________________________________________
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