Building the CarbonView as a separate component?
Building the CarbonView as a separate component?
- Subject: Building the CarbonView as a separate component?
- From: "B.J. Buchalter" <email@hidden>
- Date: Wed, 12 May 2010 02:18:18 -0400
Hi Folks,
The Carbon View is implemented as a Component, and in principal could
be built as a separate component bundle from the actual AU.
This would be a nice thing to be able to do when implementing 64-bit
AU's that have 32-bit Carbon UI's available, rather than having to
have a bunch of conditional compiles to keep the carbon UI code out of
the 64-bit component.
But it seems clunky to have to ship two components for one plugin. Is
there a way to embed the the view component inside the plugin's
component bundle in a way that the component manager (or the post 10.6
replacement) will find and auto-register them?
If not, can we register them from the AU's init code? Do they just
need to be registered before the host tries to open the component. If
we go down that route, how would we register it in the context of
"AudioComponent.h" on Mac OS X 10.6.
What's the recommended way to have a 32-bit Carbon UI when also
needing to support 64-bit?
Thanks!
B.J. Buchalter
Metric Halo
http://www.mhlabs.com
_______________________________________________
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