LabWindows/CVI Idea Exchange

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

I think it would useful to allow for a progress bar control type in a cell of a table.

 

This could be done manually by loading different canned images into the cell, which would be stills of a progress bar in motion.  But that's cludgey.

I love my CVI, but come on.  How great would it be to be able to debug your project inside VSCode?

Hi,

 

In 2015 and 2017 CVI, the horizontal scroll wheel of the mouse was working.

 

In 2019, the horizontal scroll wheel is not working now.


Since we don't have all extra-wide/extra-size screen, it is a very important feature we are missing.
The shift/alt or even the vertical scroll wheel of the mouse on the horizontal scroll bar does only vertical movement.

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.

In the .NET Controller creator, it would be nice:

  • to be able to give a pre-defined list of the only classes it is useful to wrap,
  • or that CVI memorizes the already checked classes it is useful to wrap

in order to generate the wrapper quickly.

 

Because it is very boring to have to regularly check manually only 22 classes among plenty of not collapsed classes.

a screenshot of the CVI dotNET Controller wizard.png

 

Note: I check only desired classes to reduce the compilation time of the wrapper (which is very big with all its classes: 350 000 lines of code in the resulting C file!), as suggested by the CVI manual.

 

Thanks.

LabWindows/CVI lags behind the more recent developments in its programming language, C. At present, it only partially supports the C99 standard, not to mention the improved Unicode support of the current standard, C11.

Since odds are that Unicode finally will be supported in a future version of LabWindows/CVI, this might be a good opportunity to also ask for support of the current standard of CVI's programming language, C11, allowing the use of UTF encoded strings and also including updated libraries (e.g., supporting complex or long long) and debugging tools (data tooltips and variable view supporting complex numbers, for example). It also would help to improve C/C++ compatibility for programs that use complex floating-point values.

 

I really would appreciate it if the LabWindows/CVI project will show some strong signs of development and accompany us for the next 30 years, too.

I miss it every time I try to replace a parameter or start typing a long function name and realize it's not the function I want. Or even just when I want to delete a single line and don't want to select the whole line, or sit there holding the backspace key while life passes me by.

 

It's especially annoying because CTRL+[arrow] navigates word by word. So this is half implemented already.

The CVI SavePanelState( ) and RecallPanelState( ) functions can be extremely useful.  Although the resulting panel state file is binary, it can however expose sensitive information with the use of even a simple tool like NotePad.  As a cumbersome workaround I had to use a command-line tool within my app, such as 7z, to compress and password protect the state file.   I suggest that CVI place a built-in protection into these functions.

Hi Everybody,
I'm a student, and now i'm interning at a company that wants me to develop an industrial vision system.
I would like to ask you if i can use NI Vision Builder for Automated Inspection (VBAI) with the Labwindows/ CVI
If so, how? and what are the difficulties that may affect me?
THANK YOU for your help !
Best regards,

Based on this discussion, Strip Chart controls don't support cursors.

I think it would be great if this support would be added.

The best option would be to have an advanced cursor like the "Graph Cursors Control" available for Graphs.

 

Other text editors such as UltraEdit have the capability to trim white space from the end of lines.  This would be a useful feature, as sometimes extra white space can end up at the end of lines, and is annoying when copy/pasting, etc.  I would expect to find it under Options->Editor Preferences, similar to the tab/space settings.

A useful CVI GUI tool would be the addition of sideways tree-style tab control.  I am surprised to see no mention of it in the forums.  Is there already some solution for it, or perhaps some Active-X that can do it?    Nevertheless, it would greatly modernize the GUI arsenal.

Hello,

 

working with larger UIs may result in scrollbars showing up in the UI editor. Hence it would be nice if hitting the 'PageUp' or 'PageDown' keys would scroll the page up or down, respectively. Also 'Home', 'End' and the four cursor keys should be supported, similar to their functionality in the text editor. 

 

Thanks!

Hello,

 

building upon my earlier (but difficult to implement) suggestion and the forum discussion on event data here I can provide a hopefully improved suggestion.

 

