Re: What problems do you run into when writing plug-ins?
Re: What problems do you run into when writing plug-ins?
- Subject: Re: What problems do you run into when writing plug-ins?
- From: Darrin Cardani <email@hidden>
- Date: Fri, 22 Oct 2010 15:37:29 -0700
That's a really good suggestion. Some quick advice:
Don't open a dialog during a render in Motion. Rendering happens on threads other than the UI thread, so it's not safe to display and run a dialog. I believe that currently Final Cut Pro renders on the UI thread, but there's no guarantee that won't change in the future.
I'll see if I can flesh out more details for the docs on this.
Thanks!
Darrin
On Oct 22, 2010, at 3:28 PM, Garrick Meeker wrote:
> Many people porting AE plugins could run into the issue of displaying a message to the user, i.e. figuring out what to do with the code that sets return_msg in the AE plugin. In places like parameter changed callbacks, it makes sense to just display a dialog. I'm still not sure what to do if something goes wrong in the render. Retuning NO just shows the generic "render failed" message, but opening a dialog seems like bad citizen behavior: stopping a potentially long render for user interaction, and possibly annoying the user if the dialog appears more than once. Or is that not an issue because an error will stop all rendering? What do other people do? I didn't think about this until our plugins got complex enough that "out of memory" was no longer the only possible error.
>
> While this sounds like a feature request, it'd be helpful to have some guidance in the docs for the current versions of the apps, even just "don't open a dialog during the render call."
>
> On Oct 18, 2010, at 4:16 PM, Darrin Cardani wrote:
>
>> I'm working on some documentation (gasp!), and am trying to think of problems that developers commonly run into when writing plug-ins. The things I've thought of so far are not properly handling non-square pixels, fields, and proxy resolution. So I'm thinking of writing some documentation on how to properly handle those and how to test your plug-ins to ensure that you're properly handling them.
>>
>> What other problems have vexed you in the past when writing your plug-ins? Anything you wish you had better documentation on?
>>
>> Thanks,
>> Darrin
>> --
>> Darrin Cardani
>> email@hidden
>
--
Darrin Cardani
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden