LabWindows/CVI
labview compared to labwindows
Solved!
@CVI-User wrote:
Well, Qt is using C++ so you can get away with a lot of C code. C# starts with a "class Program".
(Not implying that it is good or recommended to use C++/Qt that way but it may help some folks or your code base in the transition.)
I have programmed (D)COM in standard C. A bit cumbersome but perfectly doable. 😁
Also: the advanced math functions like (inverse) FFT or filters are something all the alternatives are missing. But I guess (hope) LV has those, too.
Unless you buy the Base package. That has no AAL library. But generally everything LabWindows CVI has (in terms of libraries that is) LabVIEW has too and then some.
As already explained, the whole UI manager layer in LabWindows/CVI was originally simply lifted from the LabVIEW code base and then wrapped into a LabWindows for DOS compatible API. The AAL was a separate department at NI that did DSP, numerical calculus and what else and provided their library to both the LabVIEW and CVI development teams. Somewhere after 2000, NI decided that they could not possibly compete with the folks from the Intel MKL project and simply replaced the entire AAL backend with the MKL library. Many LabVIEW libraries are under the hood also programmed in C/C++ and if you link the resulting DLL to a LabWindows CVI or LabVIEW binding library is very irrelevant.
