Is there an easy way to rename object terminal labels to match class name?

[Michael Aivaliotis]

The problem I have is that when I rename the class, I end up with object controls and indicators that contain the label of the original class. Is there an easy way, outside of manually renaming, to do this? Maybe someone has a tool out there?

Not sure why LabVIEW doesn't do this for me. I can't be the only one with this problem.

[Grampa_of_Oliva_n_Eden]

The problem I have is that when I rename the class, I end up with object controls and indicators that contain the label of the original class. Is there an easy way, outside of manually renaming, to do this? Maybe someone has a tool out there?

Not sure why LabVIEW doesn't do this for me. I can't be the only one with this problem.

Ditto that.

Ben

[Stagg54]

scripting is your friend.

[Michael Aivaliotis]

scripting is your friend.

I figured. Maybe someone can help?

Edit: It seems like there is some hope by using the Search and Replace text feature that's built into LabVIEW. I think this will work for now.

[ShaunR]

I figured. Maybe someone can help?

Edit: It seems like there is some hope by using the Search and Replace text feature that's built into LabVIEW. I think this will work for now.

There's a few programmatic solutions on this thread

[Michael Aivaliotis]

There's a few programmatic solutions on this thread

Thanks. I'll definitely dig into that.

[Francois Normandin]

Jon's LVOOP Assistant renames Front Panel objects.

The LVOOP Assistant supports:

- Changing Class Icons themes with native LVOOP colors, custom colors or random colours

- Icon Layers due to the integration of the Icon Editor API

- Using a Sandbox to create Static and Dynamic methods from user templates

- Creating a Constructor method from a user template

- Creating Scoped Virtual Folders

- Renaming LVOOP FP Object Labels

- Cloning a method VI

[jgcode]

Jon's LVOOP Assistant renames Front Panel objects.

Thanks François!

That is correct - also the same feature is in the Rename LVOOP FP Object Labels Quick Drop plugin tool (this would be a faster way to go if you only require that feature).

Cheers

-JG

[vugie]

The problem I have is that when I rename the class, I end up with object controls and indicators that contain the label of the original class. Is there an easy way, outside of manually renaming, to do this? Maybe someone has a tool out there?

Not sure why LabVIEW doesn't do this for me. I can't be the only one with this problem.

Here is a plugin for Scripting Sandbox I made for similar purpose. However it is not so friendly to anyone but me... but it is an idea of Scripting Sandbox - isn't it?

Replace in-out controls.vi

[Daklu]

Edit: It seems like there is some hope by using the Search and Replace text feature that's built into LabVIEW. I think this will work for now.

I always use the Search and Replace; however, for reasons I haven't figured out sometimes a majority of the labels are marked as being unmodifiable using that feature.

[PaulL]

I use search and replace, too. It is simple but it would be nice not to have to do this (so maybe I should use of the tools already mentioned, although I think it would be great if NI would incorporate such a feature into the LabVIEW core). Anyway, right now I do a text-based search and limit the search scope to the VIs in the target class. This works well.

[Michael Aivaliotis]

Thanks everyone for the suggestions and comments. In the end, I used one of jgcode's tools. It's funny how, you don't realize the value of the LAVA code repository (or LAVA) until you run into a problem.

[Stagg54]

Edit: It seems like there is some hope by using the Search and Replace text feature that's built into LabVIEW. I think this will work for now.

That sounds like it might be easier than scripting.

In general I find scripting to be a pain to write. Once written it tends to be invaluable, although I find that most of the scripting I write tends to be very narrowly focused and address one specific use-case (maybe it's just me using poor programming practices and not being general enough.)

[jgcode]

That sounds like it might be easier than scripting.

In general I find scripting to be a pain to write. Once written it tends to be invaluable, although I find that most of the scripting I write tends to be very narrowly focused and address one specific use-case (maybe it's just me using poor programming practices and not being general enough.)

Scripting is great - but you don't have to create a package and publish it to get an (internal) benefit from it.

I suggest you check out Norm's Scripting Springboard - IMHO the fastest way to get a script going.

I also like his philosophy on Scripting + Assumptions = Powerful Code.

Sometimes, for a project, you just need something quick and dirty, if that does the job and saves you time doing in manually then it is fine that it is narrowly focused.

[jcarmody]

[...] I suggest you check out Norm's Scripting Springboard [...]

I'll add Vugie's Scripting Sandbox as another great place to look.