LabWindows/CVI Idea Exchange

Community Browser
cancel
Showing results for 
Search instead for 
Did you mean: 
Post an idea

Currently "intellisense" only show up when you enter control+space keys after typing a few characters.

 

In this case I typed: setctrl and then control+space to show up this:

 

intellisense.jpg

 

 

Another example:

my_var.jpg

 

I would be very efficient if this "intellisense" shows up as soon as you start typing first letter of variable name or function name.

Hello,

 

searching through the C code for specific controls first and foremost requires the knowledge of the control's name... If there are some hundred it may get difficult to remember and thus I typically have to check the UI for the constant name. Clicking on the control shows its name in the status bar, a welcome feature, but unfortunately I cannot directly use this text for searching...

 

statusbar.png

 

What I suggest is allow copying this status bar field using CTRL+C; then it's possible to switch to the C code, press CTRL+F and CTRL+V... (The property browser is not really useful here because it only lists 'NUMERIC_7' and misses the associated panel)

 

Another, even more powerful feature would be to add a right click popup menu either to this status bar field ('Search C code for this constant') or to the control popup itself: Besides 'Generate control callback' etc. I'd like to see another entry 'Find control in C code'

 

Thanks!

Hello,

 

I would consider it quite convenient having a simple CVI function, similar to GetPanelDisplayBitmap, providing a true screenshot image of a CVI panel.

 

As discussed here, the CVI function GetPanelDisplayBitmap does not provide a screenshot image of the panel, i.e. the bitmap lacks all OS-specific features (color theme etc.).

 

For backward compatibility reasons, NI should provide a new function, returning a bitmap that looks the same as if I would have pressed Alt+Prt Sc

 

 

Thanks!

 Hi

 

It would be nice for the distribution to be in one installer able file.

Which i could then send to a customer.

 

Regards

Shakeel

At the moment the maximum panel and control name length is limitted to 32, if you set them programmatically.

 

Because of longer customer system signal names it is not possible to use them directly as control names. If the maximum length could be raised to 64 or to the maximum label length, it would help to avoid to generate new control names and the additional mapping between costumer system signal names and the generated control names in the test environment.

Hello,

 

it was very nice to see clang updated to version 3.3 in CVI2015; I wish this support of current versions of clang will be continued in the future, so I am hoping that with CVI2017 we might get clang 3.9 or 4.0 because of the following issues:

- many many bug fixes in clang

- improved diagnostics

- support of C11

- full support of OpenMP 3.1 and beyond

 

Thanks!!

If the thread that FileSelectPopup (and similar) is accessed is multithreaded, wacky things happen. The programmer can fix this by creating a new thread that is itself not multithreaded and pass information back to the current threrad. It would be helpful if the current functions were designed to default to create such a thread,  return the value(s), and garbage collect removing the programmer from the loop.

 

In the case of MultiFileSelectPopup, it is not clear to me what would be the best practice given the unknown number of results. I guess one could assume a limit for the number of results that may change as the Windows API does.

 

Other possible solutions can include an added parameter (variable switch) or with a whole new function. I could see the default case as an effective solution for legacy code that is partially refactored for multithreaded performance.

Hello,

 

building on this suggestion I'd like to see a more comfortable panel of the UI editor for editing label/value pairs, see below:

 

LABEL.png

 

Suggested changes:

 

  1. Add the possibility to dim / hide the selected entry
  2. Add the possibility to insert separators in the GUI editor, not only programmatically
     
    Thanks!

 

Hello,

 

I am still happy that the tooltips have been moved from the Programmer's Toolbox to the UI editor. Smiley Happy

 

Now when using them on a more regular basis it turns out that the programmer might grant the user the option to show / hide them. As a result, I would need to programmatically browse through all controls to change the respective parameter (the same is true for the delay time).

 

Hence I propose providing two new, more or less global attributes (these could possibly be panel attributes) that set the tooltip enable/disable status and the on/off delay times for all tooltips (on a panel).

 

This feature is not urgent as it can be implemented already now with some effort, but it might make code a bit shorter and simpler Smiley Wink

 

