LabVIEW
Share Your Input: The Next LabVIEW Feature to Go Open Source
Make the documentation of VI's open source. Periodically I think that some information is missing in the VI's documentation.
I would like to see a repo, where one could create a pull request for VI documentation.
E.g.
To more specific class:
VI Doc:
Typecasts a reference, such as a control or a type definition, to a more specific class or interface in the inheritance hierarchy.
Returns the input's default value when an invalid type cast occurs.
Html Doc:
...
For example, if Class A inherits from Class B, a variable of type B can hold a value of type A. You can use the function to downcast from type B to type A. If the typecast is invalid, this function returns an error at run time and an instance of the input's default value.
...
The pull request could then be peer reviewed for mistakes or different optimizations.
@Quiztus2 wrote:
Make the documentation of VI's open source. Periodically I think that some information is missing in the VI's documentation.
I would like to see a repo, where one could create a pull request for VI documentation.
That's the out-of-the-box thinking we need around here. My mind has just been thinking about code. Documentation is a great thing that the community could really help with.
@Quiztus2 wrote:
Make the documentation of VI's open source. Periodically I think that some information is missing in the VI's documentation.
I would like to see a repo, where one could create a pull request for VI documentation.
E.g.
To more specific class:
VI Doc:
Typecasts a reference, such as a control or a type definition, to a more specific class or interface in the inheritance hierarchy.
Returns the input's default value when an invalid type cast occurs.
Html Doc:
...
For example, if Class A inherits from Class B, a variable of type B can hold a value of type A. You can use the function to downcast from type B to type A. If the typecast is invalid, this function returns an error at run time and an instance of the input's default value.
...
The pull request could then be peer reviewed for mistakes or different optimizations.
Dang that's a good one!
@PhillipBrooks wrote:
How about the LabVIEW Unit Test Framework Toolkit?
I have been experimenting with it and it and found various problems that I can't solve other than to delete and recreate the test and vector files.
The UI is buggy and has problems with lvtest strings targeted at VI paths.
That was my experience as well. I'd have tests that wouldn't pass, then I could close/reopen, and they'd pass again. There seems to be SOME kind of relationship with lvclasses or reentrant VI's or possibly having a VI open vs closed when running the test or something that I couldn't ever figure out, so I just abandoned using that framework. I'm sure there was user error involved, but I couldn't find anywhere that said "make sure you close all your VI's before you run the unit tests" or "make sure you DO have them in memory" etc.
