Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: QCPlugIn loadPlugInAtPath: vs. Library/Graphics/Quartz Composer Plug-Ins

I'm using [QCPlugIn loadPlugInAtPath:path] to load several custom patches ...
How can I get loadPlugInAtPath:path to prefer the plugins I explicitly load from my bundle and not grumble at the Console about duplicate names in the libraries?

I've found (with the unofficial API, so it might not be the case here) that if you call your loadPlugInAtPath method _before_ any QC code, your plugins get priority (they get registered first) -- This means before you create a composition or load it or anything. Also, I don't know if it's exported through the Official PlugIn API, but there may be a method to unload old versions so your new ones will register.

As for grumble-suppression, I don't think that's possible (maybe try @try/@catch blocks? They probably don't get high-enough up to catch though...)

--
[ christopher wright ]
email@hidden
http://softpixel.com/~cwright/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/email@hidden

This email sent to email@hidden
References: 
 >QCPlugIn loadPlugInAtPath: vs. Library/Graphics/Quartz Composer Plug-Ins (From: Marc Epard <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.