Re: Audio Unit Properties that are CFStringRef
Re: Audio Unit Properties that are CFStringRef
- Subject: Re: Audio Unit Properties that are CFStringRef
- From: Per Bull Holmen <email@hidden>
- Date: Mon, 05 Mar 2012 18:12:12 +0100
Den 16:53 5. mars 2012 skrev David Duncan <email@hidden> følgende:
> I'm not entirely certain if we're on the same page after reading this.
Clearly not.... :)
> The first step is to stop thinking about this as an issue of pointers. The issue is fundamentally about communication, not pointers. If you expect to communicate with the other side by accessing its address space, that will fail.
Well, you might think of it as an issue of communication, pointers,
whatever you like... It's fine by me...! :) I am asking a question
about IMPLEMENTATION. I have no problems understanding that I'm not
supposed to pass a pointer to the view, and expect to communicate
indirectly through it by changing the contents on the other side. I
thought I made that clear in my previous post. But for an audio unit
to communicate ANYTHING to the view, or vice versa, it has to pass the
data somehow, and clearly there are guidelines for how this can be
done. There is no way to get around implementation details, whether
you think of it as "pointers", "communication", whatever. The way I
initially read Apple's guidelines was that I can never COMMUNICATE
with the view by passing the data indirectly thorugh a pointer. But
Apple's own implementation does this for the CoreFoundation data
types, so I understand I read that wrongly. The question for the
previous post was whether you can COMMUNICATE with the view by passing
your own data types too through a pointer and not have to copy all the
contents over. So I think you have indirectly told me that yes, I can.
I wish someone could explain to me how I was supposed to infer that
from Apple's docs, or point me to some place where they state this
clearly. Because then I could comfortably follow this practice and be
assured that I'm following all the guidelines. Untill then, I guess I
will just follow the safest path: CoreFoundation types I pass the way
Apple does it, and my own types I will always pass by value. Even if
it means some extra programming efforts to serialize/deserialize.
Anyway, thanks for your help.
Per
_______________________________________________
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