Could you not do some sort of detection magic, to see if a class name or class exists prior to manually either calling that functions, or using NSBundle to load the plugins ?
On Dec 1, 2011, at 5:33 PM, Christopher Wright wrote: >> excellent! > > Note that this _won't_ get rid of the console warnings about classes being > implemented in more than one binary, and it won't resolve the undefined'ness > of which one actually gets used if the user happens to have the plugin you've > bundled in already installed elsewhere. > > It seems reasonable to file a request to have better control over how QC > loads plugins. > >> On Dec 1, 2011, at 1:56 PM, vade wrote: >> >>> You can manually load QC plugins from any location, including your >>> Applications content/resources or whatever location >>> + (BOOL) loadPlugInAtPath:(NSString*)path > > -- > Christopher Wright > christopher_wri...@apple.com > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Quartzcomposer-dev mailing list (Quartzcomposer-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/quartzcomposer-dev/doktorp%40mac.com > > This email sent to dokt...@mac.com
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list (Quartzcomposer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
