LabVIEW Idea Exchange

Community Browser
cancel
Showing results for 
Search instead for 
Did you mean: 
Post an idea

Good day forum

 

The already VI hierarchy is already a very useful tool in tracing dependencies and all, but if we can tweak it in the right way, it may be able to serve other purposes for instance, a organization chart plotter or mind mapper by playing with vi-subvi relations (multi-connection), icons as glyph, floating nodes as control/indicator terminal subVIs, etc.

 

if only this feature can be developed for LV users, it can serve as an additional value-adding tool, especially for mind mapping. should this be picked up, I would very much like to see a "resize-able" glyph for starters 🙂

 

or if it is remotely possible with the current versions through VI scripting, maybe the community can collaborate and work something out? and put it into Tools Network.

I think it would be very useful if when selecting a build specification, you could build all the dependencies of that build in a manner similar to the way "make" works.

 

When building complicated projects, there may be several builds. The simplest example is an application installer that depends on the the application to be built first. Another example is a suite of compiled utilities that all have to be compiled before the installer is made. Another example is an application that uses packed libraries, all of which should be built prior to making the final build and then the installer build.

 

"Make" is an old tool that does this dependency checking for you. If you select the installer to build, it would check the dependencies of the installer, defined in a "makefile", and then build any project that is out of date. The out of date projects are those where the last modified date of the source code is later then the last modified date of the built file.

 

In this way you can simply ask that the installer be made, confident that "make" would find all the required dependencies and compile them as well.

 

This can be baked into LabVIEW. The installer build already knows which build specification it is dependent on.

 

Below is an idea of where this feature would be implemented.

 

Make Dependencies.jpg