LabVIEW Idea Exchange

Post an idea

Currently when replacing an element/subarray using Replace Array Subset, you are only able to replace an element that is of lower dimensionality where one dimension is unity.

For example, given an array of size 100x3, it is only possible to replace one row at a time 1x3.

It would be helpful for me to avoid using a loop and be able to replace a subarray of dimension Nx3 where 100 > N > 1.

I may still have to use a loop to completely fill an array, but the loop could potentially run many less iterations.

This comes up for me because I read the FIFO buffer from a device and generate a chunk of data at once.

I then need to insert this data into a preallocated array (avoiding buildarray or similar due to the time critical nature of VI).

If I have a 1E5x3 array that I want to place into a 1E8x3 array, why waste time with a loop to do each row at a time (remembering that the loop is still much faster than buildarray)?

View All (1)

View All (3)

I don't really expect this to get implemented because there are things far more important out there. But, I'm going to post the idea anyways. When creating a new VI, the default icon puts a number in the lower right corner. I have never used this number. I immediately delete it, grab the background color then dump paint to fill in the layer that was removed. You wouldn't think something this little would be so annoying, but it drives me nuts. I am curious if anyone else has similar sentiments?

This is especially annoying for classes because despite designing a default icon for the class, I still have to modify the default on every VI to remove the number!

Every so often I want to pop up a VI at my mouse location when I click a control. The annoying part is the coordinate system from the event structure is relative to the pane. The position property node is relative to the front panel window. But I need coordinates relative to the screen. It is doable to get the appropriate coordinate system but it would be faster if you can just choose which origin you want (pane, front panel, screen).

I thought it could be an input on the property nodes like in the image below. The input can be an enum with the appropriate options.

I imported and pasted a graphic (my company logo) onto the front panel of my VI, but apparently there's no simple way to resize it while constraining the aspect ratio (e.g. resizing it proportionally).

I'm not asking to do it programmatically; I'm asking simply about resizing it to fit the rest of the front panel's design.

If I grab the handles and drag, it allows arbitrary resizing on both axes. If I hold down Shift it constrains it to resizing the vertical axis only. I've tried every combination of modifier keys, on both OS X and on Windows, and I can't seem to constrain the aspect ratio.

Most other applications that allow image resizing offer one or more of the following:

Holding down a modifier key (typically Shift) while dragging a corner resize handle forces proportional resizing. The current behavior in LV makes no sense. Holding down Shift forces a vertical resizing only, but this can be done by dragging the top/bottom handle (e.g. not a corner handle).
In the Set Width/Height dialog, have a checkbox to Preserve Aspect Ratio. If checked, any entry into height or width causes automatic calculation in width or height OnBlur.
In the Set Width/Height dialog, support entry by % or by pixels, with the same option to constrain.

This will help all of us produce more professional-looking applications.

We are using property nodes heavily in our APIs as they really help to maintain backwards compatibility in a high churn API; you can add, move, deprecate properties without having to obsolete VIs constantly and you can have consistent APIs for C and LabVIEW. It is really nice that you can select the first of N properties in a property node and then grow the property node by dragging down the bottom edge to get multiple adjacent properties. But, then you have to do a Create Constant for each property.

Idea: It will be really nice if the property node had a right click option to create constants/controls for all properties that do not already have something wired to them already.