LabWindows/CVI 2020 Bug Fixes

Panoramica

The following items are notable issues fixed between the release of LabWindows/CVI 2019 and LabWindows/CVI 2020, including additional patches and service packs. If you have an issue ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of LabWindows/CVI 2020.

Bug Number

Legacy ID

Description

Details

220036 391403

Autoscale is a valid option for the y-axis of a strip chart, but the option is missing from the Attribute Browser.

Workaround:

Edit the option in the Edit Strip Chart dialog box.

Reported Version:

LabWindows/CVI 2009

Resolved Version:

LabWindows/CVI 2020

Added:

Sep 8, 2020

278932 447401

Compiler Defines return compile errors when porting code from LabWindows/CVI 2009 to LabWindows/CVI 2010.

In LabWindows/CVI 2009, multiple Compiler Defines are separated by a comma then a space. However, in LabWindows/CVI 2010, multiple Compiler Defines are expected to be separated by only a space. When compiling code in LabWindows/CVI 2010 that complies with the LabWindows/CVI 2009 Compiler Defines format, illegal character build errors are returned.

Workaround:

Remove the commas separating the Compiler Defines.

Reported Version:

LabWindows/CVI 2010

Resolved Version:

LabWindows/CVI 2020

Added:

Sep 8, 2020

278982 438547

The Functions in File dialog box immediately starts scrolling up when opened.

When a ring control contains items that can no longer be displayed on the screen, LabWindows/CVI opens a modal dialog box containing a list box with all the items in the ring.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabWindows/CVI 2012

Resolved Version:

LabWindows/CVI 2020

Added:

Sep 8, 2020

278899 556606

Tooltips can be clipped by bottom edge of monitor.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabWindows/CVI 2012

Resolved Version:

LabWindows/CVI 2020

Added:

Sep 8, 2020

279107 555915

The Information Status of the UI editor does not always show the selected control.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabWindows/CVI 2012 SP1

Resolved Version:

LabWindows/CVI 2020

Added:

Aug 22, 2016

279145 543055

The predefined macros in the Build Options dialog lists macros for previously selected configuration when All Configurations is selected in Configuration ring.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabWindows/CVI 2013

Resolved Version:

LabWindows/CVI 2020

Added:

Aug 22, 2016

220014 586821

Selecting "Compile with precompiled include file" in Build Options causes Assertion Error in Windows Event Viewer.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabWindows/CVI 2013

Resolved Version:

LabWindows/CVI 2020

Added:

Sep 8, 2020

278990 457821

Including datasize.h and windows.h causes a typedef redefinition with different types error for the INT8 type definition.

Workaround:

Modify datasize.h by commenting out the following line:

Reported Version:

LabWindows/CVI 2013

Resolved Version:

LabWindows/CVI 2020

Added:

Mar 28, 2014

279159 657483

Canvas control width cannot utilize the full range of values.

The width of a canvas control is specified with the attribute ATTR_WIDTH. The documentation specifies that the valid range for this attribute is 0 to 32767; however, when the width is set to 32655 or higher, an "out of memory error" may occur.

Workaround:

Set the ATTR_WIDTH to be less than 32655.

Reported Version:

LabWindows/CVI 2013 SP2

Resolved Version:

LabWindows/CVI 2020

Added:

May 22, 2019

278948 730724

A static string tree control will show an incorrect value after modifying the attributes of the control.

On a static tree control displaying strings, after setting the value of a cell and then modifying the column or cell attributes, the UI will show the display value as "0".

Workaround:

Reset the value to the desired string.

Reported Version:

LabWindows/CVI 2015

Resolved Version:

LabWindows/CVI 2020

Added:

Sep 8, 2020

279045 736505

"Panel, menu bar, or control array handle is invalid" error after loading the Edit Installer dialog when there are Japanese characters in the .cds path of a new distribution on a Japanese operating system.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabWindows/CVI 2019

Resolved Version:

LabWindows/CVI 2020

Added:

May 22, 2019

279090 440070

The Find Next feature of the Find dialog box does not move to new results on subsequent uses.

If you do not move the text caret from the first result you find and subsequently click Find Next from the Find dialog, you stay at the same result.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabWindows/CVI 6.0

Resolved Version:

LabWindows/CVI 2020

Added:

Dec 6, 2013

279114 438733

If "Hide windows when application is running" is enabled, and a run-time crash occurs in the Interactive Execution window, the development environment becomes hidden and cannot be restored.

Workaround:

Select "Show windows" from the context menu of the task bar.

Reported Version:

LabWindows/CVI 8.0

Resolved Version:

LabWindows/CVI 2020

Added:

May 7, 2014

279050 488375

The Find UI Object (<Ctrl-Shift-U>) feature does not work for controls on tabs which are not being shown.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabWindows/CVI 8.0

Resolved Version:

LabWindows/CVI 2020

Added:

Aug 22, 2016

278936 464163

If a User Interface Resource (.uir) file has been changed, the associated header file will be regenerated when building the project, even if there are no changes required to the header.

Workaround:

Save the .uir file before building the project.

Reported Version:

LabWindows/CVI 8.0

Resolved Version:

LabWindows/CVI 2020

Added:

Sep 8, 2020

278942 467070

The Maximum and Minimum fields in the Edit Table Cell dialog box are not wide enough to show int64 values.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabWindows/CVI 8.5

Resolved Version:

LabWindows/CVI 2020

Added:

Sep 8, 2020

279077 519487

The source editor tabs are not updated when cycling through files during a Resolve All Excluded Lines operation.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

LabWindows/CVI 8.5

Resolved Version:

LabWindows/CVI 2020

Added:

Aug 3, 2015

279119 484206

The image quality of some images loaded in a picture command button degrades after saving and loading the user interface file multiple times.

Reduction of quality is noticeable after 10 saves.

Workaround:

Reload the original image from disk. You can do this programmatically by setting the ATTR_IMAGE_FILE attribute with SetCtrlAttribute.

Reported Version:

LabWindows/CVI 9.0

Resolved Version:

LabWindows/CVI 2020

Added:

Aug 22, 2014

279093 466209

The DebugPrintf function truncates large strings when printing to the Debug Output window.

Workaround:

Split long strings into multiple print statements.

Reported Version:

LabWindows/CVI 9.0

Resolved Version:

LabWindows/CVI 2020

Added:

Aug 22, 2014

Additional Patch Information

Installing some patches may require certain additional steps or considerations. Please refer to the following table for more information about patches for this release.

These patches currently do not have any special instructions.

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).