From Saturday, Nov 23rd 7:00 PM CST - Sunday, Nov 24th 7:45 AM CST, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

Home Support Documentation Bugs

LabWindows™/CVI™ 2017 Bug Fixes

Updated Mar 10, 2020

Overview

The following items are changes in LabWindows/CVI 2017. If you have a Bug ID, you can search this list to validate that the issue has been fixed.

Bug Fixes

The following items are Bug Fixes in LabWindows™/CVI™ 2017. 

IDFixed Issue
439323LabWindows/CVI ignores changes made in the Environment Color Preferences dialog box in one of three panels in the Variables and Call Stack window
522704The build system incorrectly skips the compilation of a C file, if both the C file and an included H file have unsaved changes.
543786The __TIMESTAMP__ macro is incorrect when building with unsaved changes.
591943The _mbsnbcpy function will cause a fatal runtime error in 64-bit applications on a multibyte OS.
595132Breakpoints do not execute in the correct place when used on lines with macro-expanded functions.
595401LabWindows/CVI displays a message saying an Unrecoverable Internal Error has occurred when loading a workspace file containing two or more untitled projects.
597012A failure in a custom post-build step will not cause the overall build to fail.
599510An internal error occurs when trying to cut all tabs in a tab control.
603790GetCtrlArrayFromResourceID returns error -24 when accessing a control array if the panel is loaded into a tab page.
604455Viewing the value of a char* array while debugging will display a popup stating "The index passed is out of range".
610601The debugger will incorrectly break in the last of several repeated IF statements when one of the IF statements contains a return statement.
611786The NewBitmap function allocates an unnecessary amount of memory.
624508Distributions whose max OS requirement is Windows 10 fail to install on later Windows 10 updates.
624635TUI files saved by the auto backup feature are not automatically deleted.
625203CVI crashes after creating a patch installer for an existing UI application.
626003Editing a control value with the Operate Tool will crash LabWindows/CVI if the control is bound to a datasocket server in Write mode.
628735Ring controls with no label and a large number of elements will log an error to the Windows Application log when clicked.
631540When debugging a project it is not possible to resume execution while an interactive execution is also suspended at a breakpoint.
631623The RegEnumerateKey function does not work in HKEY CLASSES ROOT.
631752Pressing the Home or Page Up keys while a picture ring has focus will cause a general protection fault.
634145The TDMS_AppendDataValues will cause a fatal run-time error when writing timestamp data.
637396The callbackData argument in InstallWinMsgCallback() is NULL when EVENT_NEWHANDLE is fired.

Return to the LabWindows/CVI Release Information document.

Back to top

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).