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 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 building an installer to let an application run on another computer one should select all the installers of products used in his porgram. This can be really tricky, especially to new users, that don't know if a VI was included in package A or B or if it's already included in the standrad runtime.
Therefore it should be possible to hit a button, that parses through the Application and determines which packages are used.
I though of writing something like this myself, but I can't be bothered
You'd just have to parse the Project, check all the VI names and relate it to a table that contains information, about where a VI comes from.
When doing UI work, it can be quite frustrating rewiring hidden controls to the connector pane. You have to go to the block diagram -> Show Control -> go to front panel and wire it up then hide your control again.
My suggestion is that when you select the Wiring Tool on the front panel or click on the connector pane (to wire up a terminal) all the hidden controls would become partially visible and become connectable to the connector pane.
I have a project which compiles to 2 different executable for different hardware targets. I have created 2 Build Specifications which specify different locations for the build output. However, between compiling each one, I must go to the target options, and change a Conditional Disable Symbol definition so that the other .exe is generated. If the Build Specifications definition had a tab to specify the value of Conditional Disable Symbols, and which would take precedence over definitions in the project or the target options, then I could build my 2 executables without changing the target properties.
Direct to PDF reporting is an extremely important feature to provide customers. It cannot be relied upon that the customer has MS Word or the like installed.
There are a couple of LV PDF toolkits supplied by developers. However, the problems with these include that they are (a) not updated or well-supported (b) buggy (c) have out-dated dependencies such as .Net 2.0 (d) restrictive licencing for deployment.
Good reporting tools are essential and NI should develop and support a direct to PDF toolkit.
I often find when programming with LabVIEW that I don't have room on my block diagram for free label documentation. I find it hard enough trying to keep clean and tidy code and even harder document it well. Free labels take up lots of room and I end up not writing good documentation because I don't have room for it.
My solution to this problem is a Documentation Node where you can write comments in a free label, minimize it and use context help to read it in the future.
When developing a Complex LabVIEW Applications, we may need to create N Number of Folders as a part of Configuration information.
This requires the developer to make a check "Check if File or Folder Exists"
Instead of that Create Folder Function can have a Boolean "Optional Input" to create the Folder only if not found in the specified Location and Eliminating the Error when trying to create same folder again.
In the string constant you are able to make a scrollbar visible but this is still inconvenient when only see 2 lines of your whole string when you have a string constant of 50 lines or so... and you 9 out 10 times you don't want to create a bigger field because it messes with your diagram.
Therefore a small popup with a only a large textfield would grately simplify things.
I work with customers who use multiple versions of LabVIEW. Being able to run two (or more) different versions of LabVIEW concurrently is a boon to my development and productivity. However, identifying which version I am looking at or have open can be difficult.
Can YOU tell which versions I have on the taskbar?
To remedy this, I suggest a version badge be added to the taskbar icon for LabVIEW. This will facilitate quick identification of LabVIEW versions.
LabView uses the "primary" MAC address to identify a machine. If the MAC address changes, LabView assumes the software no longer has a valid activation and displays the following:
Like many developers, I have to use a VPN to connect to a corporate network. My VPN client creates a pseudo-interface with a (random?) MAC address each time I connect. LabView inspects this MAC address and decides I've installed LabView on a new machine, forcing me to go through the activation process again. I have to activate LabView about every 10 days. I have contacted support about this, and they have given me various work-arounds such as non-expiring activation codes (which required manually entering 10 activation codes, one per product, and only work until the next LabView service pack), or tying activation to the Disk Volume ID, which frankly I did not bother trying since the "eligibility on a case by case basis" did not mesh with the reality that every point release of LabView requires re-activation.
Now, I don't want to make too much of this. I've never had the activation fail, and it is pretty fast, so it's really not a big deal, but it is kind of silly to identify a machine based on a mutable property. Heck, on linux it's trivial to change the MAC address to anything you want! (I tried this with my VPN client, but it had none of it.)
I suggest the activation process something more stable, like the CPUID on Intel processors or, barring that, restricting the MAC address search to physical interfaces.
At present case structures have options (right click) to create multiple cases if enums are attached to the case selector. If someone want's to reuse the same case structure with less number of items in a new enum, one has to manually delete one case at a time. Having an option to select multiple cases to delete, or automatically delete broken cases would be desirable to speed up things.