Color properties should default to colorbox data

[altenbach]

(As already hinted here, I think this deserves a seperate idea).

Property nodes have many items that accept color data (cursor color, plot color, bg color, etc). When right-clicking these and "create constant|control|indicator", we get a generic U32 type. Instead, we want a colorbox! Even more complex color structures, e.g. (colors[4] of a boolean) should have colorboxes as the innermost elements.

In all instances I have ever used these properties, I ended up replacing the U32 with colorboxes for code readability and simplicity.

Idea: when creating an input or output (constant, control, indicator) on any color property, we should get a colorbox (control, constant, indicator) instead of a plain U32 numeric. 

[wiebe@CARYA]

Darren,

I wouldn't mind he extra option. But a color box as default when creating a constant\control\indicator from a property would be nice too.

On a similar note it would be nice if some properties (flags) created constants formatted as hex. In general, instead of a "is color" flag for color properties, it might make more sense to add a default LabVIEW type to each property, instead of "designing" the LabVIEW type based on the base type. I bet there are more situations then colors and hex integers, although none come to mind right now.

[Darren]

Available in LabVIEW 2019 and later. Creating a control, indicator, or constant off any color terminal will create a color box instead of a U32 numeric.