Starting from CVI2010, the User Interface Browser and the Attribute Browser are both located on the right of the UIR editor in the Workspace window.
I'd like to be able to hide these windows when required: when working on small screens like when you use a laptop these windows occupy a lot of space even if you reduce their size at the minimum.
In addition, the ability to choose which window to display on the bottom left could be a good option: up to version 2009 the bottom left side of the workspace window switched between the library tree (source editor) and the attribute browser (UIR editor).
Ideally, while in the UIR editor I would like to be able to:
I would like to suggest a function tree view in CVI. I feel this is sorely missing. Many times, I want to jump right to a function, but I don't remember where it is. In a single C file with 1,000+ lines, this can be very aggravating.
For this reason, I tend to use Notepad++ for the heavy lifting, along with the Source Cookifier plugin. See attached screenshot of that plugin.
There are options in the plugin to enable certain features, such as the global and local variables in addition to the function names. When you are inside a function in the souce editor, the tree updates with a selection to show that you are inside that function. This is very helpful with functions that have more lines than available veritcal screen space. This way, I don't have to scroll up to see what function I'm looking at. I simply look at the tree with a glance and I know.
It has been suggested much earlier here, but obviously passed out of mind:
When using 'Go to Definition' (CTrl+I) while in release configuration, CVI tells that no source code information was found for the identifier '...', because 'Browse information is not available in the Release configuration'... (still true for CVI2010)
This can and should be improved!
And it might be a good opportunity to also add the reverse process, 'Goto Declaration', suggested here
It would be nice to be able to import and export custom environment and color settings. This would allow users to transfer settings to another computer, and it would also allow the community to create color schemes that could be shared. Creating a good color scheme from scratch is time consuming, so it would be nice for both the creater and the user to be able to share the work that is done.
I would like to see an configuration of batchbuilt process. I have a big workspace with many projects; and would like to create different setups, like "compile only all server projects" or "compile all client projects". The workspace contains a big server-client -based software packages; some dll-projects used for server side only, some only client side.
Right now, it is possible to add a readme file to the distribution (Build / Distribution / Edit...). Unfortunately, the file type of a readme file (and the license agreement file) is limited to *.rtf.
It might be useful to distribute a more 'complex' readme file, e.g. including figures. Hence I would prefer to distribute readme.pdf instead of readme.rtf
Following the discussion with Luis here I want to suggest
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?
even today source code needs to be printed (to paper, to PDF...). So for a given font and font size there is a maximum number of characters per line that can be printed without forcing a line break.
Accordingly, I have arranged my source code that none of the lines exceeds this limit. I would consider it convenient to have a faint grey vertical line indicating this limit. So I suggest adding a 'ruler' with user settable vertical guides.
Thanks for consideration.
"Build All/Batch" would be helpful if place on tool bar menu. This feature would help developer who is familar with Microsoft Visual Studio development enviroment. CVI is already an subset of MS Visual Studio.
sorry for the strange title, I couldn't find a better one:
Right now, if I toggle a tag or set a breakpoint, these actions cannot be undone using 'Undo (CTRL+Z)'.
Similarly, if I want to discard any changes I have made in a project this may not be especially simple... If I simply close CVI then I am asked if I want to save or discard my changes - this is fine - unfortunately this does not include breakpoints, tags, etc. So even if I select 'discard', tags, breakpoints etc. are not undone.
I'd like to have a possibility to close a project in the state I have opened it.
Debugging code involving arrays is complicated by the facts that
In the CVI IDE the Window menu provides a list of View options, e.g. the Find Results.
While it's possible to display a window via selection of the corresponding menu item, it's not possible to deselect an item and hide/remove this window via the menu.
Moreover, even if the Find Results window is not selected, it does show up every time I use CTRL+F and hence does not honor my wish to not have it displayed.
Because every additional window requires some space I would prefer the possibility to decide myself if I want to have a Find Results window displayed or not.
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.