This would be such a substantial break in compatibility I cannot imagine us ever making this change without an accompanying complete UI overhaul. I've seen those enum strings in configuration files for setting up user interfaces. If we broke compatibility there, I know many large systems that would break.
I admit it would be nicer if the size were smaller, but I can't see it happening. If you do not like the size of the enum, you can create an inlined subVI of the constant and use that.
Minor correction: I cannot see it happening through changing the string. Some other feature to change how the enum is displayed (perhaps let it be resized manually?) might be feasible.
I admit it would be nicer if the size were smaller, but I can't see it happening. If you do not like the size of the enum, you can create an inlined subVI of the constant and use that.
In previous LV versions, this property was set by the 0, 1 and 2 numeric constants. Small but not self documenting.
AQ just said that the string will not be changed. This is because casting an enum to string with the operator %s will output the visible string for that value of an enum. The reverse also works when reading so if you change the string visible, any code which loads and saves a setting as string to file (which is cool, I do it myself all the time) will break.