Update component versions option

Oh goodness yes. +1

in the code a new blend node looks like this:

Quote
<Mode value="0"/> <Foreground red="1" green="1" blue="1" alpha="1"/> <Background red="0" green="0" blue="0" alpha="1"/> <Opacity value="0.5"/>

An old blend node looks like this

Quote
<Mode value="6"/> <Foreground red="1" green="1" blue="1" alpha="1"/> <Background red="0" green="0" blue="0" alpha="1"/> <Opacity value="1"/>

SO... for blend nodes it would be

search and replace '' with ''

There is a bit more to it but it should not be too hard

Good morning Everyone,

Yeah, That sounds GREAT! Lets hope the F/F Team agrees!

Rock on!

Have a GREAT day!

Ron

Technically, it will be possible in future versions -- some of the code we're doing for v2.0 can be adapted for this functionality. It will work even if the old and new components have different sets of inputs (some renamed, some added, some deleted). We don't plan this for v2.0 though -- too much to do, too little time.

I actually made a web app for this task.. but my work server is dead atm. I'll see if I can get it transferred to another server..

BUMP!

I'd like to challenge your concept of pixel perfect backward compatibility via the component versioning strategy.

1. Why would anyone want to use an outdated version of a component?
2. Your list of components to maintain and support will just grow and grow
3. There is no way to update a filter so it uses the latest components (other than the "manual way" which is really not a practically viable option)
4. A growing number of my old filters crash FF - it seems to relate to old obsolete components

I suggest you revise that strategy:

A. Only create a new version if it changes existing input options in a fundamentally incompatible way (did that ever happen outside beta period? Perhaps "Offse t" which you should really have chosen another name for as the new version did something else). I think most filter authors would rather be running on the newest version with a fractional difference from the old numeric output than running an old obsolete, perhaps buggy and likely slower version...

B. Provide a way to upgrade filter components in the editor, either by forcing the upgrade when filter is opened in the filter editor, or by a "Update Components" menu item. I would not mind the first option at all. If you are worried about the library and the overall impact this would have (i.e. push filters toward edge version), you could provide versioning of the library filters instead (this would have other advantages too).


Happy coding

I can only say this feature is on the Internal Feature Listâ„¢. Sorry, no endorsements or promises, as usual.

Ya if we could update all the old nodes in a filter automatically instead of manually it would super handy. Some of my filters have over a hundred nodes so it becomes very impractical to update each one manually