LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
Broken_Arrow

Sizable Element Gap in Arrays

Status: New

I think the Array Element Gap should be sizable. This would facilitate lining up FP arrays with other items on the FP, or simply as a mechanism to add more apparent delineation between elements.

The size should be set in the Properties box, not by dragging the element gap with the mouse - that would add too much "cursor noise".

A new Property Node for this feature would complete Idea.

 

GapSize.png

Richard






13 Comments
altenbach
Knight of NI

Go for it. I would especially welcome this for arrays of checkboxes, which are so small that they never align with anything....

 

(see for example this very old example from here).

 

Don't forget multidimensional arrays. The vertical and horizontal gap should probably be separate.

Henrik_Volkers
Trusted Enthusiast

Good idea.

To extend the idea: Four parameters are needed for the gaps to define the position of the element.

My workaround was an array of cluster, where I size the cluster. Involve two extra subvis for the UI, but is quite flexible. 

Greetings from Germany
Henrik

LV since v3.1

“ground” is a convenient fantasy

'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'


AristosQueue (NI)
NI Employee (retired)

1D arrays vertical need a Bottom margin.

1D arrays horizontal need a Right margin.

2D arrays need both a Bottom and a Right margin.

 

That controls the space between elements. I am assuming that if you set a Bottom margin of 20, then there would be 20 pixels between element 0 and 1, between 1 and 2, and so on. What about when you reach the last element displayed? Would there be 20 pixels between the bottom of the last element and the Array frame border? Or does "the space between the elements" need to be a separate setting from "the space between elements and the frame border"? The existing popup menu option for "Add Element Gap" adds a 1 pixel border all the way around.

Broken_Arrow
Active Participant

I would think having Element Gap: Height & Width would be enough. LabVIEW would disable the appropriate box in the case of a 1D array. 2D array gets both boxes.

Richard






altenbach
Knight of NI

> 1D arrays vertical need a Bottom margin.

 

I would not like the margin to be only on the bottom (or right), sometimes we want the element to be top-aligned, bottom-aligned, or centered.

 

For example if we have two vertical 1D arrays, one with small checkboxes and the other with big numerics (and with containers perfectly aligned top/bottom), we should be able to pad the checkbox array elements freely such that the respective checkbox aligns in the desired way with the corresponding numeric element with the same index.

 

Maybe we don't have to worry about edge effects, such as trying to omit the padding on the last element.

 

Another use case is if we have an array of modern numeric controls and modern numeric indicators side-by-side. In order to align, we need to either hide the increment/decrement for the controls or we need to add a gap for the indicators, because these increments are slightly over-sized, thus blowing the margins of the control array for typical font sizes.

Henrik_Volkers
Trusted Enthusiast

Why differ 1D and 2D?  Just provide properties for the size of one array element (might be there already)  and for the relative position of the control/indicator .... (back to four parameters 😉 )  or have the option to center/left-right/up-down. Or just like the cluster.... autosize or free.

 

 

Greetings from Germany
Henrik

LV since v3.1

“ground” is a convenient fantasy

'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'


altenbach
Knight of NI

Maybe pad margin in pixels for top, bottom, left, and right.

 

Ideally, it should act like an invisible decoration underlay of the correct size where we can nudge the array element around with the mouse or arrow keys.

CrystalTech
Member

Kudos!  However NI needs to do more than just a few patches to fix the FP.  It is time they take the 25 year old FP and do a MAJOR overhaul.  Notice to NI... Next year we will be in the second decade of the 21st century. 

 

The FP needs:

XY coordinates

Updated controls (e.g.. Up, down, left, right, arrow control), to name one of MANY.

Switch the FP to Vector Graphics

 

Labview is GREAT, but the FP is truly archaic.

rolfk
Knight of NI

@CrystalTech: Actually the entire FP in LabVIEW is already 2D vectorized (except in part maybe the "new" 3D controls). You just don't have much access to it in the customize mode.

 

And that custimize editor is the really archaic part of the LabVIEW UI. The rest is IMHO fairly ok.

Rolf Kalbermatter
My Blog
johnsold
Knight of NI

Not only is this a good idea, it should be expanded to make it very easy to align arrays of different types of elements such as numerics and booleans.  For controls in arrays the increment/decrement arrows should conform to the default grid as default so the alignment can fit the grid.

 

Lynn