Indicator for typedef in array on block diagram

[Trager]

The upper left corner indicator for type definitions on the block diagram is really useful, but that breaks down a little when you are using type definitions in an array. It's generally better to type define the element, not the array itself, but the array icon or terminal doesn't show anything to indicate that the contents are defined. How about putting the black upper left corner inside the bracket (for the indicator/control) or inside the frame of the icon? That would still show that it's an array, but would make it clear that the content of the array is linked to a typedef.

[AristosQueue (NI)]

We don't augment the front panel with this information at all for any typedef. That was a deliberate choice. You should file a separate idea exchange entry if you'd like to push for typedef marks on the front panel.

As for the terminal icon... how would you handle an array of a cluster where some elemetns are typedefs and some are not?

[Trager]

I'm still referring to the block diagram, not the front panel (and I agree that it's unnecessary information on the front panel). The comment about indicator/control was an imprecise statement that was meant to refer to terminal mode (i.e. icon/not-icon). To clarify: when the array terminal is in icon mode, it would be good for the upper left corner of the icon (but not the frame) to show the black typedef indicator; when the array terminal is not in icon mode, the suggestion is to color the upper left corner of the bracket. This would differentiate an array of typedefs from a typedef array (since the former would have the black corner internally, and the latter would have a black corner that reaches the bound of the icon or terminal).

Behavior for an array of a cluster where some elements are typedefs and some aren't should be the same as it is for a cluster of that type now -- no indicator. The suggestion I was making is specific to arrays that contain a typedef (which is a very common occurrence in my programming, for better or worse).

[AristosQueue (NI)]

> which is a very common occurrence in my programming, for better or worse

It is very common in all of our programming. 🙂

[Trager]

As an aside, there's part of me that thinks it would be a good idea to shade that corner indicator grey when you have a cluster (or other container, I suppose) that contains a mix of type defined elements and normal indicators/controls. But that would be a separate idea exchange entry, and I don't recall if there's already a use for a top-left grey corner.

[Manzolli]

I would give kudos to this idea with Trager refinement.

[Darren]

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