LabVIEW Idea Exchange

Top Authors

User

Kudos

Post an idea

When a third party add-on expires you get a dialog asking you to activate it, but the dialog does not offer you the option to remove it instead:

If would be nice to be able to select add-ons in the add-on list and then click a Remove/Uninstall button (and/or right-click). The current solution is to manually fire up the package manager and uninstall it from there (the remove button could alternatively (if needed /quicker to implement) call the package manager and tell it to start the removal of the selected packages.

Interactive Application Builder API

Currently, when you programmatically build an application using the "Build" VI of the App Builder API, you have no feedback (such as build details, progress percentage, warnings, errors...) and no ability to cancel while it builds.

So you have no idea how long it will take to build and cannot cancel if it takes too long.

It would be great to have these interactions, just like with the manual build:

The Build VI could have 2 notifiers or user events as additional inputs:

- 1 to receive build details, progress percentage, warnings and errors

- 1 to send the Cancel command

These additional inputs would be optional and default to invalid refnums, which would mean "do not use the feature".

View All (1)

LabVIEW Codewars

View All (2)

View All (5)

View All (1)

dotnet Core Support

Modern embedded web browser

View All (4)

Usually, unsupported LabVIEW features can be enabled with nothing more than an undocumented INI key. The one exception that I know of is the integrated XNode development feature in the Windows version, which is instead controlled by the license manager. (This feature exists in the Linux and Mac versions as well, but on those versions it's an INI key like everything else.)

Despite not being officially supported, community-made XNodes are very much a thing. Even on the Windows version, one can still create them using a third-party editor, or hack their way into the built-in one somehow. And it's clear that NI (rightfully) doesn't put much if any continued effort into preventing third parties from making XNodes, as the same methods that were used over a decade ago still work just as well now.

I'm not asking NI to provide official support for XNodes necessarily, but I think it's for the best if they at least remove all unnecessary, artificial roadblocks, and open up the XNode development forum and perhaps some internal documentation to the public, so community-based developers can at least have the best shot at learning how to do it right. You've already done this with Project Providers; why not XNodes as well?

View All (2)

Read/Write PDF

Add Target to VI Analyzer (API)

View All (5)

Software development has moved on since a similar idea was declined in 2016

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Make-LVdiff-and-LVMerge-available-for-all-labview-vers...

I would like to suggest just LVCompare is made available in all versions of LabVIEW.

If LVMerge was also available that would be great, but leaving in just in the Professional version would also work.

As a lone developer I use GIT even on very simple projects to give me the ability to rewind and see what changes I have made. Projects are often put down and picked up weeks later. LVCompare lets me see how far I had got. Its also very useful for picking up debugging that should have been removed. In short Software Version Control just make my life easier.

View All (3)

LVCompare for Classes and Libraries

When integrating libraries written in C# a common scenario that occurs is the necessity to cast a method to a generic delegate defined in the class in order to, for instance, subscribe callbacks to events belonging to sub-classes inherited by the object instantiated by the Constructor Node.

So far LabVIEW efficiently allows to subscribe to events, registering a VI as callback in case the event involved is fired, but does not allow to cast a VI to a generic delegate and that's very limiting.

The only workaround existing is to wrap the C# library, adding an additional C# layer that instantiates the delegates on behalf of LabVIEW and then exposes plain methods, properties and events that are straightly callable by LabVIEW itself.

The idea is to allow LabVIEW to instantiate generic delegates based on the definition of the delegate provided by the C# library and return the delegate object so that it can be provided as input to library's methods requesting it.

This feature would make the LabVIEW integration of C# dlls more solid and completely manageable within LabVIEW code without further wrappers needed.

Expand XML capabilities & examples

Just recently ran into an issue with XML namespaces where the LabVIEW implementation just didn't cut it. The AE had R&D confirm this too. The work around, after trolling through the vast sea of .NET XML features & forums, was there. Something this simple shouldn't burn up this much time.

The world around us uses JSON & XML extensively yet the examples are minuscule. It doesn't matter if new examples are .NET, Python or something else but we need to get to solutions quicker.

View All (2)

Official LabVIEW Docker Images

I wish LabVIEW had Official Container (Docker) Images.

With more and more users trying to use the docker in Continuous Integration, it would be

interesting supporting a NI Official Image on Docker Hub (or any other place). Containers provide an easy way of creating reproducible tests and builds.

The build of LabVIEW docker images has been feasible since NI Package Manager command line was launched, and for NI wouldn't be a new thing.

The advantage is that the images (Windows, Linux or Mac OS) could be optimized by NI team only for working for LabVIEW, shrinking size and removing unused files.

Anyone else would support this idea or has anything to complement?

Support Python Virtual Environments

View All (2)

It would be great if one could pull FPGA Bitfiles/changed Xilinx IP without recompiling the code / re-configuring the IP cores.

Currently it seems that I need to copy the Xilinx IP via the Filesystem (e.g. network-drives) after pulling a new version from a git repository.

This works since git doesn't detect any change (no commit required), but the modification date is preserved. But it is very annoying.

For FPGA bitfiles this trick doesn't work for me, at least not if the path doesn't perfectly match.

View All (3)

LabVIEW Idea Exchange

Allow removal of third party add-ons from the activation dialog

Interactive Application Builder API

LabVIEW Codewars

Add licensing and activation tools for packed project libraries (PPLs)

PowerAutomate connector and Drop-In connector VIs

Webservice Swagger/OpenAPI document generation

dotnet Core Support

Modern embedded web browser

Make VI Tags an officially-supported feature

Change XNode development to use an INI key rather than a license, and open the XNode development forum to the public

Read/Write PDF

Add Target to VI Analyzer (API)

Make LVCompare available in all LabVIEW versions

LVCompare for Classes and Libraries

Instantiate VIs as generic delegates when working with C# libraries

Expand XML capabilities & examples

Official LabVIEW Docker Images

Support Python Virtual Environments

Make FPGA Bitfile signature and Xilinx IPs version control (git) compatible

Support for Matlab version 7.3 files