Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Search instead for
Did you mean:
Do you have an idea for LabVIEW NXG?
Use the in-product feedback feature in LabVIEW NXG to tell us what we’re doing well and what we can improve. NI R&D monitors feedback submissions and evaluates them for upcoming LabVIEW NXG releases. Tell us what you think!
When I have large projects with lots of classes, Labview's edit time environment slows down to a painful crawl. Almost every meaningful action triggers a recompile that gives me a busy cursor for 3-10 seconds. My productivity falls off a cliff and I avoid making important changes in favor of the cheap hack. (The dev environment has high viscosity.)
I often wish there were a way to turn off the compiler while I make a set of changes. I'm not interested in the errors at every single intermediate state of the code while I'm making the changes. I *know* the code will be broken after I delete some nodes or wires. Let me turn the compiler off, make my changes, and then turn it back on for error checking.
I'm sure there are lots of different solutions to address this problem. My preference would be to make compiling faster so it is unnoticable. I doubt NI will ship me a new computer with the next release. My second choice would be to stop loading all of the class' member vis when any single vi is loaded. I vaguely remember a discussion about that some time ago and it wasn't practical to do that. That leaves me my third choice--more control over what automatically compiles when I make edits.
It could be something as simple as Ctrl-Shift clicking the run arrow to toggle auto-compiling at the vi level. Or it could be a right click option in the project window that controls auto-compiling for an entire library or virtual folder. Either would be okay; both would be nice.
(For that matter, it would probably be a lot cheaper if NI just shipped me a new computer...)
When creating accessors, I find that 99% of the time my read and write accessors have the exact same documentation. I'm literally copying and pasting into the "VI Description" for each pair of accessor VIs.
Let's say I have a data member called timeout_ms.
Whether it's the read accessor or the write accessor, the documentation is, "VISA timeout in milliseconds for serial transactions." Entering it twice, while routine, has become mildly annoying.
Why not make the accessor documentation a property of the "Property Definition Folder" that houses each pair of accessors? That way, most of the time the developer would only have to enter documentation once.
How might this work?
The developer would open the context menu for the accessor's property definition folder.
From the context menu, the developer would select "description", "documentation", or some such item.
The developer would then enter a description of the data member in the resulting window.
After clicking OK, the dialog would then apply that documentation to the VI description for both accessors.
The dialog might look something like this:
I'm a real stickler for VI documentation, and as much of a hassle as it can be, I document all of my accessors. Any time we can reduce the number of mundane steps to accomplish basic things, I'm very grateful.
The Attached code calculates the square root free Cholesky factorization (LDL'), it is very useful to decompose matrices and in my specific case, to make observability analysis within electrical distribution networks. I'm publishing it because LV counts with other kind of decompositions like the LU decomposition, very useful but for my case, the values delivered by LDL' are more accurate and easier to calculate.
I would like to see an Option for Child Window. This option
will useful to keep open FP in Parent FP even when it is moved around,
I understand LabVIEW dose not support MDI, but simple Child
Window option will be helpful. Currently, I am using Windows API to do this,
but native supported function/ option can be big help (won’t have to use VI
server, Dynamic path builder to check application type vi, exe, llb, and others
useful things that needs be done..).
If a control becomes disabled or disabled an creyed out, there is no possibility to copy text out of the control. It would be nice to to add a 4rd value "read only", so that the control has the behaviour of an indicator. So the User can copy parts of a String or number ot of the element.
As far as I can locate, this hasn't been posted on Idea Exchange yet.
What I'd like to be able to do is change the default colors and visibility of various components of block diagram items. For example, I might want to color the background and sub label of my timed looped structures so that they improve the appearance of my code, like NI has done in the Bioreactor example code with a free label and custom colors.
Rather than setting these colors/font sizes/label visibilities for each structure I place, I'd like to be able to set them only once. Currently, the sub labels' default visibility CAN be set in tools»options, but not the coloring.
It is sometimes verry frustrating to replace elements on the blockdiagram or the frontpanel. I have to navigate through many menues. It would be better to have the recenltly used elements in a list, so that i can use them verry fast.
So here my suggetion: extend the context menue on replace and insert by the point "last used ..."
When developing a utility to traverse any control using VI Server and save its contents to a file (similar to the OpenG utility using Variant) it is quite challenging to find out the size of the array's data.
There are various workarounds, but all of these are relatively tedious and over-complicated.
Why don't we have a "array data size" read only value on the property node of an array?
Would it be good, on the Graph Properties page, Plot tag, one can set up the Y-scale to left or right? Good idea? Give this idea a Kudos!
At present, one can achieve a two Y plot by: right click the Y axis, Duplicate Scale, Swap Side, and often confused with which plot is associated with which data set. A cleaver package like LabVIEW should not need to do this. Just look at what Mathcad does.
The current strip charts display data a fixed intervals. If I want to plot data that is collected at inconsistent intervals I have to use a XY chart and record the paired data. How about creating a strip chart that displays the data against the time it was added to the plot? The program provides the Y value and the x value is just the time the data was plotted. The plot could have a time constant for the entire window much like the scroll rate used in actual paper chart recorders (e.g. 1 cm/minute). In other words, one could configure the chart to have a span of 1 hour. After an hour, data would get "pushed" off the end etc..
The current while loop executes and then checks the termination condition. This is known as a do while loop. First you "do" then you "check". Can you add a "while do" loop. This would first check the termination condition and then either execute or not. I know I can put a do while loop in a case structure and build the same functionality as a while do loop, but it would be much easier if I could just configure the while loop to check first then execute or execute and then check.
I suggest thatLabVIEWCall Library FunctionNodeaddedautomatically identifyinput and outputportfunctions.And automaticallynamed.Thisfunctioncan savethe queryinput and outputportsof thetime,speed up the developmentprocess.Orthe sameas this Express function: