site_archiver(a)lists.apple.com
Delivered-To: pro-apps-dev(a)lists.apple.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a…
This email sent to site_archiver(a)lists.apple.com
site_archiver(a)lists.apple.com
Delivered-To: pro-apps-dev(a)lists.apple.com
On Mar 11, 2009, at 6:42 AM, Steve Christensen wrote:
Darrin
--
Darrin Cardani
dcardani(a)apple.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a…
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?
This is a difference between Motion and FCP. There's nothing you've
missed, and I don't think there's any way around it. Although, maybe
if you were doing dynamic registration you could decide at that time
not to show it to Motion? That's just a random thought - I'm not
positive it would work.
This email sent to site_archiver(a)lists.apple.com
site_archiver(a)lists.apple.com
Delivered-To: pro-apps-dev(a)lists.apple.com
steve
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (Pro-apps-dev(a)lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a…
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?
This email sent to site_archiver(a)lists.apple.com