Search the Community
Showing results for tags 'documentation'.
Found 4 results
I'm looking for a Node Map tool to document my applications using my messaging architecture. I want to write some code that can extract relationships between classes (some being processes and some being messages) and then feed that data into a tool to visualize the relationships in my application. The end goal would be something like the http://www.visualthesaurus.com/. Unfortunately, the software behind that tool starts at $5k. I am hoping to find something a bit less expensive. Has anyone found a solution they like? thanks, -John
Occasionally, I find the conciseness of the LabVIEW documentation a bit lacking. Here's an example that I would appreciate some assistance with. As shown in the screenshot below, the documentation for the "Register for Events" function states that the event source reference must be to a "local object" and not a "remote object". I'm assuming that: the term "object" here refers to an "application, VI, control or user event"; "local" means on the same physical platform as that on which the Register for Events function is located; and, "remote" means on a separate physical platform from the platform on which the Register for Events function is located. Can anyone confirm these assumptions, or better yet, point me to NI documentation that defines these terms? Thanks in advance for any help you can provide. (PS - The screenshot below is from LabVIEW 2012, but LabVIEW 2013 has the same description) -John Bergmans
We are looking to distribute our code. I was wondering if people had suggestions on the best ways to generated compiled help files (chm) for a VI library. I know there are some instructions in the LV help but thought there might be an "all-in-one" tool out there or some handy hints from people that have been doing this already. Thanks for you suggestions. John
Hey, I am going to be developing a lot of .lvlibs for reuse by others, and I would like to quickly generate documentation for them. I started programming a tool that recursively looks through a library by using the "Owned Items" property and iterating through those in order to find folders, .vis and .ctl. Then using the "VI Documentation VIs", the tool would just output a word document that contains VI icons, terminal lists, and descriptions. Does a similar tool already exist? I would gladly use such a tool if it already does. C