How about a feature in DETT that allows users to generate a plot of the memory allocations over time? This would be useful to diagnose memory leaks that occur over a period of days or even weeks? Currently it is difficult to draw conclusions from the details column unless the data is copied into a program that can generate plots.
In Write to Spreadsheet File.vi when we try to create control for the Delimiter, the control gets overlayed over the VI itself. The same is not happening in the case of Read from Spreadsheet.vi file, so this need attention. Please ignore if it is already suggested.
Delete From Array Function - Output should be renamed as "Edited Array" instead of the current name "array w/ subset deleted", as the 'w/' often confuses new users (and users like me as well sometimes), whether it means 'array with subset deleted' or 'array without subset deleted'.
Instead of this, the name "edited array" as mentioned in the Help itself would suffice, and is much more clear.
Help - "Returns the edited array in array w/ subset deleted and the deleted element or subarray in deleted portion."
Cleanup diagram is not much used (Personally I allign the diagram myself manually). But if we have few improvements with the tool we can use it atleast in sub vis more often.
At present the Cleanup diagram tool introduces unncessary wire bends eventhough it can be avoided. So it would be great if this is taken care properly and unncessary wire bends are removed.
Manually alligned without wire bends
Wire bends are introduced once the Cleanup diagram is done.
Recently, I discovered an annoying "feature" of LabVIEW: if you limit the data entry of a floating point numeric to a maximum value with coercion enabled, entering NaN to that numeric will be coerced to the maximum that you set in the data entry dialog.
I already reported that as an unexpected behaviour, but after some more thinking, I dare to go even further and propse:
allow the blocking of NaN in floating point numeric data entry
The logic needed should not be much more than a finger exercise, as string controls already allay to discard CR/LF with the "limit to single line" property.
There are numerous ideas floating around about where the color box constant and control should be located in the palettes. How about if there wasn't a distinction between a color box and its numeric representation? Like the "View As Icon" option on terminals and clusters, I suggest a "View As Color Box" on numeric constants and controls/indicators:
I'm undecided on if this options should be available for all numeric data types, integers only, or U32 only, and what should happen to the Representation options when the numeric is a color box. I see at least these options (ordered after my preference - I prefer 1) the most):
1) The "View As Color Box" option is available for all numeric data types, but when selected the data type changes into U32. If you change Representation to anything else but U32, the "View As Color Box" option is automatically deselected.
2) The "View As Color Box" option is available only when the numeric is U32.
3) The "View As Color Box" option is available for all numeric data types, and coercion happens between the selected "color value" (U32) and the true Representation of the numeric.
In the same way that mouse clicks, key presses etc can be filtered or modified before being accepted, having a Value Change? event option would allow tighter control over input data than possible using the Data Entry tab, and without needing to wire to a Value property node or local variable as AQ suggests here.
While this idea in itself probably doesn't make much difference, it would be very useful if such an event could be "bound" to a .ctl (a sort-of mini-XControl) in an enhanced version of what the Data Entry tab currently does.
During implementation of code, the algorithm and its implementation has to be tested and debugged in most cases many times. For debugging, probes are a very useful tool. But probes can only be created on existing wires.
If, for any reason, the developer wants to probe values which are not on a wire already (e.g. iterator of a loop), he has to create an indicator (or tunnel) in order to have a wire. Once the debugging is done, the terminal/tunnel and the wire should be deleted.
I find it would be much easier, if i could right-click the data output and select Create >> Debug Terminal. This terminal is part of the code, but once i close the probe, the items created by this option (terminal and wire with probe on it) are removed automatically.
PS: I know that there was a suggestion specifically for the iterator of a loop. I understand the reason why it was declined, but i find that using VI Scripting, the above mentioned functionality could be provided. As i WANT to have the information of that wire during debugging, i require that terminal/wire in any case. Using some automated tool would ease the debugging process with the hope to decrease time required to identify the software anomaly.
Add a description of inputs and outputs relative the the chosen polymorphic instance of the VI.
Current documentation is Axis 1, Axis 2, Axis 3 and there is no description e.g. how those names correlate to the polar coordinates Phi, Theta and length!
I had to figure it out by trying - please just add tose few lines to the Labview help!
I like to collapse long string and path constants to consolidate diagrams. Showing the string or path value in the tip strip is useful but tedious to update.
I suggest an appearance property that would automatically display the current value in a tip strip for string and path constants.
This property would be most useful if the Block Diagram Options page was also modified to allow a global setting.
One of the things that sometimes bugs me when using LabVIEW is that if you have a front panel or block diagram in a small window, many of the menu options and toolbar options are inaccessible without having to resize the window first. You have to have a minimum window size to be able to access all of the toolbar functions.
Still don't get it?
This is how big I want my SubVI window to be:
Problems with the above:
To be able to access the entire toolbar, the windows has to be at least one of the following wide:
Why is this a problem?
Please make it so that the menu and toolbar are accessible regardless of window size. One solution would be to have a button that allows you to 'scroll' the toolbar or have a pop-up dialogue that shows the missing toolbar buttons as per the image below.
MS Paint skills (icon lifted from Chrome's bookmarks bar):
As an aside, MS Word manages it fairly well (even though it isn't that readable), and it has a LOT of toolbar buttons:
Please consider my idea (or Kudos it) for future versions of LabVIEW - it will improve usability of the IDE.
Sometimes you might have a cluster constant, indicator or control on the block diagram or front panel without the labels shown. When you have a large cluster it's not immediately obvious which element you're editing/changing.
When you hover over a SubVI, the connector flashes on the Context Help window and eventually a tooltip appears on the block diagram under the mouse cursor as shown below:
I propose that, just like when you hover over an input/output of a SubVI it does the same to show the element name on clusters on the front panel / block diagram, as follows:
I know it's not the most exciting of suggestions but I think it would be good for usability.
This idea is somewhat similar to Shrink-Wrap-Structures but for comments and strings
The idea is to resize a comment or string to the text by double clicking one of the resize indicators around the box.
This would happen without changing the number of lines or words on each line.
The process would be resize the horizontal direction of the box until the line layout looks nice (and fits!) then double click the corner to remove the unwanted space.
There could be different resize processes depending on the corner or edge you click eg. double clicking bottom middle resizes to only remove vertical space, top left would resize and shift the text down and right so the bottom right corner remains anchored.
There are some other ideas about resizing multi line comment boxes but none were quite as straight forward as this so I made a new post for it.
This mechanism is similar to other programs for resizing boxes so it seems like a sensible thing to implement.
I'm using 2012 version, so I don't know if it's the same for 2013 and 2014 versions.
I don't use color boxes very often but when I do I always have the same problem when looking for them in the tools palette.
When in the front panel the Color Box control is situated in the Numeric folder
But when in the diagram the Color box constant is a little more hidden...
I know there is the "Search" option, which works very well. Also I can choose the color box control in the Front Panel and change it to a constant, but I worked for a lot of years with version 6.0 to 7.1 and it was very intuitive to find the constant where it was, i.e. here:
So why don't leave the color box constant with the other numeric constants?
By the way, thank you for reading, I always wanted to comment this
See the snapshot for a visual clue.
Most often we need to browse to the palette of the base data type (in this case Bool, and not only the datatype of the wire (Array)), to search/insert/replace a function while coding. Here I wanted to bring the And Array Elements function from the Boolean palette by clicking the Equal To function's output, but it gives me an option only to the Comparison & Array palettes. I'd prefer the Boolean palette to be shown up in the options.
This suggestion should be considered in a very generic & more inclusive manner for all the use cases.
P.S.:- I did not see any option for BD category, so labeling under UI & Usability (since the BD is an User Interface for me as an App Developer using LabVIEW. )
When dragging a control / indicator label or caption, if you move within a certain distance from the owning terminal the label will snap to one of a set of given positions (top-left, top-middle etc). Outside this distance (or if the user presses the spacebar to toggle this behaviour), the label can be freely positioned.
The selector terminal for a polymorphic VI should display the same behaviour with regard to the owning VI icon. A polymorphic selector is currently always free-floating.
PS : Many thanks to Intaris and TiTou for their help to formulate this idea.