The issues addressed by this idea:

  • receiving an EVENT_DATA_CHANGED event for a numeric control does not mean that the numeric value has changed
  • receiving an EVENT_DATA_CHANGED event for a numeric control does not provide information if the value has been increased or decreased
  • receiving an EVENT_DATA_CHANGED event for a numeric control does not provide information if the 'up' or 'down' arrow button has been pressed (which is not necessarily the same as the second issue)

Idea: Provide eventData1 and eventData2 information.

 

For example, eventData1 could tell about the numeric value:

  • eventData1 = -1: numeric value has been decreased
  • eventData1 = 0: numeric value is unchanged
  • eventData1 = 1: numeric value has been increased

eventData2 could tell about the increment/decrement arrow, e.g.:

  • eventData2 = -1: decrement arrow has been pressed by mouse
  • eventData2 = -2: decrement arrow has been pressed on keyboard
  • eventData2= 1: increment arrow has been pressed by mouse
  • eventData2= 2: increment arrow has been pressed on keyboard

Since so far no eventdata are provided this suggestion should not break backward compatibility.

An option to have Popups on top of the hole application, and not just on top of the current thread. It doesnt make sense

(in most cases) to have a Popup that is hidden behind the main Panel, independent if it was called by the main thread or another thread.

Please give us at least the option to change the behaviour, for all types of Pop-up Panels.

 

I used to be able to change strip chart colors "on the fly".

This facility was available pre Version 8.5 - see http://forums.ni.com/t5/LabWindows-CVI/Changing-color-in-a-Strip-Chart/m-p/2292246/highlight/true#M60735

This would allow me to change the color for future points and NOT affect what was already plotted. This is the way that ATTR_TRACE_COLOR used to work.

As the above discussion thread says, this feature was a bug, but a very useful one at that!

Could we have a control that worked in this way ATTR_TRACE_POINT_COLOR which would only work for points plotted from thereon, the strip chart still scrolling as it does at present.

I believe that this could be done if I used a graph control, but that would involve explicity redrawing the graph for every plot point to achieve a scrolling display.

 

It would be nice to have another type of message popups, which do not block the program flow.

 

For example:

MessagePopup ("Do something");

Program continues.

Program checks if the user has done it.

RemovePopup

 

I know it can be done with custom panels and InstallPopup, but a simple MessagePopup would be a lot better.

 

 

 

 

 

(Coming from this forum discussion)

 

If you double click on a UI browser element you'll go to the corresponding panel or control in the editor. That's good! Smiley Happy

There doesn't seem to be a way to go the opposite direction (i.e. from a control in the user interface editor to the corresponding item in the user interface browser tree) Smiley Sad : this could be useful in case of complex UIR files with several panels and controls, especially if you have more than one control array in it.

 

So I suggest to add two options to the control context menu to locate the control in the UI browser ad to locate in a control aray if it is included in any of them.

I'm thinking to something like that:

 

 Screenshot 2015-03-06 09.26.41.jpg

 

It would be handy if these new items could be assigned a shortcut key too: ctrl+U and ctrl+R could be a good choice (presently ctrl+U is not used in the UIR editor and ctrl+R is not active at design time)

Here goes something very simple for the source editor:

- a menu and/or shortcut key that when in a .c file will open the corresponding .h file (if it exists), and also the converse.

Hi,

 

Currently, when a CVI application is deployed on a PC with a DPI setting different than the development machine, the application will generally not look like how the programmer intended as the fonts get resized while the other UI elements do not, leading to overlapping text, awkwardly resized controls, etc.  One way that DPI scaling could be implemented in CVI would be to use the same functionality as the 'Scale Contents on Resize' option for panels, where internally CVI could resize the panel and use this scaling to rescale all the UI elements (including fonts) on the panel to the appropiate size per the Windows DPI setting.  This would make the panel look a lot closer to what the programmer intended and would generally make most applications usable with different DPI settings without any additional work from the programmer.  Per my other suggestion, I would request that the programmer has the capability of disabling this functionality so they can handle DPI scaling themselves should they wish to do so.

 

Thanks.