Re: Motion Template versioning
Re: Motion Template versioning
- Subject: Re: Motion Template versioning
- From: Peter Litwinowicz <email@hidden>
- Date: Thu, 20 Dec 2012 10:11:19 -0800
- Thread-topic: Motion Template versioning
Yes, I could do that.
I know that the version is in the Info.plist… Any easy way of extracting the value of the key CFBundleShortVersionString using an available Mac OS command line program without me having to write a script to do it? (I'm not using Apples package maker so I'll have to home-grow this)
Pete
Is there any way your installer could check the version of FCP/Motion installed on the system and install different templates, or tell the user at install time what the issue is?
Darrin On Dec 20, 2012, at 9:56 AM, Peter Litwinowicz < email@hidden> wrote: Darrin, et al.,
I have a problem with motion template versioning.
Our plugins need what you guys have supported with version 5.5 of the templates that you introduced with FCP 10.0.6 and corresponding version of Motion.
However, in pre-10.0.6 (when 5.5 was introduced) if I put the version at 5.5 in my motion template for my FxPlug, then FCP doesn't even attempt to load the plugin so I can at least put up a dialog box that says we don't run in 10.0 – 10.0.5. FCP just simply puts up a "can't deal" image of a broken film reel. However this looks like the plugin is broken (trust me, our users tell us these things), and not that our motion template is of a greater version than is supported.
Hoewever, if I put 5.2 for the version in the motion template so I can at least run the plugin enough to say "please upgrade", then I don't get the new features of the 5.5 motion template version for FCP 10.0.6 and up.
So I'm in a conundrum. Either way I have tech support issues.
Help?
Pete
|
_______________________________________________
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