Archived: LabWindows™/CVI™ 2009 SP1 Bug Fixes

NI does not actively maintain this document.

This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.

Overview



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

Table of Contents

  1. Development Environment
  2. Performance
  3. User Interface
  4. Debugging/Compiler
  5. Stand-Alone Applications and Distributions
  6. ActiveX
  7. Miscellaneous
  8. Related Links

 

Development Environment

Bug ID

Fixed Issue

Has Run-Time Impact?

196251 The Attribute Browser allows invalid characters and constant names longer than 10 characters for panels. No
230084 Progress bar in environment does not auto-fill. No
198333 The DLL Import Library Choices dialog box shown after selecting Options»Generate DLL Import Library results in the error Invalid Control ID. No
198322 The Attribute Browser allows you to edit read-only .uir files. No
199243 LabWindows/CVI displays innocuous error message after clicking on a panel title bar in the Edit Panel dialog box No
198624 Options»Generate DLL Import Library fails for 64-bit DLLs. No
201769 Help»Win32 API results in an error message after installing the Documentation from MSDN Library. No
199755 The build step variable %CVIBUILDCONFIG% does not support 64-bit configurations. No
201054 When the Attribute Browser is empty, toggling Find/Filter results in the error A custom control callback raised an exception. No
208315 Collapsible region markers may not update correctly as you scroll through a source file. No
208352 In the Edit Text Message dialog box, inserting a new line by pressing <Ctrl-Enter> does not update the control. No
226445 Row and column inheritance of table controls does not work in the User Interface Editor. No
236861 Function panel for CNVSetArrayDataValue has incorrect prototype. No
196251 The Attribute Browser allows panel names longer than 10 characters. No
208388 Error messages may display when connecting with Windows Remote Desktop to a remote machine running LabWindows/CVI. No
172157 Diffing two files can cause window contents to draw in the wrong window. No

 

Performance

Bug ID

Fixed Issue

Has Run-Time Impact?

200777 Multibyte characters on a .uir file may cause the LabWindows/CVI environment to hang. No
232735 Small timeouts in RS-232 write operations can cause the application to hang. Yes
218499 Calling GetTCPPeerName with an invalid handle can cause the application to hang. Yes
201259 Calling RegisterWinMsgCallback and UnRegisterWinMsgCallback from different threads may result in a crash. Yes
203396 LabWindows/CVI may crash if compiling a project that includes header files from earlier versions of LabWindows/CVI. No
202181 Memory corruption may occur in programs that duplicate graph controls. Yes
200341 A hang can occur if a panel is displayed from a thread other than the main thread and the main thread does not process events. Yes

 

User Interface

Bug ID

Fixed Issue

Has Run-Time Impact?

197797 The strip chart cannot plot more than INT_MAX points. Yes
235344 The right Y axis name of a graph does not adjust correctly when the graph is resized. Yes

 

Debugging/Compiler

Bug ID

Fixed Issue

Has Run-Time Impact?

206299 Running instrument driver function panels may result in a link error when using a 64-bit configuration. No
223736 Debugger may invalidate stored return values of gmtime and asctime. No
201360 Incorrect usage of designated initializers (C99) may result in a hang in the LabWindows/CVI environment during compilation. No
196430 Large static arrays declared in a block scope can cause a stack overflow if Detect uninitialized local variables at run time is selected. Yes

 

Stand-Alone Applications and Distributions

Bug ID

Fixed Issue

Has Run-Time Impact?

201771 Distributions specifying a minimum .NET version of 3.0 or later do not build. No
203306 Some .cds files created in versions of LabWindows/CVI prior to LabWindows/CVI 2009 may not work in LabWindows/CVI 2009. No
202378 LabWindows/CVI cannot load .cds files specifying Windows 7 as the minimum operating system. No
218345 Missing dependency DLL error messages reported when debugging or deploying an RT program. Yes

 

ActiveX

Bug ID

Fixed Issue

Has Run-Time Impact?

212718 Applications with ActiveX controls may hang if the active panel is changed from a non-UI thread. Yes
216830 Loading a panel with an ActiveX control in a thread other than the main thread will fail. Yes
222668 An internal error when loading a panel with ActiveX controls can cause a crash. Yes

 

Miscellaneous

Bug ID

Fixed Issue

Has Run-Time Impact?

192713 LabWindows/CVI returns error -6604 when calling TDMS_ConvertFileFormat. Yes
225480 InetPing returns error if address does not exist. Yes
216631 Hidden files cannot be opened for writing. Yes
201130 Calling OpenComConfig with an input queue size greater than 40960 bytes results in unexpected behavior on Windows. Yes
200251 Paths with the separator '/' are not accepted by LabWindows/CVI ActiveX automation functions. Yes
201013 OpenComConfig does not return an error if the configuration parameters are invalid. Yes
237190 Variable argument parameters are documented as void * in the LabWindows/CVI Help. No
200677 Path control autocompletion may interfere with the text a user enters. Yes

 

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