The more 'urgent' tooltip requests are here...

When working on laptops the room space in the UIR editor is relatively small compared to the size of actual wide desktop videos. Moreover, starting from CVI 2010 the user interface browser consumes additional room to the right of the editor, thus leaving only a few space to design/review panels.

It would be a good addition the possibility to preview an entire panel on the screen, with the ability to zoom in and out so that one can have an idea of the final aspect the panel will have.

Summary:

Hovering over the breakpoint diamond, a tooltip should display the breakpoint condition.

 

Description:

Useful breakpoint information, such as the breakpoint condition, line number or hit count could be displayed when hovering over the breakpoint diamond in the source editor. Otherwise, you would get this kind of information by looking at the breakpoint in the Breakpoints Window or the Edit Breakpoint Window.

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.

 

CustomColors.PNG

 

Regards,

 

Brandon V.

 

 

We hear all the time that should write code that is reuseable. It is difficult to plan so far ahead, so I listen to the preachers but seldom follow them.

However, it is clearely easier to use snippets, code fragments, that I put together for something, even tested them and I remember that I have done that once, but finding it again is too much hassle, it is just 3 lines, 5 lines of code. It owuld be nice to be able to manage such snippets, copy them, tag them,or even share them; I recon, there are snippet libraries out there;,out of sight, out of reach;  but it would be really nice when the need arises, - you know that nagging dejavue feeling- than I could find them, bag them an use them... With time, even nice and practical libraries could grow out of them snippets... 🙂

/Layosh

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.

This is sort of a slight extension of the valuable suggestion by vix (Go to Next/Previ​ous function in source files😞

 

Right now, in the CVI IDE it is possible to have a function tree of all library functions - for larger projects it might be useful to also have a function browser for all the functions in the current project, thus not only permitting to jump to the next or previous function, as suggested by vix, but also to more easily return to a frequently used function by one mouse click on the function name in the function browser.

 

Functions could be grouped by file name (typically there is more than one source file in a project), or alphabetically...

A feature that is still missing in NIReport is the ability to show a preview on screen of the generated report.

This feature could help very much the developer in designing the report without the immense wasting of paper that its lack implies. Moreover, customers are more and more requiring this feature to check reports before actual printing them, especially in applications where reports can be tailored some way to adapt to customers requirements.

 

Both reasons prevent me at present to use NIReport,

If you have a Numeric Indicator, and you set "Range checking" to Notify, CVI will show an ugly popup when you enter a value out of range.

If you set this property to "Coerce", the value you enter is coerced in range, but no specific event is generated.

 

I think that an EVENT_VAL_COERCED would be really useful: using this event you could easily show a message popup, for example.

Where does NI stand on this????

NI no longer supports 32 bit OS, but hasn't ported their own toolkit to x64. Since NI is NOT committed to developing (or even maintaining) CVI toolkits, how about open sourcing these so that users and the community can move these forward.

Code refactoring is a common need for C developers and availability of eiter automated or semi-automated tools can be really helpful.

Since LabWindows/CVI now uses llvm+clang, probably a tool like "include-what-you-use" can be integrated.

This is the github page for the tool.

 

From the documentation:

"Include what you use" means this: for every symbol (type, function variable, or macro) that you use in foo.cc, either foo.cc or foo.h should #include a .h file that exports the declaration of that symbol. The include-what-you-use tool is a program that can be built with the clang libraries in order to analyze #includes of source files to find include-what-you-use violations, and suggest fixes for them.

The main goal of include-what-you-use is to remove superfluous #includes. It does this both by figuring out what #includes are not actually needed for this file (for both .cc and .h files), and replacing #includes with forward-declares when possible.

 

Here you can find this topic discussed in LabWindows/CVI forum.

Hello,

whereas it is possible to add, remove and rename a folder in the project tree via a right-click popup menu it is unfortunately not possible to rename a file.

Instead one has to remove the file (plus its accompanying include file) from the project, rename it in Windows File Explorer, and then add it to the project again.

It would be more convenient being able to do so within the project tree, similar to the ability to rename folders.