Customising wrappers


#1

Is there an elegant way to extend the wrapper classes without editing them directly?

In particular I need to be more specific with the way my AAX plugins are created (pluginID, relatedTypes etc) and right now the only option is to hack into the juce_AAX_Wrapper code and keep copies in readiness for the next JUCE update.

Could there be some future mechanism for specifying the wrapper classes to be used, so that we could subclass?

justin


#2

I'm interested in this as well.
I have customized my AAX wrapper to add analyze and render functionality for Audio Suite. In the same way justinwebster describes.

Maybe there is an elegant solution and someone wouldn't mind to share?