LabWindows/CVI Idea Exchange

Post an idea

cvi forum

A couple of minor things:

1. Change it so that if characters like 'µ' are used in the documentation tags, that CVI doesn't generate invalid XML comments files. Or if that is not possible warn the user if they use characters like 'µ' in the documentation tags.

2. Make it so that Insert Construct -> Function Documentation Tags (Ctrl-Shift-G) doesn't insert an HIPAR paramater for 'void' for functions that don't have parameters. Also make it so that it doesn't insert HIRET tags for functions that don't return anything.

In principle CVI supports external compilers for an optimized release version such as Intel's ICL and I managed to successfully compile release versions using ICL 11.1.

However, documentation on this issue is sparse.

It is even worse if one attempts to use an external linker which might be appropriate if one attempts to use e.g. Intel's MKL. Here I would love to see the support of external linkers in combination with an improved documentation.

Similarly, CUDA is becoming more attractive for more demanding floating point applications - I would consider it very useful if NI could provide e.g. an application note of how to do this in an easy to follow tutorial.

View All (2)

LabWindows/CVI Idea Exchange

cvi forum

Documentation tags inprovements

better documentation / support of external compilers and linkers