What is your tip with quick replacing V4 to V5 components?
There is no compatibility between these two versions and, so far, it requires tracing old components and replacing with new ones.
It is quite difficult and time-consuming with >4000 elements script as old name aren’t displayed.
Yeah, quite an unfortunate pain. I can look into whipping up a utility to do the swapping, but it will be a few weeks before I can get to that. If anyone has any bright ideas for making this more painless, would certainly also welcome them.
In the short term, they should have different icons, even if the old names are displayed (that is, if you’ve installed the Legacy version), which might help at least a little to distinguish. Then you can use F3 to search for the components and be able to tell.
Sorry for the difficulty, but the good news is you only have to do it once?
I thought there is some trick to it, but OK.
So far, I am building solution using Fennec.
It creates a list of all components used in a definition and displays it.
I will be matching all V4 names, finding their location and replacing one-by-one.
Wish me luck
1 Like
Piotr, as a regular Elefront user i’m going to wait until they get out of Beta before sharing scripts with it. It’s my understanding 5.0 is still a work in progress.
Thanks. I will listen to your advise.
Elefront plays important role in most of my scripts. I wanted to learn what I can expect from an update but, as far as I can see, they can’t run hand by hand. Am I right?
No, not at all, it’s a complete re-write. I love what i’m seeing but its too early to switch. Its good to test & give feedback so things work for you as expected in the new version. The upgrade replacement utility Keyan mentions will make the transition easier too, we currently have something similar in RiR that replaces and puts a gh group around the updated component, maintaining inputs and output when possible.
1 Like