Hmmmm. So I still don't understand the intention of properties then. What exactly do you pass with the pointer if you shouldn't be passing pointers back and forth?
I would also vote for a more VNC like model for the UI, and less like the X-windows type architecture. If not, you are going to have to keep a ton of information on each side of the interface and just syncronize it with the parameter settings that get passed back and forth. That just seems wrong to me.
Case example: You have an FFT display in your UI. I would want to update my frequency graph in my AU code and have the UI reference that data. If you didn't pass pointers back and forther, how are you going to get that data into the UI efficiently? There has to be some kind of larger handoff of data above parameters.
How would you do this without passing a pointer?
Rick
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/coreaudio-api/email@hidden
This email sent to email@hidden
