LabVIEW Idea Exchange

[#1]

Actually for a multi choice selection by enum or numeric,  we have 3 possibilities:

1) Creat multi case structure  and connect and enum to it.

2) Creat an  array and select element by index

3) use few "bipolar" selectors

 

I think it will be better if a growable multiplexor exist and be polymorphic, with selection made by enum or numeric. Something like that:

Eric

[#2]

A better choice is to make the control itself an array of strings and always carry the data as an array, so "index arrray" is all we need. (and we already have that!).

[#3]

Yes , but my exempl is just a spcial case. If my signal sources are  few clusters elements or constant or dynamique sources , i can't convert it to an array control. An it's for this reason, i think than a multiplexor can be a good solution. 

[#4]

This is in a sense a generalization of the "select" function, in the same way that "compound arithmetic" generalizes the basic boolean operations.

[#5]

I would like the node to be more similar to the case structure.  Specifically, I would value an equivalent of selector case labels from the case structure in this node, because it would make code easier to review, especially when working with enums.  The picture below shows a case structure with three cases and equivalent design with the growable mux.

Possible extensions, all consistent with the case structure:

1. specification of multiple selector values for one choice (e.g., 1..5 to specify 1, 2, 3, 4, and 5).
2. an explicit default value
3. selections based on strings

[#6]

I got asked by a co-worker to clarify consistency between the proposed node and the case structure.  I hope the following picture conveys the point:

Here is a mock-up of a node with ranges:

[#7]

What about demultiplexer?