Carbon vs Cocoa views in AU
Carbon vs Cocoa views in AU
- Subject: Carbon vs Cocoa views in AU
- From: Alessandro Saccoia <email@hidden>
- Date: Mon, 11 Feb 2013 12:31:50 +0100
Hi,
I have been using vstgui in the past, and I have just restarted porting my old framework to use the development tools on Mountain Lion. I have fixed the api changes and now everything seems to work.
I would like to setup my framework now and just forget about it for the foreseeable future, but I am confused about writing views using carbon vs cocoa apis.
For example in TN2207 that Apple daws are actually using a Cocoa window, and overlying a carbon frame is basically a hack.
I want to write plug-ins that work consistently from os x 10.6 on and on every daw, either if they use carbon or cocoa apis. Carbon is deprecated in 10.8, and for what I understand carbon views won't compile in 64 bit mode without some hacking, that sounds like not really futureproof and cause of headaches.
Also, in order to have the possibility of registering the carbon view entry point with the VIEW_COMPONENT_ENTRY method, I had to define CA_USE_AUDIO_PLUGIN_ONLY=0. It works, but I see that the macro is used in every file of the new Core Audio SDK and I don't find any comment about its usage.
So, question n.1: Is it possible to pack both views, and let the daw decide which one to pick up? Old daws will use the carbon view, and newer ones the cocoa one.
Question n.2: is the CA_USE_AUDIO_PLUGIN_ONLY=0 a good thing to do in order to continue to use temporarily the Carbon views using xcode 4.5 on os x 10.8? What are the limitations and its meaning?
Cheers
Alessandro
_______________________________________________
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