When i finish my working day I often start to build a installer and execution. Because I don´t want my computer to run the whole night, I initiate a windows shutdown after for example one hour (shutdown -s -t 3600). In this case it would be nice if I could say "Save project and quit LabVIEW after building installer execution" or even "Save project and shut down computer after building installer and execution" so I would not get an error message when I start LV again.
As we all (should) know we can expand a block diagram by holding ctrl+l-mouse.
How do you solve it when the diagram is too big? Wouldn't it be great it ctrl+alt+l-mouse removed diagram real estate?
Just like with the expand, everything to the right and below gets moved up the size of the marked box, and in case of crossing structures (like a case structure), it should reduce their size the same.
LabVIEW has a boolean indicator displaying different colors at T/F condition and alllowing different boolean text entry
In addition, wish to have a ready made indicator with Boolean text PASS (Green Background) and FAIL (Red Background)
All the test applications shall have this PASS/FAIL result and this a quick drop will be useful!
Another common condition is TRUE/FALSE button. These can be added in Silver->Boolean>Buttons section
Typedefs are there but just an idea!
In the current version of DETT (2014) it does not appear possible to trace into VIs in vi.lib and intr.lib. This is unfortunate since we rely on using development packages deployed with VIPM - and these packages are often installed into the LabVIEW folders in one of this sub-folders. Debugging these VIs can be very useful during development and adding custom trace messaging in the application or to the VIPM packages can be cumbersome.
Ideally it should be possible, as an option, to include or exclude these folders.
Having a dockable palette/View of files that are open in labview.
Many developers would probably agree that having 30 VIs open creates lack of order in their desktop, and the way to swicth between them now is by clicking the taskbar icon and scrolling through till you find the one you want (in windows7 - grouped view at least, even worst without grouping with 30++ icons in your taskbar)
This could be solved by having a viewer, either standalone or even as part of the project explorer. buttons to either see BD or FP before or after the name of the file would also be prefered as having two entires; one for BD and one for FP creates dual entires and is only adding to the mess.
I am taking advantage of the recent FileVersionInfo to pull up the Version Number of the Executable at Run Time and display it for the User (who can then call me and say "Version 188.8.131.5234 crashed", and I can figure out which source this was). I take advantage of the Pre-Build Action to create the Version Number, taking the "Build" part from the Revision Number of the Project itself (since the Pre-Build Action gives me the path to the Project, this is fairly straight-forward).
However, in order to get the correct Build to appear in my Executable, I must build twice. The reason for this is that LabVIEW apparently reads the Version information before executing the Pre-Build Action, so my attempt to set it to the "correct" value is ignored until the subsequent Build.
Personally, I think it is illogical to have a "build Action" that silently takes place before the user-specified "Pre-Build Action", though there may well be a hidden "good reason" for this. I would like to request, therefore, that LabVIEW include a "Feature" that specifically allows the Pre-Build Action to include not only setting the Version Information (which it currently does) but allowing this updated Version Information to be used in the current Build. True, the work-around of "Build Twice, Use Once" works for me, but why should we need to jump through this particular (unpublished and unexpected) hoop?
(Unless it's already changed in newer LV's, i'm on 2011 right now)
When opening the connector pattern, the current isn't marked in any way. If i'm after some extra connectors or a symmetrical one (why do people choose 3-1-1-1?) it'd be nice to quickly see where to start looking. A simple bold outline would suffice, maybe in blue?
It is always great practice to make your code as readable and scalable as possible, along with good documentation. One of the things that get overlooked the most, without even realizing, is having coerced inputs to your functions or VI's. When you have finished developing a program, it goes through a great deal of review to validate all its functionalities. Coerced inputs can be one of those issues that can come back to haunt you down the road. I think having an icon on the toolbar and/or a shortcut keystroke to populate a list of all VI's containing coerced inputs would be a great help with identifying all the necessary functions that need to be examined.
I have the hadit of pressing Ctrl+Shift+S (Save All) which is annoying while working with Read only VIs. We always get a pop-up enabling us to save the VI in a different place or with a different name. As a result we get the browse window to Save the VI with a different name or in different path. This happens on clicking OK (which make sense) but also on click Window close button/ESC key.
My suggestion is to continue the save operation only on clicking OK and abort the operation when the user click the window close button/ESC key. This would be more meaningful and would make more sense to the way the Save operation is handled.
I am also fine with adding a Cancel option along with the OK button.
How the ideas exchange has existed for more than one project for anyone and not had a datagrid added already is beyond me. LabVIEW's table is horible, they need to add a proper grid, similar to flexgrid or other common web grids, that has grid sorting, grouping, sortable columns, drag n drop orders, totals, cell editing, cell binding, cell data types, binding complex objects (clusters), themes (CSS formatting perhaps).
LeCroy oscilloscopes do have a decicated area of the user interface for customization. The custom space can be used by an ocx-ActiveDSO PlugIn that is registred on the instrument.
This kind of ActiveX-Control can do far only be built by some VC and VB compilers.
It would be very nice to build now such a CustomDSO PlugIn for a LeCroy oscilloscope by LabVIEW.
Tameq Schweiz GmbH
+41 56 535 74 29
Another feature I wish to see in near future is a wire-anchor decoration or a mock function terminal that could help user prevent wire clutters / overlaps whenever the diagram cleanup is performed.
Kindly read the attached pdf for details. Please consider and many thanks for reading...
"Find Items with No Callers" could be a useful function on the project, but currently most items it reports are in Dependencies. Why is an item even under Dependencies if there is no caller? It seems if I call one function from an .lvlib the whole library is in dependencies, and all other functions have no callers. This floods my "Find Items with No Callers" window with useless entries.
Suggestion: add option to hide items from dependencies in the "Find Items with No Callers" window (or even hide them by default).
Hi, in large application where you have many parallel loops you must to be sure to put for all of them the correct out condition (even for "For" loop if they are long). i.e. in case of error or when user press "Stop" while the program is running.
I think could be useful if you can define somewhere a list of boolean variable and when you place a loop in the block diagram it is automatically connected to the list of boolean variables. For that particular loop you can select wich variable (one or more) defines the stop condition.
To select the variables you could use the same approach used for "Timed Loop".
The list of variables should be linked to the project and active only for that project.
One feature I wish to see in near future is a new structure that consolidate part of the code into an icon, just like creating a subVI, but does not necessitate the creation of a VI external file.
Kindly read the attached pdf for details. Please consider and many thanks for reading…
Below are some of the improvements I could think of reg VI Properties. Hope these are not posted elsewhere in the Idea Exchange (did a search, but got different results).
Any comments/takers... ?
I would find it extremely convenient to have a notification option (or options) to notify the user when the Build Status for a project is complete.
Sometimes when building executables or installers--or both--the compiler can take a while depending on the size of the project. During this time I don't just stare at the progress bar, but found that even if I left window open in plain view (off to the side or something), it is not obvious when the process is complete (the 'Done' button changes to Enabled and that's about it).
Options to notify the user could be any number of things:
I know "quick connect" is a new feature with Labview. Labview would choose to connect the newly added block to an adjacent receiving block automatically. But I am encountering some minor inconvenience when using it, expecially when there are multiple receiving blocks close to each other. This feature is actually making connecting procedure more complicated. As the chance of the newly added block to select the correct block to connect is small, corrections need to be made each time, which made connection even more time-consuming. I would recommend doing something similar to Simulink, where you select the ports you wish to connect while holding down some hotkey (say ctrl or shift) to quickly connect two adjacent blocks.