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.
When debugging, I often find I need to jump over a number of operations before jumping into an operation I'm interested in. It would be nice if we could mark VIs to not be entered (always skipped) when debugging, so that I can just spam the jump into key until I hit the one I want.
Please! Please, I'm begging you! Regardless of how many Kudos this gets, please make it an option to adjust the background of the block diagram! My eyeballs just cannot take it anymore. I dim my screen but there is just way too much white. I have to turn the lights off in the room. Can we please make it an option to dim the background of the block diagram to a light grey or something. Make it personable. It just hurts so much to stare at it these days. Especially with these new monitors and how vivd they are.
Most items that can be placed on the block diagram allow for access to their owning palette when right clicking. Many even have a second option that is related
this is very helpful - especially when the palette is three or four levels deep. The problem is that not every item has this option. I contend it should. Please allow access to the owning palette of each item as well as the parent palette.
Almost everything else from the Modern I/O palette has gotten a Silver version, but not IMAQdx session. Even the older, nearly retired IMAQ session has a Silver counterpart. It makes it difficult to present a cohesive UI. I guess the same would apply for whatever else is missing so please add anything else in the comments.
In many cases I need to use Empty String/Path array constants (Example: Initializing a shift register) but creating a normal String or Path is not readable on top whether anything prresent in the array constant. So it would make more sense to have an Empty Array and String constants available from the function palette. This can be created by pulling an Empty array and dragging the Empty String/Empty Path constants. In this case the Index and scroll bar selections from the view menu may be disabled.
The same can be extended to the other 2D array and further dimensions, which may be given polymorphic behaviour when wired to the respective dimension array.
Looking at all my body of work, I use tables exclusively as indicators. They are well suited to display formatted results in tabular form, but much less suited for user input, because they only allow strings. If we need to enter numbers, there is no input validation (as we have e.g. for numeric controls), so they are pretty useless for that.
It is thus a bit confusing that the tables in the palettes currently exist as controls. In fact, the modern, classic and system tables are even labeled "Table Control" (seems redundant!), while "Table" alone would have been sufficient (this has already been corrected for the silver controls ).
It would be much more appropriate if tables are indicators by default. We can always change them to controls in the rare case where this is needed.
Dear fellow labview programmers,
This idea is about writing scripts with 'niFgen Write Script.vi', e.g.:
Wait until scriptTrigger0
Wait until scriptTrigger0
My idea is to extend the scripting posibilities of 'niFgen Write Script.vi'
It seems that is only possible to program horizontal attributes of the waveforms (sequencing - i.e. time).
It seems that it is not possible to program vertical attributes of the waveforms (i.e. amplitude).
It would be helpful to be able to program the analog output-gain of the awg by the usage of such scripting.
Why hasn't this happened yet! I know this forum/idea already exists, which is why I'm confused it hasn't been implemented yet. It would appear the LabVIEW world wants this. Maybe it just needs to be brought up again and Kudo a ton. KUDOS!
Just click the link, I don't feel like reinventing the wheel when it comes to pictures and diagrams. However, I believe everyone agrees...definitely ignore the part about Inverting Controls/Indicators and Numeric Values.