Property Nodes Should use Enums

[mfitzsimons]

All property nodes should use enums to make the code readable and not required to open help every time you need to set a properity.  I find myself creating typeDefs for my self so I don't have to look up what the properity does and to make my code easier to edit.  Example provided is to disable a control on the front panel.  This is in the LabVIEW style guide

[ASInc]

The part I've never understood, is in most other gui languages (VB, VC++, VC# and the like), theres no option to disable without greying out.  Why does LabVIEW need this option?  If we do need it, why not call it "Inactive" or something.  This is at the very least much shorter than "Disabled and Greyed Out".  As an added bonus, you don't have users trying to click on a Disabled/but not Greyed control, and wondering why it doesn't work.  Greying out is a visual representation of the fact that the control is disabled.  I can't think of any use for Disabling without greying.

[RavensFan]

Possibly for an indicator where you want it to appear normal (not greyed), but you don't want someone to have the ability do select the data in it and be able to copy it.

[MichaelAivaliotis]

Doesn't this already exist in LV2009? This request should be marked as declined I think.

[mfitzsimons]

Michael, They have gotten better with my original request but many prosperity nodes are still just numbers.  Dig around and you will see.  This was a general request for going through and updating as many as they reasonably can.

[EricR]

Revisiting all of the existing Property Nodes and re-implementing them in a way such that a type-specific enum could be created from it, is a very long tail development task that will not be a focus in LabVIEW to change.  LabVIEW NXG does not yet have an enum property types, it is something that is much more likely to be done in that environment.