Calling an effect the new way

[Simon Brown]

How can I call another effect with prameters the way that is compatible with paint.net 3.20?

[pyrochild]

AddNoiseEffect ane;
PropertyCollection aneProps;
PropertyBasedEffectConfigToken aneToken;

ane = new AddNoiseEffect();
aneProps = ane.CreatePropertyCollection();
aneToken = new PropertyBasedEffectConfigToken(aneProps);
aneToken.SetPropertyValue(AddNoiseEffect.PropertyNames.Intensity, 40);
aneToken.SetPropertyValue(AddNoiseEffect.PropertyNames.Saturation, 0);
aneToken.SetPropertyValue(AddNoiseEffect.PropertyNames.Coverage, 100); //This line is not necessary, really, because 100 is the default...
ane.SetRenderInfo(aneToken, dstArgs, srcArgs);
ane.OnRender(rois, startIndex, length);

Is the general gist of it. Obviously, you need to separate some of those lines into their appropriate methods...

[Simon Brown]

AddNoiseEffect ane;
PropertyCollection aneProps;
PropertyBasedEffectConfigToken aneToken;

ane = new AddNoiseEffect();
aneProps = ane.CreatePropertyCollection();
aneToken = new PropertyBasedEffectConfigToken(aneProps);
aneToken.SetPropertyValue(AddNoiseEffect.PropertyNames.Intensity, 40);
aneToken.SetPropertyValue(AddNoiseEffect.PropertyNames.Saturation, 0);
aneToken.SetPropertyValue(AddNoiseEffect.PropertyNames.Coverage, 100); //This line is not necessary, really, because 100 is the default...
ane.SetRenderInfo(aneToken, dstArgs, srcArgs);
ane.OnRender(rois, startIndex, length);

Is the general gist of it. Obviously, you need to separate some of those lines into their appropriate methods...

Thanks

But I do wander why they changed it.

[pyrochild]

The new property-based system is much faster to write new effects for. And more powerrrrful.

[Simon Brown]

The new property-based system is much faster to write new effects for. And more powerrrrful.

But it's a shame they didn't make it backwards compatible.

[Rick Brewster]

Why would I make it backward compatible? This new method is far better, and allows strong typing at compile time as well as runtime discoverability of an effect's inputs and constraints.

"Backwards compatible" just entails having a bunch of compatibility props with [Obsolete] on them so that old plugins can still work. There's only 1 effect that warranted that, which was BlurEffect.