Usually as Steven said, I would run older plugins in 2014 as is first.
If they seem to fail I would check what is going on.
The good workflow would be:
Always start with the SDK for the Soft version. So if I am writing a
plugin for 2011, I would use 2011 SDK. Then in 2012 and up I would load
this plugin without recompiling. It should work (backward compatibility
as promised). If it doesn't than I will check and recompile and report
bugs if any.
On 10/23/2013 2:17 PM, Mathias N wrote:
I made the move to the 2014SP2 SDK a while back hoping that some of
the problems I was encountering were bugs rather than me simply having
no idea what I was doing (Spoiler: it was the latter). Seeing as all
my plugins compiled against it also worked fine in 2011 I figured it
would be preferable to stick with it. Clearly I was mistaken.
If doing so does not provide any benefit I guess I have no reason to
use the newer SDK. Unless 2014SP2 does indeed begin breaking 2013 SDK
plugins, in which case I'll have to compile and release multiple flavors.
Bit of a shame though, seeing as everything else seems to be working
just fine using the 2014SP2 SDK.
On Wed, Oct 23, 2013 at 7:58 PM, Steven Caron <[email protected]
<mailto:[email protected]>> wrote:
ya, what advantage where you hoping to attain by using the newer SDK?
On Wed, Oct 23, 2013 at 10:54 AM, Mathias N <[email protected]
<mailto:[email protected]>> wrote:
Huh, so I guess I should stop using the 2014SP2 SDK for my
2011 plugins.
Thanks for clearing that up.
--
ALOK
GANDHI
/ directeur technique senior- senior technical director
[email protected] <mailto:[email protected]>
T:
*450 430-0010 x225
F:
*450 430-0009
www.modusfx.com <http://www.modusfx.com>
---------------------------------------------------------------------------------------------
MODUS
FX
120 Rue Turgeon,
Sainte-Therese (Quebec) CANADA J7E 3J1
Follow us on
Facebook <http://www.facebook.com/ModusFX>
&
Twitter <https://twitter.com/Modusfx>
**
