Change default localized name for objects

[smithd]

This one is pretty basic...and I'm guessing there is a valid reason for the way it is. Still, I wanted to throw it out there.

Right now, if you make an object, the localized name defaults to <object>.lvclass. Therefore, when you put it on the front panel, create a constant on the block diagram, etc. it will be stored with the label <object>.lvclass:

My request is that the default name be changed to the name of the class, rather than the name of the class.lvclass. The size of the icon makes it pretty clear that we're using an object, making the extension unnecessary. Either way, this is something that I change every time I make a new object and I'm curious if the other lvoop users feel the same way.

Thanks

[kegghead]

Agreed. One of the first things I do with any class (or more generally any library) is change the localized name to drop the superfluous extension.

[fabric]

Yup. It's not like we get "Numeric.ctl" when we drop a typedef. Keep the names clean!

[David_Staab]

You guessed right that there's a valid reason for adding the ".lvclass" extension. If the class is part of a project library, then the default class name is "Library 1.lvlib:Class 1.lvclass", and that's what gets displayed on control and indicator labels. It helps distinguish that type against "Library 2.lvlib:Class 1.lvclass", which may have the same icon.

I wouldn't mind seeing all extensions removed by default, but I understand how that could get confusing in very large applications. I certainly see the need for them in Actor Framework applications, where using project libraries is standard practice, e.g. "Integrator.lvlib:Integrator.lvclass:Create Integrator.vi" and "Integrator.lvlib:Integrate Data Msg.lvclass: Send Integrate Data.vi".

[fabric]

@Stobber:

I understand what you're saying but I don't see that as a reason to clutter up the panel with unnecessary text.

If I drop an object then what I usually want to see is the cleanest, most concise name possible,  even if the class happens to be a nested deep within a bunch of libraries. 99% of the time the icon + short name is more than enough. If I need a detailed genealogy of the object then the  context help tells me everything I need to know (and there's always right-click>Show Class Library). Why trust text that can be inadvertently changed?

IMO the AF does not help to justify the current behaviour, but rather highlights it as more of an annoyance...

[James_McN]

+50 if I could, just another timesuck when setting up a new class.

[another-roohcifer]

Bump a decade later, I guess?  This would be particularly nice for reducing the size of class property nodes.  Perhaps NI could add a LabVIEW Options flag to "Remove .lvclass extension from Localized Class Names" that is FALSE by default to preserve backwards compatibility if that's a concern for some folks who want to keep the extension?

[wiebe@CARYA]

---

@smithd wrote:

Either way, this is something that I change every time I make a new object and I'm curious if the other lvoop users feel the same way.

---

I simply ignore these labels.

MyClass.lvclass is silly. (I know it's a class, I know it's MyClass, this info is redundant). This is just as silly as labelling an array indicator "array indicator".

Sometimes in or out is added (I know it's an in or out, this info is redundant).

Then when you save a copy, the name isn't changed. So, you don't have redundant information, you have wrong information.

I've let it go... Didn't even bother to make a script to change the labels. I think I'd prefer no label.

But I'll kudo the idea, hoping someone will put some though into this.