Rename a GOOP object after it's created

[Alex Feldman]

Does anyone know how to rename the GOOP object (.llb) after it has been created? If the llb file is renamed, the "add function" functionality in GOOP object design window stops working.

[Jim_Kring]

Alex,

You have to change the name prefix of all the VIs, while preserving the links between the VIs. There is a tool at OpenG.org called Rename Folder of VIs that will allow you to do the renaming and relinking.

Give it a try...

-Jim

[Alex Feldman]

Thanks Jim. I'll give it a try. It'd be nice if this tool came built in with the GOOP wizard on the next release of the wizard, if there will be another release.

[Jim_Kring]

Check out Endevo's website. They do have such a tool.

[Alex Feldman]

Well, I tried using that utility and it worked. The only bad thing is that utility does not update the calls, so i had to manually update all the calls.

[Alex Feldman]

Would it be able to read the "class" that I created using the GOOP Toolkit 6i? Also, it's 600 dollars. That's very pricy. Would you say it's much better overall than the Toolkit from NI?

[Jim_Kring]

If you make sure that the callers are in memory before and while the "Rename Folder of VIs" tool is running, then they will "feal" the renaming -- linking them to the newly named VIs. You can then save the callers the new links will be preserved. Endevo's tool work's the same way, I'm sure.

[Jim_Kring]

Yes, the new GOOP framework will read your old GOOP 1.0 classes. This new framework support single inheritance, so it is much more powerful than the old GOOP. IMO, it is probably well worth the price, for many people.

[Alex Feldman]

Actually, I tried that before I wrote my comment and it still didn't work. I opened up the callers and they didn't "feel" anything. I'm not sure why, because I looked at the code of the renaming tool and the option to "Save as Copy" is false.

Also, on a slightly separate note, not only did I have to manually relink all the newly named vis, but renaming also made all the functions private. I had to manualy set each function to public so that it would be the way it was before renaming.

[Jim_Kring]

> I opened up the callers and they didn't "feel"
> anything. I'm not sure why, because I looked
> at the code of the renaming tool and the option
> to "Save as Copy" is false.

This violates the laws of the Universe 😉

> Also, on a slightly separate note, not only did I
> have to manually relink all the newly named vis,
> but renaming also made all the functions private.
> I had to manualy set each function to public so
> that it would be the way it was before renaming."

That is a good point, I will add a feature the preserves "Top-Level" VIs stored within LLB. That will fix the private/public problem.

-Jim