Usually there are a select few top-level libraries and VIs that I use to navigate through my project. It is most efficient for me if those items appear in the Recent Files/Projects list on the Getting Started Window and file menu. However, often enough they slip off this list and I have to navigate to them on disk.
I would love the ability to pin selected files to the top of the Recent Files List so they'd always be available!
defering Panel updates is both useful and a bit tedious. You have to
fetch the Panel reference, and while you are doing your presumably
time-consuming operation, the entire panel is stuck. I suggest that
Deferring Updates should be a property of an individual object and not
just the entire panel. Wrap your operation with a pair of property nodes to
start and stop deferring and you are all set.
It would be usefull to include information in the header of the image to indicate which version of LabVIEW was used to create the snippet. Users running older LabVIEW versions will not be able to embed the snippet onto their diagram.
To avoid localization issues, I suggest just using a simple numeric indicator: 2009, 2010, 2011 etc. Another option is to use a watermark.
If you have mulitple versions of LabVIEW installed, some of them show up in the "Open With" menu, but regardless of which item you select, the VI will always open in whichever version of LabVIEW was opened most recently.
Example: if I opened a legacy VI in LabVIEW 2009, closed that version of LabVIEW completely, and opened another VI using the "Open with" menu and selected LabVIEW 12..., LabVIEW 2009 is relaunched and is unable to open the VI because it should have launched in LabVIEW 2012.
The current workaround is to add all installed versions as options in the "Send to" menu, but this is not nearly as intuitive as using "Open with" would be.
So the request here is to have an option wherein the array indicators (or controls) can be linked with another array indicator (or control) and can be scrolled synchronously.
There could be a property node for that (or invoke node or may be some other way), which will accept the reference of another array and thats all.
In above example, Array 1 is linked with Array 2, so whenever the user will scroll (or change the index of Array 2, the same change will reflect in Array 1.
I saw this idea which I really liked and I realised that this would also be nice.....I do this type of 'insert subVI, delete broken wires' action all day.
I searched I think what I am proposing is a little similar to this idea but I think in the difference with the idea I'm putting forward is that labview will only automatically delete a section of the broken wire when the 'short circuit' is sending data around a VI as well as through it!
The second part of the idea - where the 'merge errors' vi can be configured to appear automatically when two 'sources' are wired to one sink would be useful when you are parallelising subVIs on the block diagram. I'd also suggest that if this option is configured and the source wires are deleted (so that only one source is linked to one sink) have the merge error vi disappear!!!
I'll be gutted if I've wasted my time on another duplicate.....I keep not finding other peoples great ideas
The LabVIEW forum has shown the constant need of a colorbox indicator that looks like an LED (round or square). Of course we can make our own, but maybe it would be easier if these would ship with LabVIEW.
Here are some example links. It comes up all the time! 😄
In some cases the list of context menu items extends beyond the vertical screen height (for example when creating a property for a control). The only way to scroll up or down this list using the mouse is by hovering over the small arrows at the top and bottom (and quickly moving the mouse away to stop scrolling).
This idea is to enable mouse wheel scrolling on context menus where the list of items is scrollable (the scroll arrows are visible) and the mouse pointer is hovering over the list. This allows for precise scrolling with much fewer mouse movements.
Currently on waveform graph, once a plot is named it cannot be deleted (it can be made blank, but it still shows in all pull downs). For instance I plot 3 graphs, each having 16 plots. I then refresh data and plot only on graph of 11 plots. My new plot names show in the top of the pull downs, but all the previous plot names still show up as well (see attached screen shots).
Please expose a method to remove plot names (property to give array of existing names and property to remove name or all names).
I remember when I first discovered the "Show Item Paths" option in the "Project" menu. This is such a useful view, but for some reason we are only seeing the tip of the iceberg!
I propose that the project window be enhanced to support other useful VI properties too:
Among other things, this would allow us to very easily identify VIs (or controls, or libraries, ... ) with non-standard properties. (Have you ever revisited an old project and tried to figure out which VIs are reentrant, or inlined?)
What properties should be available?
Ideally, this view would support ALL properties for ALL project items ( - at least those that have a compact text representation).
If that proves impractical for some good technical reason then I'd suggest we at least get access to the Execution properties.
It would be great if we could choose which columns to display from available item properties. These columns could then be toggled on/off (just like the existing "Paths" column):
An added bonus would be the ability to sort by any column:
My preferred implementation would be to allow the user to click on any column name to toggle between ascending and descending view. (This type of thing has been suggested a few times for multicolumn listboxes...)
On the other hand, I'd be happy enough if this worked the same as it currently does with "Paths", i.e. using the "Arrange By" option (>> Right-click on a parent item in the project and arrange the child items by Name, Type, Path, etc)
I think this would be a BIG step in the right direction towards leveraging the existing project interface to provide some REALLY useful information.
In LV 2011, an asynchronous Call By Reference feature was added to LV. This feature added two new nodes:
Start Asynchronous Call
Wait On Asynchronous Call
It would be nice if there was a way to use the LV event structure to wait for the results of an async call. For example:
I am not necessarily proposing this is the way to integrate the ACBR with the event structure, it is just one suggestion. Instead, I hope this idea can gage the amount of interest in some sort of event structure integration. If anyone has any better ideas or suggestions, please say so in the comment.
The LabVIEW Viewer would be a stand-alone application that allows for the viewing on VIs for someone who doesn't have a full-blown LabVIEW installation. It would function similar to how the development environment functions on a 'locked' VI.
I've used 'VI Documentation' in the past, but this viewer would allow for live navigation, context help, drilling-down into SubVIs, scrolling through case structures, etc.
