Search the Community
Showing results for tags 'dependencies'.
Found 2 results
I started a new thread because I didn't want to hijack the great article about dependencies between classes : https://lavag.org/topic/19421-visualizing-dependencies-between-labview-classes/ Historically our code has contained numerous circular dependencies, where a member of library A would call a member of library B, and another member of library B would call another member of library A. As you know this situation isn't great for at least 2 reasons (but I'd love to hear even more reasons from you) 1) There is no way to load just a basic library in a small project without loading almost all the source code of the application 2) There is no hope to be able to switch to Packed Project Library one day After many days, I managed to refactor the code and got rid of almost all of the circular dependencies. I'd like to have a visual way to show the difference between the "before" and "after". The VI Hierarchy tool does show that but there is just way too much going on to really make sense of what we're seeing. I'd like a similar tool that would only show the dependencies between libraries, without seeing the details of the libraries content. Do you know such tool? Thanks!
I want to make an exe application from a .vi to install on another non-labview-installed machine (I want to use the runtime engine). The only problem I can foresee is that I built the software on a version of Labview that has all the add-ons, and I don't know which ones I have used. I want to know if there's a way to identify which add-ons or national instruments programs have to be installed in order for my exe to work. I know I used IMAQ and IMAQdx, and many of the programmer functions such as case statements, but there's probably more I don't know about. Sorry I can't attach the vi, it's potentially going to be sold in the future. Thanks for any help you can offer, James