LabWindows™/CVI™ 2013 Patch Details

The LabWindows/CVI 2013 f1 patch is available for the LabWindows/CVI 2013 Application Development Environment and Run-Time Engine for Windows. 

The patch fixes the issues listed in the following tables. NI strongly recommends this patch for all LabWindows/CVI 2013 installations. 

Note:  The LabWindows/CVI 2013 f1 patch installs automatically if you update to LabWindows/CVI 2013 through NI Update Service. To install the patch manually, refer to the Drivers and Updates links that follow.

Issues Fixed in LabWindows/CVI 2013 f1: Run-Time Engine 

ID Description
422256 Changing the size of a graph in LabWindows/CVI 2013 moves the y-axis origin from zero to -5.6E-17.
425248 The LabWindows/CVI 2013 ActiveX API is slow compared to the LabWindows/CVI 2009 SP1 ActiveX API.
427093 The TDMS API leaks memory for each file that is opened and closed.
430756 Program crashes on exit after opening a default module with LoadExternalModule.


Issues Fixed in LabWindows/CVI 2013 f1: Application Development Environment

ID Description
428743 Passing float parameters to the sqrt function when compiler optimizations are enabled causes an undefined symbol linker error.
428345 Multiply defined symbol NULL_IMPORT_DESCRIPTOR linker errors occur when including import libraries from LabWindows/CVI 2012 or earlier in LabWindows/CVI 2013 and LoadExternalModule is enabled.
427670 The LabWindows/CVI compiler crashes when compiling a file in which two functions reference a global structure through implicit casts.
427092 The LabWindows/CVI compiler crashes when compiling a file in which a function references a global structure that was created in another function via a function call.
428270 LabWindows/CVI 2013 crashes when right-clicking a watch expression while it is being edited.
427730 Double precision is limited to five decimal places in the Variables window.
424745 Undefined symbol errors occur when using custom controls in the UI Editor operate mode.
Incorrect structure packing in the LabWindows/CVI 2013 compiler may result in compiler crashes or incorrect run-time errors.
424885 Pre-build steps cause no build steps to be executed when building with an external compiler.
423480 The LabWindows/CVI 2013 compiler imports functions from DLLs differently when calling the function and when storing it in a global variable.
422710 A function panel debugging error is generated by LabWindows/CVI 2012 for DLL projects when both version 2012 and version 2013 are installed.
426770 LabWindows/CVI may not find the correct #include file when including files through relative paths.
423491 LabWindows/CVI reports an incorrect run-time error when referencing a structure member in the initializer of a global variable.
422700 Attempting to build a LabWindows/CVI 2013 project whose path contains non-ASCII characters results in a build failure.
427089 The OpenMP library does not link with __stdcall.
429200 Decrementing a pointer generates a non-fatal run-time error out of bounds after compiling for 64-bit debug configurations.
424731 Build fails when the project is located on a network drive.
425889 LabWindows/CVI does not throw compiler errors when casting the left hand of an assignment to types which are fundamentally incompatible.
429203 Errors and warnings are not shown in the Build Output window when compiling a project on a network drive.
429548 LabWindows/CVI displays an error about file version macros when you build a release configuration of a project that uses precompiled headers and the distribution is set to auto-increment the file version.
430558 Struct member dereferencing using the -> syntax causes a fatal run-time error while building, when the structure is part of an array or the structure size in bytes is smaller than the size of the structure pointer.
430979 LabWindows/CVI 2013 gives incorrect run-time errors in 64-bit configurations when accessing array, pointer, and structure fields in structures passed as parameters to functions.
430578 GetExternalModuleAddr fails if an external module references a symbol from an import library without declaring it as a DLL import.

OpenMP library functions or certain Win32 API functions cannot be used in the Interactive Execution window.


Related Links: 
Drivers and Updates: LabWindows™/CVI™ 2013 f1 Patch 
Drivers and Updates: LabWindows™/CVI™ 2013 Run-Time Engine f1 Patch