Martin,
Yes, it's intended to be public. We probably haven't updated the docs yet, though. That's something we tend to do too slowly.
I think what you've proposed is probably the easiest thing for your users at this point. And while it's not the ideal solution, it's not too bad.
Darrin On Apr 5, 2013, at 2:15 AM, Martin Baker < email@hidden> wrote: updateVersionAtCreation isn't actually documented, so is that supposed to be public?
I think we'll go with the easiest option of adding the new options on the end and just live with the ugliness of the ordering. Hopefully a future update will provide a way forward to a prettier solution.
Martin Baker ------------------------------------------------------ Digital Heaven Ltd is registered in England and Wales Company registration number: 3628396 Registered address: 55 Lynwood Drive, Worcester Park, Surrey KT4 7AE VAT registration number: GB 736 0989 03
On 4 Apr 2013, at 19:09, Darrin Cardani wrote: Ugh. OK, please file a bug on that. I guess that leaves only option 1, then. That's a bummer.
Darrin On Apr 3, 2013, at 5:45 AM, Martin Baker < email@hidden> wrote: This looked promising but has raised another issue. I'm seeing that calling updateVersionAtCreation: doesn't seem to affect the FCP project. So the next time that timeline is opened, it still reports the versionAtCreation = 1. This is even the case if you change value of another parameter.
Martin ------------------------------------------------------ Digital Heaven Ltd is registered in England and Wales Company registration number: 3628396 Registered address: 55 Lynwood Drive, Worcester Park, Surrey KT4 7AE VAT registration number: GB 736 0989 03
On 2 Apr 2013, at 18:48, Darrin Cardani wrote: 2) I'm not positive if this will work, but I think it will: During development, build a version of your plugin that reports itself as version 1, but contains 2 menus, both visible. Make a template with this version of your plug-in. Once the template is made, update the plug-in version to 2, but don't update the template. In the plug-in, in -addParameters, if it is still version 1 (which it always will be the first time the user applies it), update it to version 2 and show the new menu from now on.
|