|
Given that there's currently no workaround, my plugin just checks if it's running on Motion. In that case, no custom parameters are created and the renderOutput:... method just displays a splash screen telling the user that the plugin is only usable on FCP. Not my first choice of how to do it but at least you don't just see an empty frame when the effect is selected in the list.
steve
On Mar 11, 2009, at 10:41 AM, Micah Sharp wrote: No, afraid I have not filed a bug. Sorry, I'll try to get on that asap.
Thanks,
Micah
On Wed, Mar 11, 2009 at 9:25 AM, Paul Schneider <email@hidden> wrote:
Hi Micah,
Yeah, we have the same problem with one of our plug-ins and just got dinged in a online review for it. Nothing you can do to not show up in Motion (that I know of) I'm afraid.
Did you file a bug? :)
It sounds like our documentation isn't matching reality here, and you're unable to do something you'd like to do. It's true, Motion won't create an instance of your plugin class until it's actually added to the project; they just scan the plists to populate the Filters library. Which is generally a good thing, but it does mean that you can't do a runtime check and refuse to be loaded.
- Paul
On Mar 11, 2009, at 12:12 PM, Micah Sharp wrote: Yeah, we have the same problem with one of our plug-ins and just got dinged in a online review for it. Nothing you can do to not show up in Motion (that I know of) I'm afraid. Micah
On Wed, Mar 11, 2009 at 5:42 AM, Steve Christensen <email@hidden> wrote: I'm working on a plugin that will only work with FCP because it's using FCP's AppleEvents and XML. I have a test in -initWithAPIManager: for FCP which causes it to just return nil if it's opened in FCE or Motion.
I just launched Motion via the debugger and found, to my surprise, that -initWithAPIManager: is not being called until the plugin is selected in the Library list. That is different behavior from FCP and FCE, which call -initWithAPIManager: as the plugins are being loaded, so my plugin is correctly not available in FCE.
Is this a Motion issue or have I missed some setup piece described in the FxPlug spec?
steve
|