LabWindows/CVI Idea Exchange

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

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.

support of Unicode character set would be most welcome

On high resolution monitors, the icons in the toolbar, project tree, and library tree in CVI are really tiny. Font sizes can be configured, but icon sizes cannot.

As usage of high resolution monitors becomes more common, I think it would be very helpful to provide some configuration options to optimize the appearance and usage of the CVI environment on monitors of varying resolution. Please refer to the attached screenshot for an example of this behavior.

I would like to have the possibility to store the uir-file not as a tui-file (old-fashioned ini file), instead as a xml file.

It would be great if NI could provide standard translations of the NI runtime message file msgrte.txt in commonly-used languages.

 

Whilst we can get translations done ourselves, it is normally done by translators who have little knowledge of the runtime context so the quality is rather variable; also, I get the feeling that we are duplicating effort that may have been already spent elsewhere.

 

If it helps, I for one would be willing to pay for a decent translation.

The option tooltip is very good feature what is the problem is it is only for the controls. If I want to show tooltip for listbox then it is fine but what if someone wants to show tooltip for active rows. It simply doesn't. 

 

This is very basic but one of the disadvantage of labview over .NET.

 

This needs to be fixed

After loading a file file into the UIR Localization Tool you have the ability to show a preview of individual panels with the localized strings by pressing the "Open >>>" button. The problem is that, unless the panel is set to auto center in either direction, the preview honours the actual position (top, left) the panel has into the UIR file, with the effect that some panels cannot be previewed as they are out of the viewable screen area. As an example, see the attached UIR file, where PANEL_4 and PANEL_6 are not auto centered while the others are: you'll see that their position is not in the center of the screen.

 

In my opinion the goal of this tool preview ability is to show the final aspect a localized panel has, so it should automatically auto center each panel regardless the value these attributes have into the UIR file.