Hi, I am wondering if there is a dedicated place where to suggest minor or major improvements or report supposed bugs.... In the past, I did it in this forum, but it might be a little bit boring for others? Moreover, I would always expect an answer from NI if reporting some unexpected behavior etc., while in the forum not all entries might be addressed. In addition, it might be helpful if there would be a site where all officially acknowledged problems are listed - it might help if one encounters some 'strange' behavior and finds this already listed there - or not. Recently I have learned from this (rather hidden) link where to submit feature requests, and I thought of something similar... Does it exist, or would it be possible to set it up? Of course, I can send boring comments here, too, such as: in the Build/Target Settings/Version Info the checkmark label should read 'Preview Substitutions' instead of 'Prevew Substitutions' 🙂 Wolfgang

Hello dummy, You can always ask here about the state of any bug or suggestion. I don't know if we do it consistently, but we usually do post the bug report ID so that you can ask about it later. But even if you don't have the bug report, you can just link to the original forum discussion and we should be able to track it down. As for the general issue of making all the current known issues available externally, that is a request that we've heard before, and we hope to eventually be able to make it happen, but it's not a trivial thing. Our current bug report database has a large number of items in it that refer to internal-only issues (i.e. problems found internally on unreleased versions of CVI), and also contains false alarms, duplicate issues, trivial problems, non-bugs (tasks), reports of bugs that haven't yet been investigated, etc, etc. It's not a trivial task to filter out the "known issues" that are relevant to our users, as well as determining exactly all the versions of the product that have the bug. For example, creating the bug-fix list that you see when a new version of CVI is released is still a fairly labor intensive process, but it's feasible because tracking fixed bugs is very different tracking outstanding issues. Having said that, we haven't given up on the idea, and we hope to eventually be able to do something like this, since we are aware of how useful it is to customers. LuisNI

LabWindows/CVI

where to submit bugs / improvements

Solved!

Hi ElectroLund,

The most effective way to submit bug reports is through our support department. They can help classify the problem and can submit bug reports internally. I would say a second best approach would be to submit them on the forum, making sure the following are addressed, if possible:

What is happening?
When does it happen?
What changed such that the issue manifested?
What work arounds have you tried?
Provide code that causes the bug consistently

If it is a crash issue, a compatibility issue between versions of LabWindows/CVI (e.g., "I installed a new version of the runtime, and now my application crashes consistently"), or something else that is on that level of severity, make it very clear in the title of the post. The dev team cannot read through every post, so making your post titles accurately severe is a good way to make sure your post stands out.

Thanks,

Daniel Dorroh
National Instruments