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.
This document contains the LabWindows/CVI 9.0.x known issues that were discovered before and since the release of LabWindows/CVI 9.0.x. Not every issue known to NI will appear on this list; it is intended to only show the severe and more common issues that can be encountered.
The Known Issues for toolkits and modules can be found in the LabWindows/CVI Modules and Toolkits Known Issues document.
The Known Issues Document is divided into two separate tables appearing in two separate Developer Zone documents. The known issues in this document are organized by the category of issue, and sorted by the date the issue was added to the document. To view the issues organized by date, visit the document linked below:
Known Issues by Date
You can contact us through any of the normal support channels including phone, email, or the discussion forums. If you are contacting NI in regards to a specific issue, be sure to reference the ID number given in the document to the NI representative.
The following items are known issues in LabWindows/CVI 9.0.x Known Issues sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| .NET and ActiveX | ||||||
| 165495 Return | Installing an application that uses ActiveX controls to a clean machine might result in a runtime error. This issue can occur if the Microsoft Visual C++ 2005 runtime is not on the machine before installation of the LabWindows/CVI application. Workaround: Install the Microsoft Visual C++ 2005 SP1 redistributable package.
| |||||
| 174102 Return | Hidden LabWindows/CVI ActiveX Automation interface is visible in function panel tree The _CVIAutomationServerInterface node should not be used. Workaround: Regenerate the instrument using the per server option.
| |||||
| 204719 Return | Wrappers generated for the Microsoft.JScript .NET assembly will not compile. Workaround: Find all function parameters with the name small in the generated source and include files and rename the parameters to something like _small.
| |||||
| 217093 Return | LabWindows/CVI .NET components do not get installed if .NET 2.0 is installed. LabWindows/CVI requires only .NET 1.1 SP1 to operate correctly. Workaround: Install .NET 2.0 and repair the LabWindows/CVI installation.
| |||||
| 119213 Return | An exception can occur when inserting an image into a report created with WordReport.fp Workaround: N/A
| |||||
| 44669 4HK7LF7K Return | The WordRpt_SetHeader function might not always work as expected. Embedding pictures in a header does not work. Workaround: N/A
| |||||
| 283042 Return | A LabWindows/CVI ActiveX server can crash while shutting down if there are open client connections to the server. Workaround: N/A
| |||||
| 283065 Return | LabWindows/CVI cannot generate wrappers for .NET Framework 4.0 assemblies. The Create LabWindows/CVI .NET Controller dialog box cannot generate wrappers for .NET Framework 4.0 assemblies. When trying to create a wrapper for .NET Framework 4.0 assemblies, the error Error occurred while generating .NET controller code. The method or operation is not implemented. will be shown. Workaround: Paste the following XML into a file named cvi.exe.config. Place this file next to cvi.exe in the LabWindows/CVI directory. <?xml version="1.0"?> <configuration> <startup useLegacyV2RuntimeActivationPolicy="true"> <supportedRuntime version="v4.0"/> </startup> </configuration> After you've done this, restart LabWindows/CVI.
| |||||
| 299606 Return | The LabWindows/CVI ActiveX Controller Wizard does not display all registered ActiveX servers. Servers registered with paths of type REG_EXPAND_SZ are not listed. Workaround: Manually browse to the server object containing a type library.
| |||||
| 313299 Return | CVI_AppGetLinesFromFile returns a string with maximum length of INT16_MAX characters. The maximum puts too small of a limit on the amount of source code text that can be returned from a single call to CVI_AppGetLinesFromFile . Workaround: N/A
| |||||
| 361691 Return | The GetAllBreakpoints LabWindows/CVI ActiveX Server Interface function does not set numBreakpoints output parameter. The variable remains uninitialized after the function call if it was not initialized before. Workaround: Use the length of the breakpoint line numbers safearray output parameter.
| |||||
| 335556 Return | The Word Report WordRpt_GoToCell function will always go to the first column when used in a Microsoft Word 2007 file or later. Workaround: Load an existing file saved as a Word 97-2003 document. Or, use the WordRpt_WriteToCell function with an empty string instead of the WordRpt_GoToCell function.
| |||||
| 376796 Return | Creating an AppDomain in .NET using the mscorlib.fp library causes a System.OutOfMemoryException to be thrown. This issue occurs on Windows 8 or on a system with .NET 4.5 installed. Workaround: N/A
| |||||
| 345700 Return | The CA_InitActiveXThreadStyleForCurrentThread function return success even if it fails. If the CA_InitActiveXThreadStyleForCurrentThread function is called and the threading model is already set to a model different from what is specified by the threadStyle parameter, the function still returns 0, which indicates that it succeeded. In this case, the function fails to set the threading model. Workaround: N/A
| |||||
| Analysis | ||||||
| 140249 Return | NonLinearFitWithMaxIters may not return an error if performing the maximum number of iterations does not result in convergence. Workaround: N/A
| |||||
| 140913 Return | ThresholdPeakDetector has unexpected results when width is greater than 1. The peakIndices parameter will have one additional value that is not a peak while the numberOfPeakIndices parameter will contain the correct number of peaks. Workaround: Ignore the last value in the peakIndices parameter.
| |||||
| 156791 Return | Several Analysis Library function panels are incorrectly relying on AnalysisLibPowerOfTwo enum. No values were assigned in the enum, and the values the compiler assigns are incorrect. Workaround: Enter the actual power of two number and not the enum value.
| |||||
| 183434 Return | NonLinearFitWithMaxIters function does not return the best fit array when the maximum number of interations is exceeded. NonLinearFitWithMaxIters also does not return the mean squared error. Workaround: N/A
| |||||
| 247895 Return | The threshold parameter in MultipleToneInfo, MultipleToneSignal, CxMultipleToneInfo, and CxMultipleToneSignal does not always work. Tones can be returned with an amplitude higher than the specified threshold. Workaround: Manually filter the returned tones to exclude tones with an amplitude greater than the threshold.
| |||||
| 362123 Return | Gamma, GammaC, and Beta functions compute regularized form, which is not accurately described in help. The Gamma function actually computes the gamma function or the regularized incomplete gamma function. The GammaC function computes the regularized complimentary incomplete gamma function. The Beta function computes the beta function or the regularized incomplete beta function. Workaround: N/A
| |||||
| 361840 Return | For values of x that are very large, sin (x) returns x instead of returning a number between -1 and 1. This behavior occurs only for large values of x, such as 1e+20. Workaround: N/A
| |||||
| Compiler | ||||||
| 120676 Return | Even with C99 enabled, some variables cannot be declared immediately following a switch statement. Workaround: N/A
| |||||
| 127909 Return | Instrument drivers are marked for compilation with each configuration switch. Normally, LabWindows/CVI only marks for recompilation those files that do not already have up-to-date object files for the current configuration in the cvibuild folder. Instrument files are the one exception to this. Workaround: N/A
| |||||
| 128921 Return | Incorrect compilation of code containing multiple anonymous inner struct members. For instance, the elements of the bitfield of the following structure may not evaluate correctly: typedef struct { union { struct { unsigned short flag1 : 1; unsigned short dummy : 3; unsigned short flag2 : 4; unsigned short flag3 : 4; unsigned short dummy2 : 4; }; unsigned short all; } flags; } flagset; Workaround: N/A
| |||||
| 129546 Return | Cannot use the Utility or Formatting and I/O Libraries and some Interface to Win32 API functions at the same time. You can use one set of functions or the other but not both. The functions that conflict are the following: Formatting and I/O Library:
Workaround: N/A
| |||||
| 131800 Return | Too many initializers error when initializing incomplete array typedefs. Workaround: Replace the typedef type with the explicit incomplete array declaration.
| |||||
| 132689 Return | LabWindows/CVI autocomplete feature does not work for nested struct array fields. The following code demonstrates the problem: struct A { int a[10]; int b[10]; }; struct B { struct A sA[10]; int c; }; void main(void) { struct B sB[10]; int i, j; // BUG: Type the following and you will get completion for struct A. sB[i].sA. // BUG: Type the following and you will NOT get completion for struct A. sB[i].sA[j]. } Workaround: N/A
| |||||
| 134066 Return | Linking a project can fail with an Out of Memory error in very rare circumstances, Workaround: One workaround to try is adding a handful of empty functions to one of your source files. This will change the number of symbols in your final binary and mask the bug that causes this Out of Memory error.
| |||||
| 134406 Return | The Interface to Win32 API fails to compile with third-party compilers if C99 is enabled. Workaround: N/A
| |||||
| 134407 Return | Build warnings are reported when compiling the Interface to Win32 API with third-party compilers. These errors occur because LabWindows/CVI defines some pragmas that are specific to LabWindows/CVI in the Win32 API header files (basetsd.h and winnt.h). Compilers that do not recognize these pragmas report errors. Workaround: N/A
| |||||
| 135927 Return | ActiveX wrappers fail to compile when LabWindows/CVI uses the Borland compatibility mode. You may receive the link error Undefined symbol '_IID_IDispatch' referenced in "<module name>". Workaround: N/A
| |||||
| 136156 Return | When passing 64-bit integers to a 32-bit integer parameter in a function call, other parameters can end up with incorrect values. Workaround: N/A
| |||||
| 138186 Return | Function pointers for functions without parameters require void keyword in parameter list. Workaround: Instead of declaring a function pointer like this: typedef int (*FuncPtr)(); Declare it like this with the void keyword: typedef int (*FuncPtr)(void);
| |||||
| 139419 Return | Including WSPiApi.h and WS2tcpip.h can cause Interface to Win32 API compile errors. Workaround: N/A
| |||||
| 145895 Return | Auto completion of structs does not handle arrays of structs inside other structs correctly. Workaround: N/A
| |||||
| 152421 Return | The compiler can crash when very large arrays are initialized with small string literals. If you initialize a large char array with a small string literal like the following: char buf[500000] = ""; compilation may crash. Workaround: N/A
| |||||
| 152423 Return | Arrays initialized with string literals are not completely filled with zero bytes. If you initialize a char array with a smaller string literal such as the following: char buf[10] = ""; the bytes that are not explicitly initialized should be zero, but they are not. Workaround: N/A
| |||||
| 152425 Return | No error reported when arrays are initialized with string literals that are too large. Initializations such as the following: char A[3] = "hello"; should report an compile error, but they do not. Workaround: N/A
| |||||
| 158055 Return | Cannot include windows.h in the Interactive Execution window. Workaround: N/A
| |||||
| 162554 Return | The non-fatal runtime error "Local was referenced before being initialized" may occur incorrectly. The following code recreates this incorrect non-fatal runtime error: void foo (const void *buffer) {} void main() { struct { int x; double y; } buf[1]; buf[0].x = 0; buf[0].y = 0; foo(buf); } Workaround: Turn off Detect uninitialized local variables at run time in the Build Options dialog box.
| |||||
| 162814 Return | Cannot embed a type library in a DLL if the function panel has a custom data type. Workaround: N/A
| |||||
| 165697 Return | The last initialized global or static local variable in a file may not be fully allocated. This can occur only if the total storage of global or static variables exceeds 16384 bytes. Workaround: N/A
| |||||
| 168621 Return | Using an object file built with precompiled headers can lead to link errors. Using an object file built while the build configuration was set to Debug in a Release project can cause link errors. Debug symbols from the precompiled headers are added into the created .obj file. Workaround: Only build object files (Options»Create Object File) when the build configuration is set to Release.
| |||||
| 169037 Return | Linking against mixed-mode .NET DLLs may cause LabWindows/CVI applications to crash. Workaround: Dynamically load the entry points in the mixed-mode DLL using LoadLibrary and GetProcAddress.
| |||||
| 177794 Return | LabWindows/CVI can crash when compiling a complex mathematical computation that is not assigned to a variable. Workaround: N/A
| |||||
| 186965 Return | Compile.exe crashes on project with "Add type library resource to DLL" option enabled. Workaround: N/A
| |||||
| 201360 Return | Incorrect usage of designated initializers (C99) may result in a hang in the LabWindows/CVI environment during compilation. When compiling in debug mode, the following code snippet and others like it will hang the LabWindows/CVI environment. typedef struct { char *s; int b; } foo; // note the initialization of undeclared member a foo f = { .s = "bar", .a = 2, .b = 3 }; Workaround: N/A
| |||||
| 203051 Return | Some constant array size expressions may be incorrectly reported as variable-length in C99 mode. When building with C99 extensions enabled, size expressions involving the ternary conditional operator are treated as non-constant expressions. This can result in compiler errors reporting that a variable-length array has been illegally declared.. Workaround: Disable C99 extensions.
| |||||
| 206504 Return | Building debug versions of very large projects may cause LabWindows/CVI to run out of memory. Workaround: Right-click files that do not need to be debugged and select Enable 'O' Option. This option removes debugging information from the compiled object file, resulting in a much smaller memory footprint.
| |||||
| 222105 Return | Using XCOPY in a build step to copy a file over an existing file can break subsequent builds. Updating the command to specify the /Y option will not work until the cmd.exe and xcopy.exe processes have been manually stopped using the Task Manager. Workaround: Specify the /Y option to overwrite existing files without prompting.
| |||||
| 232139 Return | LabWindows/CVI can recompile a source file if the timestamp of a .obj file changes, but there has been no change to the corresponding source file. LabWindows/CVI should only check to make sure the timestamp on the .obj file is later than the corresponding source file. The current behavior can cause problems on high latency network drives, or if other programs, such as anti-virus programs, modify object files. Workaround: N/A
| |||||
| 232194 Return | LabWindows/CVI ignores invalid symbols in macro names. For example, LabWindows/CVI reports a duplicate macro definition for this code: #define a$aaa 10 #define a$bbb 20 LabWindows/CVI ignores the invalid symbol ($) and everything that follows it. Workaround: Do not use invalid symbols in macro names.
| |||||
| 232196 Return | LabWindows/CVI does not consider '$' to be a valid character in a symbol identifier. The C standard doesn't require that this character be supported, but some compilers do support it. Workaround: Do not use the '$' character in a symbol identifier.
| |||||
| 232258 Return | You cannot use word "defined" in a macro definition. For example, the following code will not compile: #define MY_MACRO defined(_CVI_) #if MY_MACRO int i; #endif Workaround: N/A
| |||||
| 237998 Return | Cannot link some uuid.lib symbols in a 32-bit program. Workaround: N/A
| |||||
| 240722 Return | Including strsafe.h causes compilation errors. Workaround: N/A
| |||||
| 284771 Return | When using third-party compilers, linker errors refer to temporary object files. If link errors are found for multiple modules, the link errors will all be reported in the same temporary object file. Workaround: N/A
| |||||
| 275934 Return | Including the http.h Win32 API header file can result in missing function prototype compile errors. If you have enabled the Require function prototypes option in the Build Options dialog box, including http.h can result in a missing function prototype compilation error. Workaround: If the function reported as missing a prototype does not take any parameters, ensure the keyword void is added to the parameter list in the function declaration.
| |||||
| 276524 Return | compile.exe may report link errors for National Instruments libraries. If the LabWindows/CVI development environment has not been launched, compile.exe might report link errors for some libraries, such as the LabWindows/CVI SQL Toolkit or the Programmer's Toolbox. Workaround: Run LabWindows/CVI before using compile.exe.
| |||||
| 277739 Return | Compiling a file with a syntax error can cause LabWindows/CVI to crash. A very specific type of syntax error can cause LabWindows/CVI to crash. For example, compiling a file that contains the following code will cause LabWindows/CVI to crash. void a(b, int c) { int d = b; } Workaround: Remove the syntax error before recompiling.
| |||||
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 309184 Return | compile.exe can crash when passed a project path that can't be found on disk. If you pass a .prj file and one or more .c files to compile.exe and the .prj file cannot be found on disk, compile.exe will crash. Workaround: Ensure the .prj file can be found.
| |||||
| 309627 Return | LabWindows/CVI can crash when compiling some K&R style functions. This crash occurs only if you disable the Require function prototypes option. For example, if you attempt to compile a file with the following code, LabWindows/CVI crashes. void foo (a) int a(enum {x,y}); { } Workaround: Enable the Require function prototypes option and add a prototype for the function.
| |||||
| 295246 Return | A source file containing a very large array of structures might fail to compile. For example, if you declare an array of 5000000 NIComplexNumber structures, LabWindows/CVI will fail to compile the file without any error message. Workaround: Either:
| |||||
| 327730 Return | LabWindows/CVI crashes during compilation when a very long variable name is used. Variables with names of roughly 500 characters or longer will cause LabWindows/CVI to crash when compiling. Workaround: N/A
| |||||
| 335358 Return | Using the bit shift operator multiple times on the same line of code produces incorrect results for 64-bit integers in a 32-bit application. This issue occurs when the result of one bit shift is used for another bit shift in the same line of code. For example: unsigned int a = 1, b = 62; unsigned long long result = 1ULL << a << b; Workaround: Separate the two bit shift operations into two separate lines of code.
| |||||
| 318253 Return | False positive user protection error when using an Interface to Win32 API struct. N/A Workaround: Refer to the Disabling User Protection section in the LabWindows/CVI Help. Access this section through the Table of Contents by selecting Programmer Reference»LabWindows/CVI Compiler Overview»User Protection»Disabling User Protection.
| |||||
| 363456 Return | Compiler warning when using __int64 in switch statement expression in a 32-bit configuration. "Warning: Conversion from '__int64' to 'long' might lose data" can occur if the switch expression is of type __int64 and all of the case expressions are of type int or long. The conversion does not actually occur and the warning can be ignored. Workaround: N/A
| |||||
| 359304 Return | The modulo operation with 64-bit integers in a 32-bit configuration may produce incorrect results. The result will likely be incorrect if the second operand is negative. Workaround: N/A
| |||||
| 368271 Return | When using an external optimizing compiler, compiler defines that are defined to strings with escaped quotations are not passed to the external compiler as strings. For example, adding the following define to the Compiler Defines section in the Build Options dialog box: /DMYDEFINE="\"abc def\"" sends the following define to the third-party compiler: /DMYDEFINE="abc def" Workaround: N/A
| |||||
| 404327 Return | LabWindows/CVI may crash when changing the default calling convention of a library after it has been built. Workaround: Re-open LabWindows/CVI and change the calling convention.
| |||||
| Debugging | ||||||
| 127318 Return | Calling some inifile.fp functions while the Programmer's Toolbox is compiled from source code can result in a false report of leaked resources. The temporary file ini$$0.tmp may be reported as a leaked resource. Workaround: N/A
| |||||
| 134586 Return | Erroneous user protection error when accessing member of a multidimensional array of structs/pointers. Workaround: Use one of the following workarounds:
| |||||
| 137735 Return | The Source Code Browser does not retain all its settings when a file is recompiled. You must browse to the variable again to see the correct display. Workaround: N/A
| |||||
| 139139 Return | Viewing memory as HEX longs (64-bit) in the Memory Display window causes all values to turn red. Workaround: N/A
| |||||
| 155604 Return | Adding a watch expression that references a variable declared in block scope can hang the program when it is debugged. Workaround: N/A
| |||||
| 177188 Return | LabWindows/CVI debugger can crash when using memcpy to copy data from a const struct array. Workaround: Remove the const keyword from the array declaration.
| |||||
| 179034 Return | Obtaining a non-existent attribute with CVIXMLGetAttributeByName results in a false report of leaked resources. Workaround: N/A
| |||||
| 184979 Return | Breakpoint pass counts are off by one. For a pass count of n, LabWindows/CVI breaks on the nth pass, instead of the nth + 1 pass. Workaround: N/A
| |||||
| 189661 Return | Variables window does not always show a variable declared in for-loop scope. Workaround: N/A
| |||||
| 217295 Return | AppendString might work incorrectly when debugging a LabWindows/CVI program. If you use toolbox.obj as the program file for the Programmer's Toolbox instrument, the debug information for the size of the pointer reallocated by AppendString will be incorrect, which may lead to errors from functions such as strlen. Workaround: Attach toolbox.c as the program file for the Programmer's Toolbox instrument.
| |||||
| 255342 Return | Remote debugging can hang when debugging DLLs with DllMain. Workaround: Move DllMain to a source code module that is not compiled with debug info.
| |||||
| 257782 Return | The Resource Tracking window does not track thread local variable handles. Workaround: N/A
| |||||
| 247337 Return | Watchpoints for nested structures may show incorrect values. The value displayed in a tooltip might also be incorrect. Workaround: View the value of the variable in the Variables window.
| |||||
| 285461 Return | Attaching the LabWindows/CVI debugger to a C++ DLL might result in significant performance degradation. If you are debugging a process that calls into a C++ DLL, significant performance degradation might occur. This performance degradation has occurred for C++ DLLs that throw many exceptions or create and destroy large STL maps. Workaround: There is no workaround while debugging, but there is no performance degradation while running outside of the LabWindows/CVI debugger.
| |||||
| 255345 Return | TDMS_CloseFile can take a long time to complete when the LabWindows/CVI debugger is attached. If your TDMS file contains many channels, a call to TDMS_CloseFile can take a very long time. The more channels you have, the longer the call can take. This occurs only when the LabWindows/CVI debugger is attached. This is related to Known Issue 285461. Workaround: N/A
| |||||
| 278151 Return | A breakpoint with a pass count and a condition will never break execution as a result of the pass count. If a breakpoint has both a condition and a pass count, the pass count will be ignored. As a result, if the condition is never met, the breakpoint will never break execution. Workaround: N/A
| |||||
| 298184 Return | Non-fatal user protection errors can sometimes display only the message &%%s&. This can happen when there is a mismatch in the release vs. debug build configuration between a LabWindows/CVI EXE and its DLLs. Workaround: Ensure all LabWindows/CVI binaries in a process are either in debug configuration or release configuration.
| |||||
| 294217 Return | The Edit Breakpoint dialog box incorrectly maintains a reference to old files. If you place breakpoints in one workspace and then debug a project, the source files those breakpoints were placed in will not be removed from the Edit Breakpoint dialog box when a new workspace is loaded. Workaround: N/A
| |||||
| 37498 44K3HK07 Return | Variables defined inside of a block statement cannot be added to the Watch window. For instance the variable a in the following code cannot be added to the Watch window. void foo (int var) if (var == 0) { int a; a = var; } } Workaround: N/A
| |||||
| 326213 Return | The Go to Line button causes an internal assert to be triggered. When execution is suspended on a breakpoint, pressing Go to Line in the Breakpoints dialog box for a breakpoint that has a valid location but an invalid condition causes an assert to be triggered. Workaround: N/A
| |||||
| 316246 Return | LabWindows/CVI changes foreground lock timeout to 0 when debugging. When debugging an application, the debugger changes the HKEY_CURRENT_USER\Control Panel\Desktop\ForegroundLockTimeout registry key to 0. This is necessary to control which window is in the foreground when debugging. The debugger should restore the registry key to its previous state when it is done debugging. Workaround: N/A
| |||||
| 322203 Return | If you change a breakpoint due to an invalid condition while you are debugging, LabWindows/CVI ignores the next breakpoint. If your code contains a breakpoint with an invalid condition followed by another invalid breakpoint (either with an invalid condition or set on a line containing no executable code), LabWindows/CVI displays the Invalid Condition dialog box for the first breakpoint. If you make the condition valid and click Replace or click Delete to delete the breakpoint, LabWindows/CVI ignores the next breakpoint. Workaround: N/A
| |||||
| 324351 Return | Canceling from the Invalid Breakpoint dialog box causes the LabWindows/CVI debugger to ignore all remaining breakpoints and continue execution. If you have a breakpoint with an invalid condition when you begin debugging, LabWindows/CVI displays the Invalid Condition dialog box for that breakpoint. However, if you click Cancel in this dialog box, LabWindows/CVI resumes execution of the program. All other breakpoints following this breakpoint will be skipped and debugging will continue. Workaround: N/A
| |||||
| 324829 Return | LabWindows/CVI crashes while debugging when adding a conditional breakpoint to the Interactive Execution window if the window doesn't contain any executable code. N/A Workaround: N/A
| |||||
| 325547 Return | Error message in the Invalid Condition dialog box may overflow text region. When debugging and a breakpoint with an invalid condition is hit, the Invalid Condition dialog box opens. Replacing the condition with a longer but still invalid condition causes the error message to be longer, but the dialog box does not expand to accomodate the longer message. Workaround: N/A
| |||||
| 333287 Return | Cursor does not change back to arrow after operating the splitter in the Watch Window while debugging. This occurs only when debugging an application and execution is not suspended. Similar behavior occurs for both the vertical and horizontal splitters. Workaround: N/A
| |||||
| 353320 Return | Attempting to edit a "??" entry in the Memory window causes an error. In LabWindows/CVI 2009 and earlier the error is "Cannot write to address <address*gt;" and then the ADE may crash. In LabWindows/CVI 2010 and later, the error is "A custom control callback has raised an exception" and the ADE does not crash. Workaround: N/A
| |||||
| 358560 Return | Function name is not reported in Break On Library Errors message. Workaround: N/A
| |||||
| 335983 Return | Tooltip for symbol values during debugging may appear on top of the editor's scrollbar. Workaround: N/A
| |||||
| 370519 Return | The LabWindows/CVI environment crashes when setting a string in the Array Display window to hexadecimal format while debugging a LabWindows/CVI application. Workaround: N/A
| |||||
| 378420 Return | The CNVGetFolders and CNVGetVariables functions return string arrays that show the incorrect number of elements while debugging. Workaround: N/A
| |||||
| Development Environment | ||||||
| 126050 Return | tmpdir registry value is not used when backing up files. The registry key HKLM\SOFTWARE\National Instruments\CVI\<version>\tmpdir should be able to specify what directory temporary files are saved in. However, this key is not used. Workaround: N/A
| |||||
| 127036 Return | LabWindows/CVI may display repeated save prompts if a project file path is made invalid. If files LabWindows/CVI is using are moved on disk while they are open in LabWindows/CVI, you may receive multiple prompts to save the files. Workaround: N/A
| |||||
| 127953 Return | Closing a workspace may not remove all the files associated with a workspace. Workaround: N/A
| |||||
| 129695 Return | LabWindows/CVI can crash on exit after TestStand executes code modules in an external instance of LabWindows/CVI. Workaround: N/A
| |||||
| 130204 Return | Multiple file search does not ignore invalid paths when searching only a specific set of files. When searching multiple files in LabWindows/CVI, if you choose not to search an entire folder by unchecking the Search in Folders checkbox, LabWindows/CVI still tries to validate the path in the dimmed Directory control. If that path is not valid, LabWindows/CVI does not proceed with the search. Workaround: N/A
| |||||
| 131218 Return | The Edit Item dialog box of a tree control shows an incorrect description of the image name. Workaround: N/A
| |||||
| 133845 Return | Table row labels cannot be sized when the column labels are not visible and vice-versa. Workaround: N/A
| |||||
| 134049 Return | User Interface Editor does not retain the awareness that it should save the .uir in an older format. If you override the .uir format when you save a .uir file, LabWindows/CVI does not remember this. Therefore, the next time you save the .uir file using <Ctrl-S>, it will use the default format instead. To continue saving in the different format you'll have to use the Save As option and manually change the ring selection each time. Workaround: N/A
| |||||
| 135900 Return | The Workspace window title bar does not show Aero transparency. Workaround: N/A
| |||||
| 136241 Return | Attempting to run code in a released Interactive Execution window runs the project instead. Pressing the Run arrow on the toolbar when the Interactive Execution window is released runs the currently active project instead of the code in the Interactive execution window. Workaround: Confine the Interactive Execution window.
| |||||
| 136293 Return | LabWindows/CVI can crash after removing from the workspace a project that uses a third party compiler. Workaround: N/A
| |||||
| 140209 Return | Cannot change coordinates of a control label in the User Interface Editor if the control is in a tab page. This bug occurs if you select only the control label and not the entire control. Workaround: Select the entire control to move the label.
| |||||
| 149012 Return | Cannot list ViInt64 attributes in function panels. Workaround: N/A
| |||||
| 154794 Return | Web links in the Help menu do not work when .html files are not associated with a Web browser. If .html files are not associated with a Web browser, but are instead associated with a program like notepad.exe, the links will not work. Workaround: N/A
| |||||
| 156166 Return | Cut Line does not work correctly with a collapsed block of code. The cursor will jump to the top of the source file, and the editor will not redraw for a period of time. Workaround: N/A
| |||||
| 156975 Return | The User Interface Editor prompts you to assign constant names when backing up files. If any of your controls, panels, menu bars, or menu items have a blank constant name, a dialog box displays every time the *.uir file is backed up. Workaround: Make sure all of your UI objects have constant names.
| |||||
| 157568 Return | Go to Next Reference does not cycle through all references of a variable or a function in other files. Workaround: N/A
| |||||
| 162197 Return | Help tooltip for the Run button in the toolbar is incorrect after running the Interactive Execution window. Workaround: N/A
| |||||
| 166027 Return | Launching the Icon Editor results in the error Value is invalid or out of range. Workaround: Load the icon editor project (samples\apps\iconedit\iconedit.prj), set the configuration to Release, and rebuild the project.
| |||||
| 168302 Return | Numeric float-type function panel controls cannot be added through automation. Workaround: Call FPGenSetParamDisplayFormat to set the correct display format for the control after creating the control but before inserting the function in the tree.
| |||||
| 168426 Return | Using an RT target originally configured by browsing the network can result in "The target machine is not connected to the network" errors. Workaround: Manually enter the IP address of the RT target instead of selecting it from the browse list.
| |||||
| 172750 Return | The LabWindows/CVI GUI Localization Utility preview does not work correctly with non-native character sets. If the .uir file is set to the Native character set, it will not correctly preview character sets other than the native character set. Workaround: N/A
| |||||
| 179291 Return | Labels for numeric slide controls do not redraw if the display format is set to Scientific or Engineering, and the data type is then changed to int64 or unsigned int64. If you try to operate the control in the LabWindows/CVI User Interface Editor while the label is not drawn, LabWindows/CVI may crash. Workaround: Set the desired data type before setting the format.
| |||||
| 182743 Return | Editing a panel that has a control with a label of exactly 50 characters can cause a crash. Workaround: Shorten or lengthen the control label.
| |||||
| 185942 Return | Cannot add empty function panel file to a project. Workaround: N/A
| |||||
| 189843 Return | The Perforce 2009.1 client may cause LabWindows/CVI 2009 to crash. LabWindows/CVI may crash when the Perforce SCC DLL is unloaded. Workaround: Upgrade to the Perforce 2009.2 client.
| |||||
| 193526 Return | Adding a watch expression that already exists fails silently. The existing watch expression should be made visible in this case. Workaround: N/A
| |||||
| 194053 Return | LabWindows/CVI can display multiple prompts to check out a project file from source code control. Workaround: N/A
| |||||
| 198012 Return | Dragging binary files, such as a static library, between projects may result in an exception. If this is done, LabWindows/CVI may confuse what files are in what projects. If this happens, save the current workspace and restart LabWindows/CVI. Workaround: Do not drag binary files between projects.
| |||||
| 201055 Return | Type library generation may fail if FP control names contain ODL keywords. When generating type libraries, FP control names are converted to lowercase, which causes problems for names such as "Auto" and "Register", which become ODL keywords "auto" and "register". Workaround: Modify the names of the FP controls.
| |||||
| 203337 Return | The DirectShow API in the full Interface to the Win32 SDK is unusable. This API requires multiple header files that are not included in the LabWindows/CVI installation. Workaround: N/A
| |||||
| 207820 Return | Modifying a menu bar font can hide elements of the Edit Menu Bar dialog box. If you change a menu bar font size to be very large, the Customize Font button will be hidden by the menu bar preview the next time you try to edit the menu bar. Workaround: N/A
| |||||
| 167925 Return | Workaround: N/A
| |||||
| 172157 Return | Diffing two files can cause window contents to draw in the wrong window. Workaround: N/A
| |||||
| 237395 Return | Dragging a file from the Open File dialog box to the LabWindows/CVI Project Tree can cause LabWindows/CVI to crash. Workaround: Open files through the Open button of the dialog box, not by dragging files from the dialog box to the Project Tree.
| |||||
| 258505 Return | Selecting "Create New File" on a project folder results in an invalid file. If you right-click a folder in a LabWindows/CVI project and select Create New File, you will not be able to create an Empty file. Workaround: N/A
| |||||
| 254788 Return | LabWindows/CVI doesn't remember source line position of the first file opened until a second file is opened. If you scroll down in the first file you open in LabWindows/CVI before you open another file and then close the first file and reopen it, the file will be scrolled back to the top of the file. Workaround: Open a second file.
| |||||
| 256142 Return | Copying collapsed tree items with images in the User Interface Editor can cause LabWindows/CVI to crash. Workaround: N/A
| |||||
| 252825 Return | The Variables window might flicker when debugging a DLL built using LabWindows/CVI. Workaround: N/A
| |||||
| 253907 Return | If Perforce is configured with two workspaces that have different root paths, Perforce SCC integration will fail in LabWindows/CVI. Workaround: Ensure all workspaces have the same root path.
| |||||
| 211495 Return | LabWindows/CVI function panel help is missing stylesheets and images in multibyte operating systems. Workaround: N/A
| |||||
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 240876 Return | Adding a space to the Menu bar constant prefix in the Edit Menu Bar dialog box causes the dialog box to close without warning. None of your changes will be applied. Workaround: N/A
| |||||
| 241552 Return | LabWindows/CVI does not support offline files in Windows Vista and Windows 7. If you do attempt to work with files in offline mode from LabWindows/CVI, your file might be deleted when you reconnect to the network. Workaround: N/A
| |||||
| 248824 Return | Using replace for a text selection may not always work. The replace operation will only miss replacements on the last line of a selection and only if earlier replacements on that line push later matches on that line outside the range of the original selection. However, the same issue can occur on any line in the selection if the selection is made in column selection mode. Workaround: N/A
| |||||
| 276026 Return | LabWindows/CVI can generate code into the wrong source file without asking for confirmation. The following steps will reproduce this issue:
Notice the callback and header files were placed in the unrelated example's source file. Workaround: Ensure you always have zero or at least 2 source files open when generating code.
| |||||
| 283527 Return | LabWindows/CVI carets ignore Windows keyboard settings. Through the Keyboard Settings applet in the Windows Control Panel, you can adjust the blink rate of the caret, or you can disable blinking altogether. LabWindows/CVI ignores this setting. Workaround: N/A
| |||||
| 283634 Return | The LabWindows/CVI Visual Studio Conversion Wizard fails for some projects that reference National Instruments modular instruments drivers. If the modular instruments driver references any files relative to IVI Standard Root, IVI Standard Root 64-bit, VXIPlug&Play 64-bit, or VXIPlug&Play kbase 64-bit, the LabWindows/CVI Conversion Wizard fails. Workaround: Open the LabWindows/CVI .prj file in a text editor and change entries that look like the following: Path Is Rel = True Path Rel To = "IVI Standard Root" Path Rel Path = "Drivers/niRFSG/niRFSG.fp" Path = "/c/Program Files/IVI/Drivers/niRFSG/niRFSG.fp" You should change to: Path Is Rel = False Path = "Full path to <niRFSG.fp>" Note that values in project files are limited to 82 characters (including the quotes), and if the path is going to exceed that amount, you'll need to split up the path into multiple lines.
| |||||
| 282253 Return | Data tooltip is too small to hold negative zero floating-point values. Workaround: N/A
| |||||
| 289949 Return | Using an import library generated by MinGW results in "Bad COFF Library Member Header" error message. Workaround: Open the header file that contains the function prototypes for the DLL in LabWindows/CVI. Then use the Options»Generate DLL Import Library menu item to generate an import library for the DLL.
| |||||
| 289314 Return | User-defined types always receive an asterisk when used as output types in function panels. For instance, if you define a custom type as typedef char[256] String255; you would not want it to have an asterisk appended to it when used as an output type. Workaround: N/A
| |||||
| 299674 Return | Pasting unicode text into the LabWindows/CVI Source window can cause LabWindows/CVI to crash. Workaround: N/A
| |||||
| 295507 Return | Undoing after hiding and showing panels can cause LabWindows/CVI to crash. The following steps will result in LabWindows/CVI crashing:
Workaround: N/A
| |||||
| 295654 Return | Building a project with the same name as a previously loaded project can cause LabWindows/CVI to crash. This crash can occur if you complete the following steps:
Workaround: N/A
| |||||
| 296380 Return | EVENT_SORT does not appear in the User Interface Editor. If you interactively sort tree items in the User Interface Editor, the only event that appears in the status bar is EVENT_GOT_FOCUS. EVENT_SORT does not appear. Workaround: N/A
| |||||
| 296381 Return | You cannot use the Edit Text Tool to edit the last cell in a table column. If you click <Enter> after editing the last cell, it looks as if the value that you entered has been committed, but if you change to operate mode, or if you click on a different cell, you'll notice that the changes have been lost. Workaround: Instead of clicking <Enter>, click a different cell instead. Or, use the Edit Table dialog box instead of the Edit Text Tool to enter values in edit mode.
| |||||
| 294281 Return | Making a change to a project that is under source code control in LabWindows/CVI does not result in checking out the project. LabWindows/CVI does not acknowledge that the project has been checked out after making a change. This means that you are unable to save the project. Workaround: Close and re-open the project. Then make your changes.
| |||||
| 294282 Return | Files added to a project cannot be added to source code control. When you add a file to a project under source code control (SCC), a dialog box will be shown asking if you want to add the file to SCC. If you select yes, you will be shown the file checkout dialog, but it is empty. Workaround: Close and re-open the project. Then add the file to SCC.
| |||||
| 294650 Return | Undo in the User Interface Editor can change the z-plane order of controls. Workaround: N/A
| |||||
| 294008 Return | New files added in the Edit Project dialog box do not use the Project Tree Font. If you use a non-standard font for the Project Tree Font and add files to a project in the Edit Project dialog box, the new files will be drawn with the wrong font. Workaround: N/A
| |||||
| 328823 Return | Toolbox.c and toolbox.h are not added to a Microsoft Visual Studio project if LabWindows/CVI is not run at least once after installation. N/A Workaround: N/A
| |||||
| 329035 Return | LabWindows/CVI Conversion Wizard does not transfer 'Compile with precompiled include file' setting to 'Precompiled Headers' setting in Microsoft Visual Studio. Workaround: N/A
| |||||
| 331534 Return | The scroll bars in the User Interface Editor do not appear when changing the panel size using the cursor. When you expands a panel to fill the User Interface Editor using the cursor and click the inside edge of the border of the panel, the panel border may be partially outside the editor. In this case the scroll bars do not appear and part of the panel is inaccessible. Workaround: Move the panel and the scroll bars will appear properly.
| |||||
| 332047 Return | LabWindows/CVI stops responding while searching for an inaccessible network location. When LabWindows/CVI is searching for a file at a network location that is not available, the environment stops responding. Workaround: The search times out after about 2 minutes and the environment will resume. Avoid attempts to access network locations that may not be available.
| |||||
| 311356 Return | Changes to the font persist in the Font dialog box when the action is canceled. If you make changes in the Font dialog box, but cancel your changes, the changes are not applied. However, if you open the Font dialog box again, the changes will still be active in the dialog box and will be applied if you then click OK. This behavior does not affect changes to the Source Window font. Workaround: N/A
| |||||
| 311364 Return | Function name displays twice in the function prototype tooltip when the return value is const or volatile. N/A Workaround: N/A
| |||||
| 316626 Return | The physdemo.cws example uses functionality that is removed with Security Update 5Q5FJ4QW. The physdemo.cws example is not installed with LabWindows/CVI 2010 SP1 or later. Workaround: N/A
| |||||
| 321793 Return | Adding multiple files with the same name in the Edit Project dialog box can cause LabWindows/CVI to crash. This behavior can occur if you use the Edit Project dialog box to add two files to the project with the same filename but different paths. When you select OK to confirm the changes, a warning will appear stating that a file with the same name already exists in the project. If you remove the duplicate file and click OK again, the development environment will crash. Workaround: N/A
| |||||
| 325813 Return | The Replace File in Project option crashes the development environment if a file with same base name is specified. Replacing a file in the Project Tree with another file that has the same base name using the Replace File in Project context menu option causes the development environment to crash. Workaround: N/A
| |||||
| 326195 Return | The active function panel is incorrectly detected when multiple function panels are being edited in the Function Panel Editor window. If you create multiple function panels in the Function Panel Editor and attempt to add a control to a panel other than the original, the control is not always added to the selected function panel. Workaround: Select the original function panel then the function panel that you want to create a control on before adding a control.
| |||||
| 334683 Return | The window number is displayed in the title bar of maximized windows when switching between tabbed and non-tabbed workspace. N/A Workaround: N/A
| |||||
| 332690 Return | The Source Window background is not painted gray when a non-tabbed workspace is opened. If the Show tabbed Workspace option is disabled and you open LabWindows/CVI, the background of the Source Window is painted partially white. Moving windows across the white region causes them to be painted gray. Workaround: N/A
| |||||
| 333571 Return | Moving selected text in the Source window and then undoing offsets the original cursor position. Selecting text and dragging it in a Source window moves the text to the new location. However, when this operation is undone, the input cursor is not restored to the correct location even though the text is still highlighted. Workaround: N/A
| |||||
| 333983 Return | Non project C files loaded by function panels are not unloaded when switching projects. When loading a project or switching the active project in a workspace, the function panels that were explicitly loaded by the previous project (not the dependency Function Panels) are unloaded, but the corresponding non project C files remain linked. Workaround: Restart LabWindows/CVI.
| |||||
| 334920 Return | Corners of Source Editor windows are painted black in non-tabbed Workspace when opened. When opening a workspace that has the Show Tabbed Workspace option disabled and at least one source code window open, the top corners of the Source Editor windows are painted black. Workaround: N/A
| |||||
| 335301 Return | Disabling tabbed workspace doesn't restore windows to their original unmaximized state. N/A Workaround: N/A
| |||||
| 335499 Return | Unmaximizing windows after loading a workspace leaves inactive windows without a number in front of the title in the title bar. N/A Workaround: N/A
| |||||
| 361327 Return | The CNVGetScalarDataValue function expects a char* only and not a char[ ] as described in the function help. Workaround: N/A
| |||||
| 361958 Return | The Project Tree does not auto-hide when a UIR file is opened. Other file types do auto-hide the Project Tree. This behavior occurs only if you enable the Auto hide Project Tree and Library Tree option in the Environment dialog box. Workaround: N/A
| |||||
| 354449 Return | Very long strings in the Edit Distributions dialog box may crash LabWindows/CVI. Many of the text fields in the Edit Distributions dialog boxes do not have string length limits. Strings that are too long for the field may cause the ADE to crash. Workaround: Limit the Application Name to 50 characters, the registry keys relative paths to 255 characters, and registry values to 2048 characters.
| |||||
| 347511 Return | Microsoft Visual Studio does not rebuild a LabWindows/CVI project if a UIR file changes but its header file does not. Workaround: N/A
| |||||
| 347986 Return | The Load UI resource file dialog box in the User Interface Localizer utility unloads the currently loaded localization. If changes have been made in the loaded file, a dialog box prompts you to save. Workaround: N/A
| |||||
| 352408 Return | Pressing F1 on a function in the ActiveX Library or most of the Tools Libraries does not open the LabWindows/CVI Help to the topic for the specified function. Workaround: N/A
| |||||
| 354450 Return | Using a very long string when setting the value of a variable in the Variables window may crash the LabWindows/CVI environment. Workaround: N/A
| |||||
| 354451 Return | A very long string value in the Add/Edit Tools Menu Item dialog box may crash LabWindows/CVI. Workaround: N/A
| |||||
| 354452 Return | A very long string value in the Project folder or File Folder option of the New Project from Template or New File from Template dialog boxes may crash LabWindows/CVI. Workaround: N/A
| |||||
| 337770 Return | Setting LabWindows/CVI to "Run as administrator" will open a new instance of LabWindows/CVI each time you open a file associated with LabWindows/CVI. Workaround: If you want to use LabWindows/CVI as administrator you can check the "Run as administrator" option from the Advanced button of the Shortcut tab instead of the Compatibility tab. You can access these options by right-clicking the LabWindows/CVI icon on your desktop and selecting Properties.
| |||||
| 333302 Return | Auto Backup will provide an error if the file is marked as read-only. This behavior is common if the file is stored in source control. Auto Backup may also take effect even if the file was not modified. Workaround: Disable Auto Backup in Environment Options.
| |||||
| 344947 Return | The LabWindows/CVI development environment crashes when you cut, copy, or delete a function panel tree item if it is the active item, but not selected. The active tree item has a dotted border around it but is not highlighted in blue. Workaround: N/A
| |||||
| 352775 Return | Sorting an empty column in the Modules window causes an error. The LabWindows/CVI environment will throw the "The index passed is out of range" error when a column is selected that has no items in it. This can happen when you are not debugging because the modules list is empty. Workaround: N/A
| |||||
| 315800 Return | The Find in files search will display a warning if a line it attempts to search is greater than 1024 characters. Lines greater than 1024 characters are truncated at 1024 characters and the rest of the line is not searched. The warning does not provide any information on which file is causing the problem. Workaround: N/A
| |||||
| 333273 Return | Using column selection mode in the Source window over a collapsed region of code will cause the region to be improperly selected. Workaround: N/A
| |||||
| 333324 Return | Function panel controls in a disabled function may not be dimmed when the function panel is reopened for editing. Workaround: N/A
| |||||
| 336446 Return | Entering more than 255 characters into the Line Label or Bus Label fields of the Edit Digital Graph dialog box will cause the LabWindows/CVI environment to crash. Workaround: N/A
| |||||
| 336721 Return | Switching the active application while a control is being moved by the mouse causes the selection outline to not be undrawn. This behavior occurs if you press <Alt-Tab> while dragging a control. Workaround: Minimize and then maximize the LabWindows/CVI environment to remove the drawing errors.
| |||||
| 338093 Return | Not moving the mouse when using Zoom to rectangle mode triggers EVENT_ZOOM with ZOOM_RESTORE for the eventdata1 parameter of the callback. Workaround: N/A
| |||||
| 341151 Return | Workspace folders with very long names can cause the LabWindows/CVI environment to crash when loading or saving. Workaround: Avoid workspace folder names with over 100 characters.
| |||||
| 373262 Return | The Ini_WriteToRegistry and Ini_ReadFromRegistry function panels incorrectly list OS compatibility as Windows 9x/NT/2000. Both functions are available in Windows XP and later. Workaround: N/A
| |||||
| 386081 Return | Items in the Resource Tracking window can be expanded only if they contain at least two items. The Expand Resource and Collapse Resource items of the Resource Tracking window context menu are dimmed unless the resource category has at least two items in it. Workaround: N/A
| |||||
| 369682 Return | Once the value of the File name field of the New File from Template dialog box is changed, the File path field does not change extension if the file type is changed. Workaround: N/A
| |||||
| 370519 Return | The LabWindows/CVI environment crashes when setting a string in the Array Display window to hexadecimal format while debugging a LabWindows/CVI application. Workaround: N/A
| |||||
| 371022 Return | The LabWindows/CVI environment crashes when entering a path instead of an IP address in the New Remote Debugging Target dialog box. Workaround: N/A
| |||||
| 388073 Return | The Show Prototype tooltip displays the help button for macros when the previous Show Prototype tooltip was for a function with help documentation. Workaround: N/A
| |||||
| 368470 Return | The wrong text is selected after dragging multiple lines of text in the Source window into the middle of another line of text. When multiple lines of text are dragged into another line of text, the text selection will extend to include characters that were not previously selected. Workaround: N/A
| |||||
| 386160 Return | Cannot load attribute info for a .fp file when the associated .sub file is encoded as Unicode. Workaround:
| |||||
| 387331 Return | Clearing a window in the Output Region causes the item to be dimmed in the Window menu. If a window is cleared using the Clear Window option in the context menu, the item is dimmed in the Window menu and cannot be re-opened if closed. Workaround: N/A
| |||||
| 391055 Return | Auto indent does not place the cursor in the correct location when pressing the Enter key after a break in a switch statement. Inside a switch statement, when you press the Enter key following a break; statement, you most likely want to start a new case statement, which should be indented one level less than the break statement. However, LabWindows/CVI auto indent starts the new line at the same level as the break statement. Workaround: N/A
| |||||
| 392932 Return | Documentation generated for variadic functions does not display variable parameter in function prototype. Workaround: N/A
| |||||
| 399264 Return | The Find command may miss some search matches if the Whole word option is enabled. Workaround: N/A
| |||||
| 403645 Return | LabWindows/CVI might crash when declaring a variable for the Attribute Value parameter of some attribute accessor functions. For example if you use the Declare Variable option to declare a variable for the last parameter of the Ivi_GetAttributeViBoolean function, LabWindows/CVI will crash. This issue occurs only for functions where there is a parameter in between the attributeID and the attributeValue parameters. Workaround: N/A
| |||||
| 407329 Return | Selecting Rebuild from the Batch Build dialog box causes a memory leak. Workaround: N/A
| |||||
| 408295 Return | Source files with several while loops may cause LabWindows/CVI to hang while scrolling the source file. Workaround: N/A
| |||||
| 408324 Return | LabWindows/CVI will crash when you click the selection button for a ring control while editing a function panel. The selection button should not be displayed while the function panel is in edit mode. In some cases, the button will appear in edit mode, and LabWindows/CVI will crash if it is clicked. Workaround: N/A
| |||||
| Hardware | ||||||
| 142035 Return | Some LabWindows/CVI GPIB functions return positive values if the GPIB driver is not installed. The functions this bug affects are ibdev, OpenDev, CloseDev, and CloseInstrDevs. If the GPIB driver is not installed, these functions should return negative values according to the documentation, but instead they return 0x8000 (the ibsta value indicating that an error occurred). Workaround: You can workaround this by checking if the return value is 0x8000 (ERR), and if so, check the value of iberr. You can also ignore the return value and check if ibsta has the ERR bit set after the function returns.
| |||||
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 171624 Return | CPU usage can spike when using ComRdTerm. Workaround: Set the timeout to zero using SetComTime and poll until the termination byte occurs.
| |||||
| 201013 Return | OpenComConfig does not return an error if the configuration parameters are invalid. Workaround: N/A
| |||||
| 201130 Return | Calling OpenComConfig with an input queue size greater than 40960 bytes results in unexpected behavior on Windows. An input queue size greater than 40960 bytes causes an error in the Windows serial driver, leading to the port being opened with default settings. LabWindows/CVI does not return an error when this happens. Workaround: Do not use an input queue size that is greater than 40960 bytes
| |||||
| Installer | ||||||
| 128084 Return | Uninstalling LabWindows/CVI from Windows Vista does not completely remove context menu file associations. Workaround: N/A
| |||||
| 149929 Return | Workaround: N/A
| |||||
| 177971 Return | Creating an installer spec file fails if a Microsoft Visual Studio 2008 wizard is explicitly included Creating new spec file by passing the /generateSpecFile flag to setup.exe will not allow you to finish if you explicitly select Microsoft Visual Studio 2008 integration. Workaround: Manually modify the spec file located in the support files directory of the installation media.
| |||||
| 334574 Return | Installing multiple versions of LabWindows/CVI on the same system can cause the wrong versions of the LabWindows/CVI Help to be associated with the development environment. N/A Workaround: N/A
| |||||
| Performance | ||||||
| 129094 Return | Asynchronous timer limited to intervals no greater than approximately 429 seconds. Workaround: Split intervals of greater than 429 seconds into smaller intervals.
| |||||
| 129812 Return | Calling a LabVIEW-built DLL causes the printf family of functions to format a double to a string incorrectly. A string that should appear as 36010.000MHZ may instead appear as 3600:.000MHZ. Workaround: N/A
| |||||
| 139658 Return | GetFileSize can crash if you pass a path that is too long. Workaround: Make sure the file path size is less than 260 bytes before calling this function.
| |||||
| 144368 Return | strtod and scanf can crash in multithreaded applications. Workaround: Use locks from the Utility Library around every call to strtod or to the scanf family of functions.
| |||||
| 144640 Return | LabWindows/CVI MAX_PATHNAME_LEN is more restrictive than Windows ANSI path limitation in multibyte systems. Workaround: N/A
| |||||
| 144806 Return | CmtWaitForThreadPoolFunctionCompletion can hang in some rare circumstances. Workaround: N/A
| |||||
| 155155 Return | If you enable the Compile with precompiled include file option, LabWindows/CVI may occasionally crash when you view data tooltips during debugging. Workaround: Disable precompiled headers.
| |||||
| 157141 Return | A memory leak occurs in the thread-safe queue. Workaround: The leak does not occur under release builds.
| |||||
| 162398 Return | Toolbox lists can grow by amounts greater than the allocation policy specifies. N/A Workaround: Change the definition of NUMITEMSPERALLOC in toolbox.c from #define NUMITEMSPERALLOC(list) Max(((*list)->listSize * ((*list)->percentIncrease + 100)) / 100 , (*list)->minNumItemsIncrease) to #define NUMITEMSPERALLOC(list) Max(((*list)->listSize * ((*list)->percentIncrease + 100)) / 100 - (*list)->listSize, (*list)->minNumItemsIncrease)
| |||||
| 167239 Return | LabWindows/CVI can hang while editing a large non-source code data file. Workaround: Waiting long enough will often resolve the hang.
| |||||
| 175150 Return | LabWindows/CVI can crash when opening a .c file containing lines with exactly 1020 characters. Workaround: Do not create source files with lines exactly 1020 characters long.
| |||||
| 182036 Return | CreateUDPChannelConfig fails if ws2_32.dll is installed to the application directory. Workaround: Remove ws2_32.dll from the application directory after making sure it resides in one of the other system paths.
| |||||
| 184428 Return | LabWindows/CVI applications can crash when calling the Delay function from multiple threads. Workaround: Use the Sleep function from the Interface to the Win32 API.
| |||||
| 191778 Return | Passing NULL to the Data_Buffer or Data_Length parameters of RegEnumerateValue results in a General Protection Fault. Workaround: N/A
| |||||
| 191841 Return | Matrix operations that use the Intel MKL on Windows have slight numerical differences between LabWindows/CVI 2009 and previous versions of LabWindows/CVI. LabWindows/CVI 2009 uses the latest version of the Intel Math Kernel Library (MKL) to accelerate linear algebra operations under the Windows operating system. Some functions in the Intel MKL return minor differences in the result than previous versions of MKL due to higher optimization, causing slight numerical differences between results in functions in LabWindows/CVI 2009 and previous versions of LabWindows/CVI. This issue affects Vector and Matrix Algebra, Statistics, and Curve Fitting functions in LabWindows/CVI. Workaround: N/A
| |||||
| 196430 Return | Large static arrays declared in a block scope can cause a stack overflow if Detect uninitialized local variables at run time is selected. Workaround: Disable the Detect uninitialized local variables at run time option in the Build Options dialog box.
| |||||
| 197427 Return | NIReport_GetPrinters has a small memory leak. Each time the function NIReport_GetPrinters is called, a small amount of memory is leaked. The size of the leak depends on the number of installed printers and the length of the printer names. Workaround: N/A
| |||||
| 201259 Return | Calling RegisterWinMsgCallback and UnRegisterWinMsgCallback from multiple threads may result in a crash. Workaround: Synchronize via locks or critical sections calls to both RegisterWinMsgCallback and UnregisterWinMsgCallback.
| |||||
| 215744 Return | Calling CNVData functions in network variable callbacks can cause hangs. Calling any of the CNVData functions in network variable callbacks may result in a hang if multiple threads are writing through a single shared CNVWriter object. Workaround: Call the function PostDeferredCallToThread immediately upon entering a network variable callback. Construct a data structure to pass all the necessary elements to the callback routine to be executed on the main thread.
| |||||
| 41414 4DDCC0IO Return | A small memory leak exists in network variable creation. Explicitly creating network variables results in a memory leak of approximately 50 bytes per variable that is created. Workaround: Consider using implicitly created network variables if you are creating and deleting numerous network variables over a long period of time.
| |||||
| 218499 Return | Calling GetTCPPeerName with an invalid handle can cause the application to hang. Workaround: N/A
| |||||
| 233510 Return | Ini_GetInt64 doesn't return 5021 (Invalid integer) for numbers greater than LLONG_MAX. Instead of returning an error, the function succeeds and returns LLONG_MAX. Workaround: N/A
| |||||
| 256901 Return | Passing a pointer to a custom data type to a function that takes a void * will leak memory in a debug build. LabWindows/CVI user protection leaks memory when a pointer to a user defined data type is passed to a function with a void * parameter. An example of this would be calling the function ListInsertItem and passing a pointer to a user defined data type to the PointerToItem parameter. Workaround: Disable user protection, or build the program in a Release configuration.
| |||||
| 258354 Return | CNVProcessIsRunning may incorrectly report that the process is running if the program is run as a startup program. CNVProcessIsRunning checks only if the process is configured to run when the Variable Engine is started. In most cases, this check is a good indicator of whether the process is running because the Variable Engine--a Windows service that automatically starts when Windows starts--loads all the processes configured to run. Workaround: Try to browse to the process using the functions in the Browser Functions class of the Network Variable Library. If you are able to browse to the process using CNVBrowse, the process is running. The following code is an example of browsing to a process: CNVBrowser browser; CNVCreateBrowser(&browser); CNVBrowse("\\\\localhost\\your-process-name"); CNVDisposeBrowser(browser);
| |||||
| 253304 Return | TDMS Files with very high channel counts might be slow to open. Workaround: N/A
| |||||
| 246218 Return | The numElements parameter of the DefineThreadSafeArrayVar macro is not expression-tolerant. Workaround: Wrap your expression in parentheses when calling DefineThreadSafeArrayVar.
| |||||
| 285443 Return | The run-time movable custom control (movectrl.fp) leaks memory. Workaround: N/A
| |||||
| 290737 Return | InetSendMail can crash if the "To:" field exceeds 250 bytes. Workaround: If the "To:" field is longer than 250 bytes because you need to email multiple people, call the InetSendMail function multiple times so that the "To:" field doesn't exceed 250 bytes.
| |||||
| 298456 Return | A program that has called EnableDragAndDrop might crash if closed from the Windows taskbar. Workaround: N/A
| |||||
| 292992 Return | Users cannot completely disallow creating directories in FileSelectPopup and DirSelectPopup. If you pass 0 as the AllowMakeDirectory parameter of FileSelectPopup or DirSelectPopup, the icon for creating a folder is not present in the dialog box. However, users can still right-click the file list and select New»Folder. Workaround: N/A
| |||||
| 314876 Return | The LabWindows/CVI Run-Time Engine can hang when calling CloseCVIRTE in a secondary thread. The CloseCVIRTE function can cause a hang if called from a thread other than the main thread. Workaround: N/A
| |||||
| 335299 Return | Multiple calls to ClipboardPutBitmap in a multithreaded application causes temporary hang. Calling the ClipboardPutBitmap function from a thread other than the main thread can cause a temporary hang. Workaround: N/A
| |||||
| 356348 Return | Using the TCP Library from multiple threads may cause a deadlock when combined with locks in the user's TCP callbacks. Workaround: N/A
| |||||
| 339884 Return | When allocating memory with malloc, LabWindows/CVI will truncate the memory allocated to be an integer multiple of the size of the pointer data type. You cannot allocate a large memory block and then manually split it into smaller blocks. If you do, you may receive run-time errors. Workaround: N/A
| |||||
| 355436 Return | The InetTelnetOpen function limits connections to 100. If you exceed this limit, a non-fatal run-time error occurs. Workaround: N/A
| |||||
| 343157 Return | Calling the GetFileAttrs function with an improperly formed path and a non-existent drive may cause a crash. Calling GetFileAttrs function with z:\test.txt as input for the first parameter will cause a crash. This is because there should be two slashes in the path string and because the z drive does not exist. Workaround: Using two slashes will prevent the application from crashing.
| |||||
| 390072 Return | A memory leak occurs in the FileBrowser_GetSelectedFiles function when no files are selected or an error occurs Workaround: The source code for this library is installed with LabWindows/CVI and can be edited by a user.
| |||||
| 397059 Return | The GetMonitor functions fail if the monitor configuration changes. When the monitor configuration of the system changes (e.g. unplugging a monitor from a system with multiple monitors), GetMonitorFromPoint, GetMonitorFromRect, and GetMonitorFromPanel always return a value of 1 for the monitor ID. Workaround: N/A
| |||||
| Stand-Alone Applications and Distributions | ||||||
| 130423 Return | The .NET Library cannot be included in a distribution without also including the full run-time engine. You also cannot install the .NET Library if you are privately installing the LabWindows/CVI Run-Time Engine. Workaround: N/A
| |||||
| 131196 Return | The Import Measurement & Automation Explorer (MAX) Configuration File checkbox is always checked on the Advanced tab of the Edit Installer dialog box. This happens when reloading the distribution settings from a .cds file. As long as the config file path is empty, the build behavior is not actually affected. Workaround: N/A
| |||||
| 137318 Return | Adding dependencies of an executable to the Installation Files & Directories section in the Edit Installer dialog box displays two copies of the DLL. Workaround: Re-open the Edit Installer dialog box.
| |||||
| 141434 Return | LabWindows/CVI crashes when unloading a workspace with an ActiveX server project after building a distribution. Workaround: N/A
| |||||
| 154605 Return | Projects with a relative path for the application file can crash when configuring a distribution. Workaround: Ensure that the Target Settings dialog box specifies a full, absolute path for the project output file rather than just a filename. Specifically check the Release configuration.
| |||||
| 182036 Return | CreateUDPChannelConfig fails if ws2_32.dll is installed to the application directory. Workaround: Remove ws2_32.dll from the application directory after making sure it resides in one of the other system paths.
| |||||
| 186565 Return | LabWindows/CVI distributions cannot install fonts on Windows Vista or Windows 7. Workaround: N/A
| |||||
| 292521 Return | An application whose installer includes only the "Network Variable Support" sub-item might run slower than expected on a minimally configured target computer. Under this scenario, the components necessary for LogosXT are not installed. Workaround: Distribute the entire LabWindows/CVI Run-Time Engine.
| |||||
| 292805 Return | An application whose installer includes only the "Network Variable Support" sub-item might not run correctly on a minimally configured target computer. Workaround: Distribute the entire LabWindows/CVI Run-Time Engine.
| |||||
| 312179 Return | Some Microsoft DLLs are automatically included in distributions built with LabWindows/CVI. Some Microsoft dependencies are operating system dependent and should not be included in distributions. These dependencies typically already exist on most targets. If not, then they should be installed from a Microsoft distribution. Workaround: N/A
| |||||
| 316361 Return | The LabWindows/CVI low-level support driver CVINTDRV.sys contains a security vulnerability. Refer to Does National Instruments Security Update 5Q5FJ4QW Affect Me? for more details. Workaround: N/A
| |||||
| 354481 Return | User specified icons are not displayed in Windows Explorer for larger sizes in Windows Vista/7. In certain situations, the icon displayed may be a cached icon rather than the icon you have specified. Workaround: Remove the cached icon.
| |||||
| 369355 Return | Applications that use the DIAdem Connectivity Library that are installed using a distribution built in LabWindows/CVI might generate run-time errors related to the Microsoft Visual C++ 2005 run-time not being installed. This issue occurs with distributions that include the DIAdem Connectivity Library support by selecting the NI USI component in the Edit Installers dialog box, but do not include the full LabWindows/CVI Run-Time Engine. Workaround: Either include the full LabWindows/CVI Run-Time Engine in the distribution, or download and install the Microsoft Visual C++ 2005 Redistributable package from the Microsoft website.
| |||||
| 369915 Return | Creating a distribution for a project that uses the DataSocket Library does not automatically check the NI DataSocket 5.0 option in the Drivers & Components tab of the Edit Installer dialog box. Workaround: N/A
| |||||
| 384581 Return | The GetExternalModuleAddrEx function fails to load a DLL if it is not in the current working directory or the system path. If you load a import library that is located in a different path using the LoadExternalModuleEx function, the GetExternalModuleAddrEx function will not be able to locate the DLL if it is in the same path as the import library. Workaround: Make sure the DLL is in a directory where the system can locate it (e.g., the current working directory or the system path).
| |||||
| 396825 Return | The default value for the Publisher option on General tab of the Edit Installers dialog box is "%company". This value is not evaluated and the publisher appears as "%company". Workaround: N/A
| |||||
| User Interface | ||||||
| 101593 Return | Strip chart scroll bar overlaps the plot area. Workaround: N/A
| |||||
| 126708 Return | PlotArc lacks accuracy for drawing a small angle with a large radius. Workaround: N/A
| |||||
| 129832 Return | Editing multiple controls changes tab order and z-plane order. Workaround: N/A
| |||||
| 131102 Return | On Windows Vista, file selection dialog boxes add an extra backslash (\) character when selecting a file at the root of a volume. Workaround: N/A
| |||||
| 131413 Return | After widening the inc/dec arrows, the entire area of the arrows is not clickable. This bug will only manifest itself if the left edge of the control label does not extend all the way to the left edge of the inc/dec arrows. Workaround: If a label is not needed for the control, the user can add a label and then move it off screen programmatically using the ATTR_LABEL_LEFT and ATTR_LABEL_TOP attributes. The idea is to move it up and left far enough that it always is off screen, thereby ensuring the label always extends past the left edge of the inc/dec arrows.
| |||||
| 134165 Return | Menu bar does not resize when using the Scale Contents On Resize or Resolution Adjustment options. Workaround: N/A
| |||||
| 135032 Return | Checkerboard dimming of controls is leaving label text etched. The system attribute ATTR_USE_CHECKERBOARD_DIMMING was introduced to restore the LabWindows/CVI 7.1 control dimming behavior. However, because the label text remained etched, it did not fully restore the LabWindows/CVI 7.1 control dimming behavior. Workaround: N/A
| |||||
| 135264 Return | The Done button can disappear when you resize a file selection dialog box. Workaround: Size the file selection dialog until the Done button shows.
| |||||
| 136678 Return | Menu events cause a crash if there is no menu callback specified and the application has a main callback. Workaround: Create and use an empty callback function for the popup menu items.
| |||||
| 138050 Return | The Remove All button in the multi-file selection dialog box is missing a corner. Workaround: Resize the dialog box to display the missing corner.
| |||||
| 139151 Return | Debugger does not always catch incorrect use of ATTR_COPY_ORIGINAL_DATA. If ATTR_COPY_ORIGINAL_DATA is set to 0 and the data buffer is deallocated before the graph control is done using it, a program may crash without any explanation from the debugger. Workaround: N/A
| |||||
| 139269 Return | Hidden tab pages of a nested tab control can be made active. Controls with tooltips can cause hidden tab pages to display if the hidden tab page was the last active tab. Workaround: N/A
| |||||
| 140926 Return | Changing the axis range on a LabWindows/CVI graph plot with few points causes skewed plot lines. Due to rounding errors, as points move further off screen, the plot lines become less accurate. Workaround: Provide more points for your plot, or constrain the range of the graph in question.
| |||||
| 143075 Return | Table and tree controls do not scale proportionally to other controls. The Scale Contents On Resize option does not work correctly with table and tree controls. Workaround: N/A
| |||||
| 145322 Return | Graph y-axis name not drawn correctly after graph changes position before being displayed. Workaround: After resizing the panel, but before displaying it, add the following code: SetCtrlAttribute (panelHandle, PANEL_GRAPH, ATTR_FIXED_PLOT_AREA, 1); SetCtrlAttribute (panelHandle, PANEL_GRAPH, ATTR_FIXED_PLOT_AREA, 0); This code should have no discernible effect other than making sure that the y-axis name is visible once you display the panel.
| |||||
| 147737 Return | Numeric markers do not always adjust correctly to the resizing of a slide control. If you readjust the size of a numeric slide while the markers or ticks are not visible, the markers or ticks will be drawn in the wrong location when you make them visible. Workaround: N/A
| |||||
| 149350 Return | The cursor position of a text box control can be incorrect when typing Thai characters. Workaround: N/A
| |||||
| 151308 Return | Passing '.' or '..' to the DefaultFileSpec parameter of FileSelectPopup causes a legacy file dialog box to be shown. Workaround: N/A
| |||||
| 154911 Return | Setting ATTR_INCDEC_WIDTH on numeric controls has no effect if the inc/dec arrows are not visible. Workaround: Show the inc/dec arrows, set the width, and then hide the arrows.
| |||||
| 173952 Return | Truncating tree item strings can cause user applications to crash under some circumstances. This issue can occur when a string is truncated from three characters to the first character followed by .... For example, a problem could occur if the string 123 was truncated to 1.... Workaround: Ensure room for at least 4 characters in any tree string.
| |||||
| 175118 Return | Minor gridlines of graph controls and minor ticks of numeric slide controls can disappear. Enabling the reverse axis option on the y-axis of a strip chart or graph can cause this to happen. Workaround: N/A
| |||||
| 177284 Return | Table and tree scroll bars are not always clipped to a child panel's bounds. Workaround: N/A
| |||||
| 183301 Return | Splitter controls with no range limit do not draw shadow when operated. Workaround: N/A
| |||||
| 189247 Return | Drag and drop operation on the title bar or window frame does not work. Workaround: Change the line that reads if (!S_DragQueryPoint ((HANDLE)(*pwParam), &mousePoint, &sdkRetVal) && sdkRetVal) in the function DragAndDropCallback in toolbox.c to read if (!S_DragQueryPoint ((HANDLE)(*pwParam), &mousePoint, &sdkRetVal)) instead.
| |||||
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 189400 Return | Loading a very wide .bmp or .pcx file can fail with an Out of Memory error. Workaround: N/A
| |||||
| 190831 Return | ATTR_NO_EDIT_TEXT allows tab spaces to be entered into a text box control. Workaround: Swallow the appropriate key press events.
| |||||
| 193088 Return | If a LabWindows/CVI popup panel is not active, subsequent popup panels may appear behind the original popup panel. This issue only occurs on Windows 7/Vista. Workaround: N/A
| |||||
| 193403 Return | The panel attribute ATTR_MOVABLE does not work with Aero enabled on Windows 7/Vista. Workaround: N/A
| |||||
| 194174 Return | Bitmaps with alpha channels, such as .PNG images, do not print correctly. The images on picture button controls become very small when they are printed. Workaround: N/A
| |||||
| 194970 Return | Using string controls with right or center justification causes the cursor to appear in the wrong position when there are trailing spaces Workaround: N/A
| |||||
| 197797 Return | The strip chart cannot plot more than INT_MAX points. The strip chart appears to hang after plotting INT_MAX points. Workaround: N/A
| |||||
| 216830 Return | Loading a panel with an ActiveX control in a thread other than the main thread will fail. The error NON-FATAL RUN-TIME ERROR: Library function error (return value == -143 [0xffffff71]). ActiveX control error may be thrown on calls to LoadPanel. Workaround: Load the panel in the main thread.
| |||||
| 243203 Return | LabWindows/CVI file dialog boxes cannot open files accessed through the Libraries button on Windows 7. Windows 7 introduced the Libraries button to the common file dialog boxes. LabWindows/CVI cannot open files that have been accessed by browsing through this button. Workaround: Do not browse to files with the Libraries button.
| |||||
| 231945 Return | SetCtrlVal does not immediately redraw an LED to the new state. Workaround: Add a call to ProcessDrawEvents after calls to SetCtrlVal.
| |||||
| 217094 Return | EVENT_MOUSE_POINTER_MOVE can nest until the stack overflows if ProcessSystemEvents is called from the event callback. Workaround: Do not call ProcessSystemEvents globally for a callback function or when handling EVENT_MOUSE_POINTER_MOVE.
| |||||
| 225134 Return | Bitmaps obtained with the GetCtrlDisplayBitmap function cannot be used as menu images. Workaround: N/A
| |||||
| 237405 Return | The event EVENT_LEFT_CLICK_UP can be sent to a panel behind a modal dialog box. Workaround: Set a flag so that you do not handle EVENT_LEFT_CLICK_UP while a modal dialog box is present.
| |||||
| 238634 Return | ActiveX controls aren't dimmed when ATTR_DIMMED is set to True. Workaround: N/A
| |||||
| 256995 Return | Deleting a tree item after hovering over it may generate a first chance exception. When you hover over a tree item, the LabWindows/CVI Run-Time Engine creates a timer that waits for one second before displaying a tooltip for the tree item. If the tree item is deleted before one second elapses, a first chance exception will be thrown when the timer code tries to access the deleted tree item. Workaround: Ignore the exception. It will be handled internally by the LabWindows/CVI Run-Time Engine
| |||||
| 255807 Return | When manually sizing a panel with a text box, the error message "The attribute passed is not valid" may be displayed. Workaround: Set the ATTR_EXTRA_LINES attribute of the text box to -1 or to a very large value.
| |||||
| 255934 Return | Fonts may not scale correctly when using the panel option Scale Contents on Resize. This problem is most evident when the scaling of the panel does not preserve the original aspect ratio. Workaround: Enforce the original aspect ratio by handling the EVENT_PANEL_SIZING event and calling the functions GetPanelEventRect and SetPanelEventRect.
| |||||
| 256628 Return | In some cases, a ring control can display a menu that doesn't completely fit on the screen. Workaround: N/A
| |||||
| 250654 Return | A strip chart that has been scrolled prints as if it were not scrolled. When printing a strip chart with PrintPanel or PrintCtrl, the strip chart will be printed without scrolling. Workaround: N/A
| |||||
| 252100 Return | The quality of images with transparency may deteriorate with repeated opening and closing of the associated UIR. Workaround: N/A
| |||||
| 253696 Return | Printing images with transparent backgrounds does not work correctly. The transparent part of an image will be rendered as white when calling PrintPanel or PrintCtrl on a control with an image that contains transparency. Workaround: N/A
| |||||
| 248368 Return | Hidden table rows and columns can still be clicked on, making them reappear temporarily. Workaround: N/A
| |||||
| 286276 Return | The frame of the increment and decrement buttons on numeric controls may not draw entirely. When using Windows visual styles, the top portion of the frame of the increment button or the bottom portion of the frame of the decrement button may not be drawn depending on the font that is used. Workaround: Slightly alter the font size or font face you are using.
| |||||
| 284842 Return | The GetTableCellRangeVals and SetTableCellRangeVals functions do not work for string cell types in a 64-bit application. Workaround: Set the value of each cell individually with SetTableCellVal.
| |||||
| 276442 Return | Displaying a file select popup panel from a panel with a tab control might disrupt the panel z-plane order. If a panel has both a tab control and child panels, and the child panels overlap the tab control, the child panel can be overlapped by the tab control after displaying a file select popup panel or a directory select popup panel. Workaround: N/A
| |||||
| 276443 Return | A tab inserted anywhere but the end of the list will use the wrong image. A tab that is inserted into a tab control at any position but the end of the list will result in the new tab using the image from tab that is in the next position. For example, if a tab control has three tabs, inserting a tab into the second position will cause the new tab to use the same image as the now third tab. Workaround: N/A
| |||||
| 276799 Return | Numeric table cells do not coerce values when values are pasted from the clipboard. If a table cell or range of cells is not in edit mode when a value is pasted from the clipboard, the cell will not coerce the value to the specified minimum or maximum values. Workaround: N/A
| |||||
| 281082 Return | A strip chart legend may not be drawn correctly if it overlaps the strip chart plot area. If a strip chart legend overlaps the plot area for the strip chart it is associated with, the legend will not redraw correctly if its visibility is toggled. Workaround: Place a transparent control on top of the strip chart's plot area.
| |||||
| 281083 Return | The y-axis name of a strip chart control might be drawn incorrectly when the y-axis autoscales. When the data on a strip chart causes the y-axis to autoscale, the y-axis name may be drawn incorrectly. Workaround: Do not enable autoscaling for the strip chart.
| |||||
| 288389 Return | The splitter control can disappear after is it dragged. This issue occurs only on Windows 7 or Windows Vista with Aero enabled. Workaround: Create a callback function for your splitter controls. In the EVENT_DROPPED case, hide the control, delay for a short amount of time, and then display the control. For example, adding the following code to the EVENT_DROPPED case of the splitter callback function should cause the splitter to display whenever it is dropped. SetCtrlAttribute (panelHandle, PANEL_SPLITTER, ATTR_VISIBLE, 0); Delay (.02); SetCtrlAttribute (panelHandle, PANEL_SPLITTER, ATTR_VISIBLE, 1);
| |||||
| 302494 Return | Memory is leaked when calling GetScaledCtrlDisplayBitmap on graph control with ATTR_COPY_ORIGINAL_DATA set to 0. Workaround: Complete the following steps:
| |||||
| 303637 Return | Scrolling strip charts can have inaccurate values for min and max due to rounding errors. For example, if your strip chart displays 100 points and you plot 100 points at a time, the end values may end with a value other than 99. Workaround: N/A
| |||||
| 303721 Return | Table row and column header separators do not line up with the row and column marker lines when Windows visual styles are enabled. In Windows 7, the row lines do not match up. In Windows XP, the column lines do not match up. Workaround: Disable Windows visual styles for controls.
| |||||
| 304541 Return | The Run-Time Movable Control (movectrl.fp) custom control does not display a hand when moving numeric controls. Normally, when moving a control by using the movable control custom control, a hand is displayed as the mouse cursor. However, an I-beam cursor is displayed for numeric controls. Workaround: N/A
| |||||
| 305258 Return | GetScaledCtrlDisplayBitmap can hang for some scaling ratios. For instance, scaling a graph from 400x801 pixels to 200x200 pixels will cause a hang. Workaround: Modify the scaling factor until the hang does not occur.
| |||||
| 306560 Return | VAL_SIZE_TO_PICTURE can significantly degrade the resolution of pictures if the pictures must shrink. Workaround: N/A
| |||||
| 298632 Return | Full ticks are not consistently drawn for many numeric controls. When full ticks are enabled for numeric slides, knobs, gauges, dials, or meters, some full ticks will be drawn darker than others. This is because the full ticks are drawn multiple times at once, leading to darkening because of the alpha blending done by ClearType. Workaround: Disable ClearType.
| |||||
| 299688 Return | Some items in the LabWindows/CVI status bar require a double-click to toggle, while others require a single-click. Workaround: N/A
| |||||
| 293672 Return | Some user interface controls do not draw Windows styles on mouse-over. For example, the following controls and control parts should display as a highlighted blue on Windows Vista and later, but do not:
Workaround: N/A
| |||||
| 293859 Return | The Floating Style attribute of a child panel can cause displayed panels to display as modal behind other displayed panels. Workaround: Change the Floating Style panel attribute of all child panels to Never.
| |||||
| 294159 Return | <Ctrl-Left Arrow> and <Ctrl-Right Arrow> do not work correctly in text controls on multibyte versions of Windows. The text cursor does not correctly move to work breaks. Workaround: N/A
| |||||
| 292070 Return | Passing TRUE to the RestrictDirectory parameter of FileSelectPopup does not completely restrict the directory to the initial directory. The user can select files from other directories by entering the path directly into the File Name control and by selecting a file from the previously selected files drop-down list. Workaround: N/A
| |||||
| 37666 3TJ0IB7K Return | Panels displayed with ATTR_WINDOW_ZOOM set to VAL_MAXIMIZE will not restore after showing the desktop. You can show the desktop by pressing <Windows Key-D> or by selecting the Show Desktop button on the task bar. Workaround: Call SetPanelAttribute with ATTR_WINDOW_ZOOM after calling DisplayPanel.
| |||||
| 328679 Return | Graph legend items are highlighted after calling RecallPanelState under some conditions. This behavior can occur even if the ATTR_LEGEND_INTERACTIVE attribute is disabled. Workaround: N/A
| |||||
| 329406 Return | LabWindows/CVI crashes when setting the Offset option for a graph if the Absolute Time Display Format is set to a very large number. N/A Workaround: N/A
| |||||
| 329461 Return | Printing UIR files resizes the table control in the print output. N/A Workaround: N/A
| |||||
| 326106 Return | If you save UIR files as older versions, LabWindows/CVI does not warn you that features that are unsupported in that version will not be saved. When saving a UIR file as an older version, LabWindows/CVI does not warn you that some features that were not supported in that version will not be saved. These features cannot be saved because they did not exist in that version. Workaround: N/A
| |||||
| 313512 Return | Ring control label/value pairs precision does not persist when changed. When the precision of a double or float label/value pair is modified in the User Interface Editor, the precision attribute is restored to its original value when the Edit Label/Value Pairs dialog box is opened again. Workaround: This behavior occurs only if there is only 1 label/value pair. Multiple label/value pairs persist the precision attribute. If you want only 1 label/value pair, add a second label/value pair and then change the precision attribute. Close the Edit Label/Value Pairs dialog box by clicking OK. Return to the Edit Label/Value Pairs dialog box and remove the second label/value pair. The precision attribute will now persist this value.
| |||||
| 314106 Return | The x-axis of the digital graph displays improper divisions. Large digital graphs with engineering or scientific display format set for the x-axis may display divisions and division labels that are inconsistent with other display formats. Workaround: N/A
| |||||
| 310781 Return | The table control displays a gap between the table cells and the bottom and right edges of the control when resized. This is an effect of the control's 3D style and not a bug. Future versions will allow the frame to be made invisible with the ATTR_FRAME_VISIBLE attribute. Workaround: Disable the Use Windows Visual Styles for Controls option for the panel.
| |||||
| 311281 Return | Graph controls display the x-axis name at an angle if you set the ATTR_XYNAME_FONT attribute to a metafont that rotates text. The graph should not display fonts that specify an angle of rotation for text for the x-axis name. Workaround: N/A
| |||||
| 312398 Return | Deleting all lines from a text box control with no lines available to delete causes a nonfatal runtime error. Passing -1 for the Number of Lines parameter of the DeleteTextBoxLines function deletes all lines from the index to the end. However, if there are no lines after the index, a nonfatal runtime error will occur. Workaround: N/A
| |||||
| 313765 Return | The LabWindows/CVI Run-Time Engine may crash when unloading a DLL that contains a panel in a thread other than the main thread. N/A Workaround: N/A
| |||||
| 314344 Return | Changing the panel title from a different thread can cause a hang. Changing the panel title from a thread other than the thread that the panel was created in can cause a hang. Workaround: N/A
| |||||
| 316365 Return | Panel toolbars are not fully discarded when created and discarded in a thread other than main. Calling the Toolbar_Discard function in a thread other than the main thread will cause a Non-Fatal Run-Time Error to occur when exiting the main function. Workaround: The error can be ignored because it only occurs when the application is exiting. Call SetBreakOnLibraryErrors (0) as the last statement in the main function to hide this error.
| |||||
| 318200 Return | The Edit Tabbing Order dialog box does not allow you to modify the tabbing order of controls that are behind overlapping controls. N/A Workaround: N/A
| |||||
| 319561 Return | SetCursorAttribute does not return an error when passed an annotation attribute. The SetCursorAttribute function will attempt to set an attribute that does not exist and can produce undefined errors. Workaround: Do not pass annotation attributes to SetCursorAttribute.
| |||||
| 322979 Return | Drawing a filled shape on the canvas with a pen width greater than 1 causes the filling to exceed the shape's border. When the pen width for a canvas is greater than 1 and you specify VAL_DRAW_FRAME_AND_INTERIOR as the Draw Mode for the draw function, the filling will exceed the shape's border. Workaround: N/A
| |||||
| 329376 Return | The graph legend does not always match the angle of text plots. The angle of the text in the sample plot of the graph legend may or may not match the angle of the text plot. Different behavior is demonstrated for various angles, font sizes, and fonts. Some conditions may cause the sample plot to display an underlined font when the plot does not use an underlined font. Workaround: N/A
| |||||
| 329411 Return | User interface control labels appear to resize when switching from Windows XP to Windows Vista or Windows 7. The font size of the labels actually remains the same, but the rendering of the labels is handled differently in Windows XP than it is in Windows Vista and Windows 7. The larger label size causes the controls to resize. Workaround: For the labels, disable the Size to text option in the Label Appearance section of the Edit Control dialog box.
| |||||
| 333163 Return | The Choose Date/Time Value dialog box displays an error message for an invalid date three times. If you enter an invalid date, such as Febuary 31, in the Choose Date/Time Value dialog box, LabWindows/CVI closes the dialog box and its parent dialog boxes and displays an error message stating Value is invalid or out of range three times. Workaround: N/A
| |||||
| 334681 Return | Setting the Label text in the Edit Tree dialog box to a string greater then 250 characters can crash LabWindows/CVI. N/A Workaround: N/A
| |||||
| 329405 Return | Numeric control radix does not resize with control text size. N/A Workaround: N/A
| |||||
| 345272 Return | Tree control may crash when more than 200,000 items are inserted. Workaround: N/A
| |||||
| 363056 Return | Floating point format in UI controls allows too many digits before automatically switching to scientific format. The floating point representation may show more digits than are represented by the underlying data. Workaround: Use scientific format if you may need to display very large numbers.
| |||||
| 337950 Return | Graph zoom selection box leaves artifacts if a control is moved over the drawing region in between frames. If a control is moved over the graph's drawing region while creating a zoom selection box, the control may interfere with the drawing of the selection box and leave traces of where the selection box once was. Workaround: N/A
| |||||
| 345703 Return | Some controls do not print colors correctly in bitmap printing when set to black & white mode. Workaround: N/A
| |||||
| 347056 Return | Dragging the ring tank control value to change its fluid height at run-time may cause black lines to appear where the previous fluid height was. Workaround: N/A
| |||||
| 347323 Return | Changing digital graph line label and bus label programmatically does not update the control labels if the plot does not contain any data. Workaround: N/A
| |||||
| 349832 Return | The mouse wheel scrolls the wrong control while ring control menu is displayed. This behavior occurs if the focus is still on a different control when the ring drop-down menu is opened. Workaround: N/A
| |||||
| 350412 Return | In some cases, the EVENT_LOST_FOCUS and EVENT_COMMIT events are not displayed in Operate mode when changing focus away from controls. Workaround: N/A
| |||||
| 350752 Return | A tree item tooltip continues to display when the cursor is over a tree item and another active window is in front of part of the tree item. Workaround: N/A
| |||||
| 350944 Return | The numeric control cannot have a transparent background. Workaround: N/A
| |||||
| 345074 Return | Passing an incorrect panel attribute to the GetPanelAttribute function causes a general protection fault. For example, passing ATTR_LABEL_TEXT to the GetPanelAttribute function will cause a crash because it is not a valid attribute of a panel. Workaround: N/A
| |||||
| 346432 Return | Child panels in a tab control do not resize when the tab is resized and Scale Contents on Resize is enabled. Workaround: N/A
| |||||
| 347326 Return | The digital graph control does not limit the Line Label and Bus Label values string size to 255 characters. Workaround: N/A
| |||||
| 348756 Return | The CVI GUI Localization Utility will not advance to the Right Y Axis of strip charts if the Next button is clicked. Workaround: Select the Right Y Axis item with the mouse.
| |||||
| 349930 Return | Mouse tracking is not aborted during a mouse click event if the control callback causes the panel to lose focus. For example, a string control handles the EVENT_LEFT_DOUBLE_CLICK event and during the callback the panel loses focus by displaying a popup dialog. When the popup dialog is closed, the mouse will continue to highlight the string control text. Workaround: N/A
| |||||
| 350416 Return | ExcelRpt_WriteDataFromTableControl function does not support combo box, ring, or button cell types. Picture cell types are also not supported, but Microsoft Excel does not have an equivalent cell type to accept the conversion. Workaround: N/A
| |||||
| 290770 Return | Popup dialogs appear in the same location where they were located the last time the dialog appeared in that process. The file dialog will appear centered in the monitor of the active panel the first time a process with this name is executed. From this point on, it will remember where you have moved it and it will always appear in that same location. Workaround: N/A
| |||||
| 309845 Return | Tree control tooltip does not use the character set of the tree. Hovering over an item with the mouse shows a tooltip with the item label if the label is longer than the visible area of tree control. That tooltip uses the native character set instead of the character set specified for the tree control. Workaround: N/A
| |||||
| 336312 Return | Calling the GetCtrlVal function for the picture ring control may cause an "Assertion failed" error in the Event Viewer if the picture ring data type is set to " string (char *)". Workaround: Use "int" as the data type for the picture ring control then use an enum or switch statement to reference the desired string.
| |||||
| 337804 Return | Changing the label of a tree item from the Label control or the Quick Edit Window does not update the corresponding entry in the Default Index option for that tree item. Workaround: N/A
| |||||
| 341569 Return | The index counts in the Default index option can have the wrong value if items are inserted in the tree out of order. Workaround: N/A
| |||||
| 343989 Return | Some Programmer's Toolbox functions do not support Lab Style controls. The SizeRingCtrlToText, ConformCtrlBitmapToPanel, and RecessAllCtrlFrames functions do not support Lab Style controls. Workaround: N/A
| |||||
| 352509 Return | ATTR_XLOOSE_FIT_AUTOSCALING_UNIT attribute does not work well with log scales. This attribute allows you to specify the base 10 logarithm of the loose fit factor. By the nature of a log scale, the same factor cannot be used for both the minimum and maximum value of the scale. Workaround: N/A
| |||||
| 373393 Return | Classic-style decoration controls that have rounded edges appear speckled. Some of the pixels of the edges display as transparent instead of the specified color. Workaround: N/A
| |||||
| 379530 Return | Opening a UIR file containing a tab control attached to a splitter control that is saved in LabWindows/CVI 7.1 causes an "Invalid control ID" error. The example project events.prj contains events.uir, which will cause this error if saved in LabWindows/CVI 7.1. Workaround: N/A
| |||||
| 379767 Return | UIR files saved in LabWindows/CVI 8.1 and earlier that contain a knob, dial, gauge, or meter can corrupt the environment memory when opened in LabWindows/CVI 8.5 or later. The memory corruption may cause the LabWindows/CVI environment to crash. Workaround: N/A
| |||||
| 388199 Return | Passing the same index for the Item Index and the Relative Index parameters of the AreTreeItemsRelated function returns the incorrect value for some relationships. If the Item Index and the Relative Index parameters are the same, the function should always return 0 indicating that they are not related through the specified relationship. However, the function returns 1 for the Sibling and All relationships. Workaround: N/A
| |||||
| 275954 Return | Setting the ATTR_FIRST_VISIBLE_LINE attribute does not cause a text box control to redraw in some cases. If the first visible line is partially shown and this same line is set for the ATTR_FIRST_VISIBLE_LINE attribute, then it will not cause the text box control to redraw. The first visible line can be only partially shown if the text box control is scrolled using the scroll bar. Workaround: N/A
| |||||
| 386878 Return | The DisplayImageFile function uses more memory than is necessary. The function might use up to four times as much memory as the size of the file. Workaround: N/A
| |||||
| 391657 Return | The value of the eventData1 parameter is always 1 in a callback for an EVENT_COMMIT event of a graph cursor that is locked. Workaround: N/A
| |||||
| 392640 Return | Cannot duplicate panels with controls that are duplicated and attached to a splitter control. You will receive error -153: "Item is already attached to splitter control." Workaround: N/A
| |||||
| 396304 Return | LabWindows/CVI might crash when running out of memory during a table copy operation. Workaround: N/A
| |||||
| 403028 Return | Changing the value of ATTR_INTERPOLATE_PIXELS can leave the plot with extraneous data. Workaround: N/A
| |||||
| 413695 Return | Radial controls do not resize all elements proportionally. Some controls will not scale all elements proportionally when the Scale Contents On Resize panel option is enabled and they are resized. Radial controls such as the gauge, meter, and knob must maintain a consistent aspect ratio for the radial portion of the control. However, this is not necessary for some elements of the control such as the label. These elements will not be scaled the same. This can cause elements to become misaligned or overlap. Workaround: Use the splitter control to resize controls rather than the Scale Contents On Resize option. Refer to the docking.cws example for details on how to accomplish this with splitter controls.
|
Document last updated on 8/1/2013