because I had installed CVI2010 on a brand new Windows 7 machine, I was curios to find out about all the service processes running on the system.
It seems that there are quite a few NI services that start after log-on. Some of them seem superfluous, such as the Lookout Citadel service (no LabVIEW, no Lookout installed), but due to the lack of any information I did not bother trying to stop them
1) NI should critically review the services and only start the services that are absolutely needed.
2) Services that are optional might be selected by a checkbox during installation or from the Options / Environment setting
3) NI should provide some documentation / explanation of each service and why it is needed.
I'd like to see better documentation online.
Currently, documentation seems to be spread over different areas: online, in sample code included with the development environment, in a downloadable help file, etc. What online documentation there is is incomplete - for instance, if I'm looking at the function reFFT (just an example, I know it's obsolete), the online help gives me the parameters and what they are but they don't tell me acceptable values, e.g. what is the largest/smallest value I can use for numberOfElements: 1 - 9e99999? Another case was with the NIscope driver NISCOPE_ATTR_INPUT_CLOCK_SOURCE. When I looked at the documentation (downloaded zip file filled with CHM files) there was a list of defined values but no desciption of what they were or were not for. Example: NISCOPE_VAL_NO_SOURCE ("VAL_NO_SOURCE")...I *assume* NO SOURCE is equivalent to Intenal but should I really have to guess when looking at documentation? For that matter, why does this information only appear to be available via downloadable file?
In another case with NISCOPE I found that the niScope_ConfigureHorizontalTiming expects a certain clock frequency (10 MHz) if you're using an external clock, but if you are using a clock frequency at exactly what you're asking for you have to set the attributes directly. I messed with this for a while before calling the help desk. The person at the other end was able to tell me how to fix my problem but he could not find documentation online (accessable by me) where this information could be located. It seems to me that the number of help calls could be drastically reduced if sufficient help were available online. Finding information on error codes is similarly lacking.
I also have a problem with referencing "installed" sample code in lieu of a online programmer's manual. I don't always run on my development machine. So I'm on my target system (that does not have the development environment installed) and I want to look something up...it's very frustrating to find all help on a particular subject referring to my development machine.
It would be nice to be able to add some comments on UIR objects in the editor.
I'm mainly concerned about versioning: sometimes I happen to apply some modifications to existing panels / objects that are not self evident and I run the risk of forgetting them while revising the project after a couple of weeks.
As an example, I have recently modified some string and text message controls using "Greek" character set so that I can embed omega and delta symbols in them. At present I have a text file describing all modifications I have done in the project, including those in the UIRs, but it means I need to revise this file when I open the project again. It would be good if I could add a comment on those controls and have a visual reminder of it directly in the editor (e.g. with a little symbol like when you add a comment on an Excel cell) so that every time I open the UIR I see the presence of comments at a glance.
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.
On my development machine, I have access to various library functions in the NI-Vision library. Some of these functions apparenly require the NI-Vision Acquistion license, and some of these require the NI-Vision Runtime license, and some of these require no license. They are all mixed together and I can find no documentation anywhere that tells me which license(s) I need to put on the deployed computers given what library functions I call in my application. The only reliably way I have found to determine this is to deploy a test application to a PC that is not licensed and see if the function call fails with an ERR_UNREGISTERED. It seems that there should be a better way. Thanks.
It would be great to add the possibility to include documentation for (especially global) variables and data structures to the HTML documentation. Currently only functions could be documented. And it would make no sense to duplicate information about data structures used as parameters in each function which is using it.
It would further make sense to structure the HTML documentation at least by the module (.C file) it is defined in, together with the variables and data structures. Such you would get a tree like HTML doc with the modules as 'chapters', then sections for data structures, variables and functions. At the moment I get one big HTML index with documentation from all functions within the project sorted by name (I have not been able to find out how to get another structure in the 'functional index').
In best case there should be a chance to group 'public' data structures, variables and functions independent of 'private' ones to clearly identify the ones which are the intended interface functions and which are module internal helping functions. One way to automatically distinguish between this types might be using all functions documented in .H files as public and documentation from within .C files as private.
It has been discussed here.
I suggest to add a note to the documentation, for example
_TARGET_PRODUCT_VERSION_ and _TARGET_FILE_VERSION_ values are updated only when the file that contains them is recompiled.
So be sure to include them only in files that are recompiled at every build.
Please can we CVI users have a completely seperate forum/ knowledge exchange from LABVIEW, I seem to spend ages looking for solutions only to find they have been done using labview, even if I include cvi in the search. The knowledge base sometimes appears to jump from a cvi forum into a labview forum, this can be frustrating.
p.s.This idea exchange is great
What is the point of this Idea Exchange, when there is such a low uptake rate from NI?
There have been many very good suggestions posted here, but only 6 are labelled as "In Beta", which I assume means will be in the CVI release this autumn. There are 106 "Under Consideration", but there is no indication what is required to move them to "In Beta". For instance, Wolfgang posted "Reduce and document the NI services running after Windows logon" on 04-01-2011. It went to "Under Consideration" on 08-15-2011. Two Years from the original posting, we still have nothing!
How do I justify renewing our Volume Licence Agreement when the LabWindows development effort within NI is so small?
This is an (extensible) list of things I'd like to see improved in the CVI help:
- I miss a list of all obsolete functions, preferably in an ordered, linked list showing obsolete function name, replacement function name (if any), library, CVI version of improved function:
Convolve | ConvolveEx | Advanced Analysis Library | CVI 9.0
- I miss a list of all new functions / attributes ... per version (if I am updating one of my older projects that has been untouched for years I'd like to also update it to new CVI features (and change to non-obsolete functions) so I'd like to see what is new since then.)
- I'd also like to have the lists of fixed (and open) bugs included in the help
In the CVI IDE I am using tags to mark functions as 'ready'. It would be nice if different tags would be available allowing to simultaneously flag several characteristics, such as 'checked', 'verified', 'tested'... I would imagine differently colored flags, possibly similar to the colored flags available in Outlook.
In larger projects this might be a useful feature to add some quick 'documentation' of the development status, and using F2 (goto next tag) to go to the next function that is not finished yet, has not been tested, etc.
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.
Note: the LabWindows/CVI Idea Exchange is not the appropriate forum to submit technical support questions.
The LabWindows/CVI R&D team is committed to reviewing every idea submitted via the LabWindows/CVI Idea Exchange. However, we cannot guarantee the implementation of any LabWindows/CVI Idea Exchange submission.