LabVIEW Idea Exchange

Allow a multi-line Format String, with Format Into String treating new lines as though \n was in Format String.  Here's an example, where the output appears as three separate lines (and the Format String also looks like three separate lines, shown on the left, with the "correct" and only "legal" way to do this shown on the right).

Not realizing this would be a problem, I just created an 11-line "content" for an INI-like file, not expecting it would "reformat" itself as a line containing 198 characters ...  Oops.

Bob Schor 

Sometimes one has a 2D array of data that one wants to display in nice-looking rows and columns.  The "obvious" way to do this is as a 2D array, but the row and column "dividers" can interfere with the desired "unified" Spreadsheet look.  One solution is to use Array to Spreadsheet String, which creates a single String with a default "tab" separating columns and an "eol" separating rows, but aligning columns becomes very difficult, especially with a non-monospaced font.

I'd like to propose a "special" (I don't have a name for it -- maybe SpreadSheet String?) String Array Indicator that behaves like any other Array Indicator except that the "visual separators" between the rows and columns can be made "invisible", possibly by a right-click option.  Now the Front Panel Designer can lay out rows and columns, adjust widths and heights, then make the interior walls vanish so when the user "fills in the blanks", it appears as a nicely aligned series of row and column data.  If the data are strings, the user could even set Right, Center, or Left justification for the standard cell, again simplifying formattting.

Bob Schor

I find it difficult to pinpoint the local variables and property nodes in a program with many layers (cases, events...). It would be very helpful if LabVIEW had a list of all property nodes and local variables in one place, like a table, and with a click one could jump directly to the selected instance.

Double clicking a reentrant defined Vi opens always it clone instance. But nearby most of the time i have to edit the function and thus need the original VI open instead of the cloned instance.

It would be comfortable if you add an entry in the context menu like 'Open Prototype VI', so i don't need the navigate through the project explorer to the desired VI for editing.

When you have a probe to se the data in an array, you se all elements in one row (in the Value column) and just one element in the Probe Display area. If you have a large array, it is difficult to get a good overview.

My suggestion is that in the part of the probe window called Probe Display, you should be able to pull the bottom right corner and see several elements simultaneously.

An extra feature would be to also show the array size anywhere in the probe window.