Provide error cluster's(MODERN) Label's initial letter in capital(Like other controls and indicators)

[amitwadje]

Hello,

How about capitalizing the initials of error cluster in modern control, In silver function it is already capital then why not in modern.

Every time, I finalized the front panel I always need to do capitalize these initials to have uniform label look.

Thank you.

[jcarmody]

Open <LabVIEW>\vi.lib\errclust.llb and edit the labels however you want.

[AristosQueue (NI)]

We will not be changing the default label. Labels are used for scripting code and there is too much scripting code, both within NI and among our users, that looks for these particular strings. As jcarmody noted, you can modify your own LabVIEW, but you may break some of the editor parts of LabVIEW that do scripting and are looking for that string. It is unlikely because most of us within NI have over the years modified functions that look for error clusters to find the type instead of the label, but I cannot guarantee that everything does that.

LabVIEW has never established a standard for capitalization of names of controls/indicators. You can see wide variance within LabVIEW core, between NI toolkits, and among user code. The error cluster is used in all of these contexts.

R&D has been investigating options that could improve this situation by making the editor smarter when a control is dropped onto a particular VI to follow the conventions established by that VI, but those are a long way off.

[tst]

AQ, I take it this applies to this (popular) idea as well - http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Get-rid-of-the-quot-no-error-quot-part-of-the-error-cl... ?

How does this scripting stance mesh with the fact that you already have different labels for the different styles? Are you talking specifically about code which creates silver controls and then looks for them? Code which looks for the different types of labels that might exist? Just scripting code in general, because "we know people deal with the error cluster, but we don't know the extent, so we'll take the safe road"?

[AristosQueue (NI)]

Yeah... we tried to implement that a little over a year ago. I thought about posting on that thread last night. We would like to do away with it, but we ran into difficulty.

> How does this scripting stance mesh with the fact that you already have different labels for the different styles?

It means that some scripting tools that were poorly written don't work with other styles. Relying on the label is a bad practice, but is unfortunately common enough that we are unwilling to rock the boat without a more systemic fix.

We are investigating that more systemic fix. Nothing to report at this time.

[AristosQueue (NI)]

Note that the other idea remains open because we are kind of using it to drive priority on a more systemic fix.

[Darren]

Any idea that has received less than 2 kudos within 2 years after posting will be automatically declined.