This document contains the LabWindows/CVI 2015 known issues that were discovered before and since the release of LabWindows/CVI 2015. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.
Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community.
Each known issue includes these fields:
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 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. Visit the NI Website to contact us. 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 2015 sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| .NET and ActiveX | ||||||
| 44669 4HK7LF7K Return | The WordRpt_SetHeader function might not always work as expected. Embedding pictures in a header does not work. Workaround: N/A
| |||||
| 284293 Return | Using a WebBrowser ActiveX control from a thread created in a LabWindows/CVI thread pool leaks memory. Threads from a LabWindows/CVI thread pool, run using CmtScheduleThreadPoolFunction, will leak memory if they host a panel that displays a WebBrowser ActiveX control. Workaround: N/A
| |||||
| 348295 Return | A panel containing an ActiveX control disappears when the mouse hovers over the control if the titlebar is not visible. Workaround: If the control has a windowless mode, use the windowless mode.
| |||||
| 148778 Return | The ActiveX Controller Wizard does not support LONGLONG and ULONGLONG data types. Workaround: Add the methods containing int64 parameters manually to the generated files.
| |||||
| 363992 Return | The first letter of exported functions in type libraries has inconsistent case behavior. Workaround: N/A
| |||||
| 426545 Return | Creating an ActiveX Controller for a large type library, such as the Microsoft HTML Object Library, results in the message Maximum number of function tree nodes exceeded. LabWindows/CVI is unresponsive while the ActiveX Controller Wizard generates the code, and the message appears after some time. Workaround: Two ways to reduce the number of function panels:
| |||||
| Analysis | ||||||
| 306163 Return | The PeakDetector function does not recognize peaks of a sine wave when the sampling rate is very high. If the peak is relatively flat because of the high number of points acquired at the high sampling rate, the PeakDetector function may not find the peaks. Workaround: N/A
| |||||
| Compiler | ||||||
| 237998 Return | Cannot link some uuid.lib symbols in a 32-bit program. Workaround: N/A
| |||||
| 291945 Return | Compiling a very large array in debug mode can be very slow. For instance, compilation of the following code in debug mode would be very slow: char *bigarray[30][25][1000][100]; int main (int argc, char *argv[]) { return 0; } Workaround: Change the Debugging level option (Options»Build Options) to No run-time checking.
| |||||
| 335405 Return | Cannot link some odbccp32.lib symbols in a 32-bit program. The issue exists with the odbccp32.lib that is included in the Windows 7 SDK. Workaround: Use odbccp32.lib from the Windows Vista SDK instead.
| |||||
| 457821 Return | Including datasize.h and windows.h causes a typedef redefinition with different types error for the INT8 type definition. Workaround: Modify datasize.h by commenting out the following line: typedef char INT8;, which is line 104 by default.
| |||||
| 412591 Return | Building a project that has a long file path causes LabWindows/CVI to crash. Previous versions of LabWindows/CVI display a Filename is too long message instead of crashing. Workaround: N/A
| |||||
| 422103 Return | Some large source files take much longer to compile in LabWindows/CVI 2013. The following is true of the new LabWindows/CVI 2013 compiler:
Workaround: N/A
| |||||
| 424254 Return | Calling the assert macro generates a warning that code will never be executed when the LabWindows/CVI compiler can determine the outcome of the expression. If the compiler can determine a condition will always have the same outcome, it will return this warning. Workaround: N/A
| |||||
| 430785 Return | Compiling causes an error: definition of the macro '_TARGET_FILE_VERSION_' conflicts with the definition used to build the precompiled header message. This error can occur when using the auto-increment version feature in projects that include precompiled headers. A similar error occurs for _TARGET_PRODUCT_VERSION_. Workaround: Do a rebuild instead of a build, after modifying a file that does not trigger the compilation of the precompiled header.
| |||||
| 471567 Return | Generating HTML help from source with array pointer type parameters results in an 'unknown' type generated in the help. The following function declaration causes this type of error: static int func(double (*dataArray)[4]); Workaround:
| |||||
| 505265 Return | The FileExists function may fail in projects that use the Vision Builder AI engine. A File Not Found error may occur when the FindFile function is used in a project that uses functions from the Vision Builder AI engine. Workaround: Avoid using the FindFile function in a project which uses the Vision Builder AI engine. If it is necessary to use the FindFile function, it will be necessary to separate these two functions into separate projects. For example, the application could be implemented as two separate executables which communicate using shared variables.
| |||||
| 516928 Return | Including a library (.lib), possibly of an old format, in both the project tree and the LoadExternalModule (LEM) Options dialog causes the following error: error: Input file is not a valid archive. Workaround: Check a library in the LEM Add Files to Executable dialog only if you intend to use it later with LEM functionality (e.g., using GetExternalModuleAddr).
| |||||
| 522704 Return | The build system incorrectly skips the compilation of a C file, if both the C file and an included H file have unsaved changes. The problem can be described with the following steps:
Workaround: Use the rebuild feature to rebuild the project.
| |||||
| 533493 Return | The build system does not handle function panel (FP) auto-load list dependencies when building projects that are not the active project. This can lead to undefined symbol errors for functions defined in the auto-loaded FPs, not explicitly referenced in the project. Workaround: Include all FPs manually in the project instead of relying on the auto-load list.
| |||||
| 539474 Return | I am unable to compile code with binary constants (0b prefixed numbers). Compilation fails with a binary integer literals are a GNU extension message. Workaround: Specify numbers using a different format such as decimal or hexagonal.
| |||||
| 540675 Return | Some extensions that caused compiler warnings in previous versions now cause compiler errors. Workaround: N/A
| |||||
| 541058 Return | The compiler returns an error when compiling code that uses the C99 _Complex data type. While the _Complex data type is only partially supported in previous versions and causes the compiler to issue a warning, the new behavior prevents code from compiling. Workaround: N/A
| |||||
| 706577 Return | Casting a double variable to a float produces unexpected results if compiled in 64-bit release mode with no optimizations. Casting a double to a float in an application compiled in 64-bit release mode with no optimizations can result in unexpected behavior. The value assigned to the float may be completely different from the original double value. It may also result in a stack overflow. Workaround: N/A
| |||||
| Debugging | ||||||
| 210086 Return | The LabWindows/CVI environment may hang while debugging with the Variables or Watch windows open. Workaround: N/A
| |||||
| 335983 Return | Tooltip for symbol values during debugging may appear on top of the editor's scrollbar. Workaround: N/A
| |||||
| 346034 Return | #define macros cannot be monitored in the Watch window. If you define a watch expression for a macro, the Watch window will show ERROR: Unknown identifier and type at run time. Workaround: N/A
| |||||
| 370682 Return | When the cvidebug.exe process dies or is intentionally stopped, LabWindows/CVI cannot debug again until it has been restarted. Each time you debug you receive a dialog box stating An unspecified error has occurred, probably due to corrupted data. Workaround: Restart LabWindows/CVI.
| |||||
| 423739 Return | The DefineThreadSafeVar macro produces a warning indicating it will never be executed. Workaround: This is an incorrect warning that can be ignored.
| |||||
| 438870 Return | Using the debugger to change the value of one variable in an anonymous nested structure changes it for all the variables in the structure with that name. Workaround: Name the nested structures.
| |||||
| 438896 Return | LabWindows/CVI does not display a warning message when both a main and a WinMain entry point are defined in a source file. When main and WinMain are both defined in a source file, only the WinMain entry point will execute at run time. LabWindows/CVI does not warn that main may not execute. Workaround: N/A
| |||||
| 442184 Return | Interface to Win32 API functions cannot be run in the Interactive Execution window. Linker errors occur when Interface to Win32 API functions are used. Workaround: Complete the following steps to work around this issue:
| |||||
| 456208 Return | The Source Code Browser window displays the same reference to a macro multiple times. Workaround: N/A
| |||||
| 460794 Return | The Available Types dialog box in the Watch and Variables and Call Stack windows do not display the full list of types. The list contains only types that are referenced in the application. Workaround: If the type you want is not in the list, you can create a Watch Expression that casts the value to the type you want. For example, if you want to interpret variable foo as an unsigned char, and unsigned char is not in the list, you can create a Watch Expression for (unsigned char)foo.
| |||||
| 460799 Return | The Watch and Variables and Call Stack windows display the type incorrectly after using the Interpret As option multiple times. If you interpret an int as a char and then interpret it as an unsigned int, the window will show the type as unsigned int (char (int)). The window should show the type as unsigned int (int). Workaround: N/A
| |||||
| 461757 Return | The Break On Change state of a watch expression is lost when stopping and restarting execution or unloading and reloading a workspace. Workaround: N/A
| |||||
| 464146 Return | Setting a breakpoint from Breakpoints dialog box on an invalid line while debugging an application causes uncommitted changes in the dialog box to irreversibly take effect. Workaround: N/A
| |||||
| 464507 Return | Running the Interactive Execution window a second time after finishing a run of the interactive statements with the Finish Function option causes the Interactive Execution window to crash. Workaround: N/A
| |||||
| 464904 Return | The Watch and Variables and Call Stack windows do not mark the item for a pointer to a variable as red if the variable value changes. Workaround: N/A
| |||||
| 430376 Return | The Variables and Call Stack, Watch, and Array Display windows do not show the contents of char arrays with more than 252 unprintable characters. Workaround: N/A
| |||||
| 434406 Return | LabWindows/CVI no longer displays a warning while debugging a real-time application if threads are still running on the target when RTmain exits. Workaround: N/A
| |||||
| 437356 Return | Stepping over a function call located at the last line in the enclosing lexical scope causes a Step Into instead of a Step Over. Workaround: Make sure the last statement is not on the same line as the closing curly brace.
| |||||
| 438839 Return | LabWindows/CVI displays incorrect or no values for CmtThreadLockHandle and CmtTSQHandle variables when the variables are declared as int. Workaround: Declare the variables as either CmtThreadLockHandle or CmtTSQHandle instead of int.
| |||||
| 443138 Return | The Interactive Execution window does not allow immediate termination when execution is suspended due to a break on change on variable value. Workaround: Step Over to the next step point or Continue to the next breakpoint.
| |||||
| 447051 Return | If the LabWindows/CVI debugger crashes (cvidebug.exe), all of the entries from the Watch window are cleared. Once you begin a new debugging session, the entries are restored to the Watch window. This scenario may cause LabWindows/CVI to become unstable. Workaround: Restart LabWindows/CVI.
| |||||
| 460394 Return | The Resource Tracking window shows freed resources as allocated if resource tracking is disabled after allocation. Workaround: N/A
| |||||
| 463635 Return | Opening the Graphical Array View for large, dynamically allocated arrays from the Array Display window causes an Index passed is out of range error. Workaround: N/A
| |||||
| 464563 Return | LabWindows/CVI does not allow you to attach to a 64-bit process running on a remote system. When you attempt to attach to a 64-bit process running remotely, you receive an error stating The current project configuration is not compatible with the debugger.... The Build»Configuration menu selection also becomes out of sync with the configuration displayed in the status bar at the bottom of the editor. Workaround: You can set the executable and command line correctly for the remote target system using Run»Specify Executable and Command Line and then you can select Run»Debug MyApplication.exe to launch the 64-bit process on the remote machine and debug it.
| |||||
| 466209 Return | The DebugPrintf function truncates large strings when printing to the Debug Output window. Workaround: Split long strings into multiple print statements.
| |||||
| 466763 Return | LabWindows/CVI does not show enough digits of precision in tooltips or the Variables and Call Stack window. The display has a 15-digit limit. Workaround: N/A
| |||||
| 466921 Return | Running a function using its function panel results in an Interactive Execution Unresolved symbol error even if the Include loaded instrument drivers in Interactive window Environment dialog box option is enabled. Workaround: Save your project after loading the instrument driver.
| |||||
| 469910 Return | LabWindows/CVI hangs when stepping through code for a console application and choosing Set Next Statement on the previous line after closing the console window while suspended. Workaround: N/A
| |||||
| 470486 Return | The Interactive Execution window incorrectly excludes the line and offsets the execution highlighting when adding a variable declaration on an instruction line. Workaround: Do not declare variables on instruction lines in the Interactive Execution window.
| |||||
| 470948 Return | The Interactive Execution window does not allow stepping into the main function of a project. Workaround: The Interactive Execution window allows stepping into the main function when execution is suspended in the project during a debugging session.
| |||||
| 472987 Return | The Parameter type incompatible with format specifier non-fatal run-time error does not display source location when 64-bit variables are used in code that causes the run-time error in the Debug64 configuration. Workaround: N/A
| |||||
| 502946 Return | The LabWindows/CVI debugger does not recognize variables that include the $ symbol as part of the variable name. If you view the value of a variable with a $ in its name in the Variables window while debugging, you will see an Error: Unrecognized Identifier error. Workaround: The C language specification states that $ is not a valid character to include in a variable name, so it is best to avoid using this character in variable names. This will prevent the error from occurring in the Variables window.
| |||||
| 465367 Return | If the data slice in an Array Display is changed, the numeric controls, Row and Column, in the Go to Cell dialog correctly change their ranges, but Go to Cell does not go to the correct cell. Workaround: N/A
| |||||
| 470673 Return | Changing the data slice and displaying the format of a 2D char array causes the Array View to become unusable, if the first dimension of the array is bigger than the second. Workaround: N/A
| |||||
| 473458 Return | The Variables and Call Stack window occasionally shows ERROR: Unexpected character. when changing the specific type for a variable. Workaround: N/A
| |||||
| 477649 Return | An incorrect uninitalized variable non-fatal run-time error is generated for partially initialized arrays inside of structs. Workaround: Initialize the array completely or turn off run-time error checking.
| |||||
| 478665 Return | A Graph doesn't have that many cursors error appears when debugging an application with multiple arrays shown in the Graphical Array View. Workaround: Open only one Graphical Array View at a time.
| |||||
| 479326 Return | The tooltip for an empty field on a function panel displays an = ERROR: Unexpected end of input. error when execution is suspended during debug. Workaround: N/A
| |||||
| 487428 Return | You receive a non-fatal run-time error, Attempt to read beyond end of string, when specifying a string member of a struct returned by a function as the source input for sprintf. Workaround:
| |||||
| 503717 Return | Debugging a project while concurrently debugging statements in the Interactive Execution window causes LabWindows/CVI to stop responding to commands. Workaround: Stop debugging in the Interactive Execution window before debugging a project.
| |||||
| 504099 Return | A linker error will occur if a global variable is referenced in the Interactive Execution window and if the project which defines the global variable is being debugged. If a statement such as extern int x; is used in the Interactive Execution window while the project which defines the variable x is being debugged, attempting to run statements in the Interactive Execution window will result in a linking error. Workaround: Declare the global variable in a second source file. Alternately, run the Interactive Execution window statements while not debugging the project which defines the global variable.
| |||||
| 515028 Return | When trying to browse for the members of a structure (<Ctrl-F1>) inside the Watch window, no browse info is found. Workaround: Call browse info from the source rather than from the Watch window.
| |||||
| 515433 Return | When a compilation error occurs while running a function panel interactively, information about which function panel field caused the compilation error is not shown. Workaround: Double-click the error in the Build Output window to see where the failure occurs in the Interactive Execution window.
| |||||
| 515436 Return | When using a user-interactive function (e.g., printf) in the Interactive Execution window, the console is not closed when execution finishes. Workaround: Select Build»Clear Interactive Declarations to close the console.
| |||||
| 515499 Return | Active breakpoints in the Interactive Execution window are hit when running function panels interactively. Workaround: Toggle breakpoints in the Interactive Execution window before running a function panel.
| |||||
| 515639 Return | An uninitialized pointer in a structure cannot be modified in the Variables and Call Stack and Watch windows. In the Watch window the pointer has the value Uninitialized. Workaround: N/A
| |||||
| 519172 Return | If you try to stop a program running in the Interactive Execution window after the cvidebug.exe process has been terminated, the editor crashes. Workaround: N/A
| |||||
| 532612 Return | Data tooltips do not display pointer values. When execution is paused at a breakpoint, hovering the mouse over a pointer in source only displays the address for that pointer. Workaround: Add a watch expression for the pointer or look at its value in the Variables and Call Stack window.
| |||||
| 533817 Return | The editable data tooltip does not display characters after a newline character. Workaround: Use the Watch window or the Variables and Call Stack window to correctly view the variable's value.
| |||||
| 541867 Return | While debugging, you cannot change the value of a _Bool variable in the data tooltip or the Watch or Variables and Call Stack windows. Workaround: N/A
| |||||
| Development Environment | ||||||
| 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.
| |||||
| 193733 Return | Launching the DataSocket Binding dialog box may cause LabWindows/CVI to hang on Windows 7. Workaround: Switch away from LabWindows/CVI to another application, and then switch back to LabWindows/CVI.
| |||||
| 216549 Return | LabWindows/CVI installs KeyHelp.ocx, which contains a security vulnerability. For more information, refer to this link. Workaround: This component is used for help tooltips in the LabWindows/CVI User Interface Editor. It can be safely prevented from being used in IE by using the Microsoft kill bit mechanism. The CLSID for this control is {16DDBCA2-9F0B-4927-9315-62D8893FC7E8}.
| |||||
| 227324 Return | LabWindows/CVI cannot copy files to the VXIPnP directories on Windows Vista and later. These directories are locked by default, which is not the correct behavior. Workaround: Install VISA, which will unlock these directories.
| |||||
| 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
| |||||
| 308191 Return | A multi-project workspace with projects targeting both 32-bit and 64-bit can incorrectly display import libraries. For example, consider the case where you have a workspace with two projects. If both projects have import libraries associated with them, and one project is 32-bit and one project is 64-bit, the bitness marking of the import libraries may be confusing. If the 64-bit project is the active project, the import libraries of the 32-bit project will show as dimmed and 64-bit. Then, if you make the 32-bit project the active project, the bitness of its import libraries will show correctly, but the import libraries of the 64-bit project will now display as 32-bit and dimmed. 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
| |||||
| 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.
| |||||
| 322905 Return | Files in a project may not display source control icons when a LabWindows/CVI project is associated with the Perforce client. If the Perforce Workspace root path has different casing than the actual path, then the icons do not display. Workaround: N/A
| |||||
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 333837 Return | LabWindows/CVI projects are not handled properly when adding them from new workspaces in instances of LabWindows/CVI created from just-in-time debugging. Adding or removing a project from the Project Tree in an instance of LabWindows/CVI created by the just-in-time debugger can cause unexpected behavior. Workaround: Do not add projects to the Project from instances of LabWindows/CVI created by the just-in-time debugger.
| |||||
| 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
| |||||
| 357212 Return | The save icon does not dim after saving a file. After a file is saved, the save icon is not dimmed. Once you click anywhere in the LabWindows/CVI editor after saving, the icon will then dim. 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
| |||||
| 363196 Return | Attribute passed is not valid error when declaring a variable in a function panel. The error is incorrectly displayed and can be ignored. Workaround: N/A
| |||||
| 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
| |||||
| 356708 Return | The Source window cursor can persist after selecting text and editing a variable tooltip. This behavior can cause two cursors to exist at the same time. Workaround: Scroll the Source Editor window up/down to make the old cursor go away.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.
| |||||
| 335488 Return | Excluded import libraries that represent both 32-bit and 64-bit .lib files are no longer dimmed after switching configurations. The .lib file is excluded but is not dimmed. Workaround: N/A
| |||||
| 366229 Return | The CVIXMLGetNumChildElements function does not count child elements included in an XML entity. Workaround: N/A
| |||||
| 440070 Return | The Find Next feature of the Find dialog box does not move to new results on subsequent uses. If you do not move the text caret from the first result you find and subsequently click Find Next from the Find dialog, you stay at the same result. Workaround:
| |||||
| 390670 Return | When you add a line continuation character \ to the end of a comment line initiated by the \\ symbol, the syntax highlighting feature does not continue to the next line, indicating the next line continues the comment. This behavior can be demonstrated with the following code snippet: \\This is a comment. \ This is also a comment. Workaround: Do not use a line continuation \ to break a comment between lines.
| |||||
| 439323 Return | LabWindows/CVI ignores changes made in the Environment Color Preferences dialog box in one of three panels in the Variables and Call Stack window Workaround: N/A
| |||||
| 451665 Return | The UI to Code Converter generates code containing an undefined function, InsertCtrlInCtrlArray. InsertCtrlInCtrlArray was renamed to InsertCtrlArrayItem in LabWindows/CVI 2010. Workaround: Replace all occurrences of InsertCtrlInCtrlArray with InsertCtrlArrayItem.
| |||||
| 369029 Return | The compile process does not wait for user response about missing include statements for header files. In versions of LabWindows/CVI previous to 2013, compiling a project with missing header files caused a dialog box to appear, prompting you to include the missing headers. The compile process did not continue until the dialog box was dismissed. Now, the compile continues despite the dialog box, and the project has to be rebuilt after adding the missing headers. Workaround: N/A
| |||||
| 375449 Return | Upgrading LabWindows/CVI breaks paths to Clang in .ecc configuration files. Workaround: Edit the .ecc file to point to the version of LabWindows/CVI you are trying to use.
| |||||
| 375463 Return | File icons may obscure full pathnames in the Project Tree. Workaround: N/A
| |||||
| 383011 Return | Unable to close the Open GL plot Properties dialog box after right-clicking the Open GL plot twice while the dialog box is open. Workaround: N/A
| |||||
| 391648 Return | Show Completions (<Ctrl-Space>) does not list members in anonymous structures or unions. Workaround: Do not use anonymous, nested structs. Declare nested components using named fields.
| |||||
| 403299 Return | The Functions in File ring is not wide enough to display some function names. Workaround: Open the drop-down view to see the function names in full length.
| |||||
| 411386 Return | The function panel size changes how function calls are inserted into code. For example, if the function panel is not maximized, the function call is added over multiple lines. However, if you maximize the function panel, the function call is inserted on one line. Workaround: N/A
| |||||
| 412464 Return | Opening, editing, and saving a source file with a very long file path causes LabWindows/CVI to crash. Previous versions of LabWindows/CVI display a Badly formed pathname message instead of crashing. Workaround: N/A
| |||||
| 429854 Return | The Find in Files feature fails when searching all files (*.*) in a directory containing .svn-base files. Workaround: Explicitly choose file types to search rather than using *.* in the File types field.
| |||||
| 437791 Return | LabWindows/CVI does not handle edge-specific maximization when restoring from a minimized state. Windows 7 introduced the ability to maximize only in one directiononly vertically or only horizontally. When you close the development environment with the Workspace window in an edge-specific, maximized state, it loses the original size of the window. Workaround: N/A
| |||||
| 438547 Return | The Functions in File dialog box immediately starts scrolling up when opened. When a ring control contains items that can no longer be displayed on the screen, LabWindows/CVI opens a modal dialog box containing a list box with all the items in the ring. Workaround: N/A
| |||||
| 438733 Return | If Hide windows when application is running is enabled, and a run-time crash occurs in the Interactive Execution window, the development environment becomes hidden and cannot be restored. Workaround: Select Show windows from the context menu of the task bar.
| |||||
| 384832 Return | Adding a file that is under source code control (SCC) using the Edit Project dialog box does not mark the file as being under SCC in the Project Tree. Workaround: Add files using Edit»Add Files to Project.
| |||||
| 391403 Return | Autoscale is a valid option for the y-axis of a strip chart, but the option is missing from the Attribute Browser. Workaround: Edit the option in the Edit Strip Chart dialog box.
| |||||
| 402786 Return | Show Completions <Ctrl-Space> does not work if a multi-line string starts with special char like {, }, ;, or #. You cannot perform Show Completions on foob in the following snippet, unless the { is removed from the beginning of the string. int foobar; printf("\ {sdf = %d", foob Workaround: N/A
| |||||
| 408099 Return | Pressing <Ctrl-Tab> to switch between tabs causes a Panel, menu bar, or control array handle is invalid message to display if confined function panel windows are open. Workaround: N/A
| |||||
| 409526 Return | Macros defined in precompiled headers are not included in browse information. Workaround: Use the Find in Files feature (<Ctrl-Shift-F>) to find the macro.
| |||||
| 423818 Return | The Show Completions feature fails to display context help for function parameters once the second parameter is highlighted if the function call immediately follows a curly brace. Workaround: N/A
| |||||
| 431732 Return | The LabWindows/CVI debugger starts applications outside of the window space in Windows 8.1 if you enable Variable, Continuous Size of Snap Views in Windows and LabWindows/CVI is used in the right-half of the screen. Workaround: Use LabWindows/CVI in the left half of the screen.
| |||||
| 435479 Return | Creating a file with the New»File from Template option that has the same path and name as an existing file results in an out of memory error. Workaround: Create a file with a different name or delete the existing file from disk before creating a file with the same path and name.
| |||||
| 436648 Return | Enabling the Compile with precompiled include file option in the Build Options dialog box causes a The User Interface Manager could not be opened to be displayed. Workaround: Save the project on disk.
| |||||
| 446313 Return | A dialog box explaining that saving UIR files will generate new versions of their include files is incorrectly displayed multiple times if there are multiple unsaved UIR files containing custom controls. Workaround: N/A
| |||||
| 463642 Return | Watch expressions cannot be deleted by pressing <Delete>, if the Break On Change checkbox has focus. Workaround: N/A
| |||||
| 463873 Return | Although Insert Mode is shown as active in the Array Display window when the window displays a data slice, the Insert Mode no longer has any effect. Workaround: N/A
| |||||
| 463921 Return | A tooltip containing Invisible is incorrectly displayed in the Memory Display window after maximizing and restoring the window. Workaround: The tooltip disappears after you confine the Memory Display window.
| |||||
| 467070 Return | The Maximum and Minimum fields in the Edit Table Cell dialog box are not wide enough to show int64 values. Workaround: N/A
| |||||
| 467775 Return | Enabling LoadExternalModule on one of the default Interface to Win32 API libraries and subsequently removing the library from the project tree causes the Interface to Win32 API library to remain forcibly included. The .prj file still contains an entry for the library under the [Modules Forced Into Executable] tag. Workaround: Add the Interface to Win32 API library file back to the project tree, uncheck the Interface to Win32 API library in the Add Files to Executable dialog box, and then remove the library from the project.
| |||||
| 470691 Return | The Build Output window highlights only error rows after double-clicking an error when building with an external compiler for release configuration. Normally the correct column is highlighted upon double-clicking the error message. Workaround: N/A
| |||||
| 473109 Return | Some data types such as _Bool and _Complex are not displayed correctly in function prototype tooltips. Workaround: N/A
| |||||
| 473496 Return | Data tooltips have a character entry limit that is about 24 characters at a time. Workaround: Close and re-open the data tooltip to enter more characters than the limit.
| |||||
| 475321 Return | Variables and Call Stack window columns incorrectly display extra columns, and columns are displaced after resizing columns while scrolling. Workaround:
| |||||
| 477231 Return | Incorrect confirmation prompts appear when exiting graph or chart dialog boxes. These prompts can occur with the following scenarios:
Workaround: N/A
| |||||
| 477287 Return | The Options»Preprocess Source File feature truncates output after 1024 characters on a line. Workaround: N/A
| |||||
| 499830 Return | Text for Custom Build Actions in the Build Steps dialog box may become corrupted when dialog box is closed. When the Custom Build Actions text is edited on the Build»Build Steps dialog box, the text may become corrupted when the dialog box is closed. If corruption has occurred, re-opening the dialog will show unexpected characters at the end of one or more of the lines in the Custom Build Actions dialog box. This could cause errors to occur when the custom build actions are executed during the build process. Workaround: If build errors occur due to corruption in the Custom Build Actions text, re-open the Build Steps dialog box and remove the corrupt characters from the Custom Build Actions field.
| |||||
| 470220 Return | Enabling both the Expand tabs to spaces when saving files and Convert leading spaces to tabs when loading files Editor Preferences options causes the current line statement to be highlighted incorrectly when debugging. Workaround: N/A
| |||||
| 471435 Return | Source code completion does not work properly following a / operator. Workaround: N/A
| |||||
| 479810 Return | Options»Create Object File does not throw errors if the output object file is read-only. Workaround: N/A
| |||||
| 489731 Return | The Variables and Call Stack window will not retain its position when LabWindows/CVI is restarted. If you right-click the Variables and Call Stack window, choose Release Window, and re-position the window, its position will not be saved when LabWindows/CVI is closed. Workaround: N/A
| |||||
| 492787 Return | "The buffer passed was too small for this operation" error will occur when entering text for a multiline tooltip in the User Interface Editor. This issue will occur for all controls and is not dependent on the length of the text entered for the multiline tooltip. Workaround: There are two possible workarounds to this issue:
| |||||
| 493985 Return | Closing the Format and Precision dialog while editing default cell values will cause the Edit Default Cell Values dialog to close. Workaround: N/A
| |||||
| 504102 Return | Interactive Execution will create a local copy of global variables instead of using the global variable reference. When the Interactive Execution window is used to execute a statement such as extern int x;, a separate copy of the x variable will be created rather than referencing the existing global variable x. Workaround: N/A
| |||||
| 509337 Return | Distribution Builder may not work properly if the distribution is stored at a network location requiring authentication. If the distribution is stored at a network location and that network location requires authentication, the Distribution Builder may not work properly unless you have previously provided login credentials for the network location in Windows Explorer. Behavior may include seeing the Select Source dialog reappear continually throughout the build process. Workaround: Before building the distribution, manually navigate to the network location in Windows Explorer and provide login information when prompted.
| |||||
| 512779 Return | The function prototype tooltip will not appear if a struct containing a member with the same name as the function is declared between the function declaration and function definition. The function prototype tooltip will not be displayed if a struct is defined between the function declaration and function definition if the struct contains a member with the same name as the function. For example, in the following code, a function prototype tooltip will not be displayed when the foo function is used: int foo(int param); struct myStruct { int foo; }; void main() { foo( // Function prototype tooltip will not be displayed when this line is typed } Workaround: Avoid defining structures between function declarations and definitions when the structure contains a member with a name shared by the function. For example, the code could be written in this way: struct myStruct { int foo; }; int foo; void main() { foo( // Function prototype tooltip will not be displayed when this line is typed }
|
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 515994 Return | When the Control Data Type of a Function Panel is a multi-dimensional array, the Select Variable result list is empty. Workaround: Use pointers to add dimensions when necessary.
| |||||
| 519487 Return | The source editor tabs are not updated when cycling through files during a Resolve All Excluded Lines operation. Workaround: N/A
| |||||
| Hardware | ||||||
| 296666 Return | Regenerating DAQmx example code can sometimes fail to regenerate code. If you change acquisition mode from "Every N Samples" to "Continuous Samples", the example code may not regenerate. Workaround: Regenerate the code from the source file instead of the header file.
| |||||
| Installer | ||||||
| 128084 Return | Uninstalling LabWindows/CVI from Windows Vista does not completely remove context menu file associations. Workaround: N/A
| |||||
| Performance | ||||||
| 144640 Return | LabWindows/CVI MAX_PATHNAME_LEN is more restrictive than Windows ANSI path limitation in multibyte systems. Workaround: N/A
| |||||
| 176800 Return | LabWindows/CVI projects converted to Microsoft Visual C++ 2005 projects fail to build because of link errors. Link errors such as cvisupp.lib(setprec.obj) : fatal error LNK1103: debugging information corrupt; recompile module and cviauto.lib(implib.obj) : fatal error LNK1103: debugging information corrupt; recompile module are indications your projects are affected by this problem. Workaround: Apply the VS2005 SP1 hotfix included for KB949009.
| |||||
| 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.
| |||||
| 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.
| |||||
| 281013 Return | Calling DDC_SaveFile often while creating a TDMS file using the TDM C DLL or the DDC Library can result in errors. Depending on when DDC_SaveFile is called, you might receive error -6218 or error -6226. Workaround: Don't call DDC_SaveFile until all operations are complete.
| |||||
| 257029 Return | The LabWindows/CVI Run-Time Engine creates windows in its DLL_PROCESS_ATTACH handler. When the LabWindows/CVI Run-Time Engine loads, it creates multiple windows in its DLL_PROCESS_ATTACH handler. This is generally discouraged practice, but has not been known to cause problems in user applications. Workaround: Do not call the Win32 API functions LoadLibrary and FreeLibrary to load and unload a LabWindows/CVI built DLL from different threads.
| |||||
| 457464 Return | Passing a bitmap file containing negative heights to PlotBitmap or GetBitmapFromFile causes a non-fatal run-time error: Library function error (return value == -12 [0xfffffff4]). Out of memory. Workaround: Modify the bitmap file header to have a positive height, reorder the pixels, and save the file.
| |||||
| 460818 Return | SMTP servers reject email from InetSendMail because it does not send date information in the header. Workaround: N/A
| |||||
| 371953 Return | The intensity plot does not handle NaN values. Workaround: Handle NaN values before passing the data to PlotScaledIntensity.
| |||||
| 405988 Return | Changing the active table cell can incorrectly send the EVENT_ACTIVE_CELL_CHANGE event multiple times. If, inside a callback function that handles EVENT_ACTIVE_CELL_CHANGE, you do something to change the focus of the panel (for example, displaying a message popup), the event is sent a second time after the callback finishes executing. Workaround: You can use the following code to handle the second, incorrectly sent event. void CVICALLBACK FlagClearFunc (void *callbackData) { *(int *)callbackData = 0; } int CVICALLBACK TableCB (int panel, int control, int event, void *callbackData, int eventData1, int eventData2) { static int ignoreNextEvent = 0; switch (event) { case EVENT_ACTIVE_CELL_CHANGE: if (!ignoreNextEvent) MessagePopup ( "title", "message" ); ignoreNextEvent = 1; PostDeferredCall (FlagClearFunc, &ignoreNextEvent); break; } return 0; }
| |||||
| 408097 Return | Passing a scalar value as the mask parameter of PlotPackedDigitalLines causes a general protection fault. Workaround: Ensure the mask value you provide has a data type that matches what you have specified for the dataType parameter.
| |||||
| 424944 Return | Creating a .NET controller for a large assembly, such as Microsoft.mshtml, appears to cause a hang but eventually completes successfully. Workaround: N/A
| |||||
| 429320 Return | InetFTPGetDirList returns 0 on certain FTP servers despite the presence of files.
| |||||
| 382850 Return | The NIReport_Print function hangs on Windows 8 when you select Microsoft XPS Document Writer as the printer. Workaround: N/A
| |||||
| 511573 Return | Scrolling through a table control containing thousands of images may cause a General Protection Fault. A fatal run-time error with the message General Protection Fault may occur if you create a table control with 10,0000 or more images and attempt to scroll through it. Workaround: It is recommended to use fewer rows when displaying images in a table control. If it is necessary to store a large number of images, you could store them in a data structure such as an array and populate a table control with a subset of the images as needed.
| |||||
| Stand-Alone Applications and Distributions | ||||||
| 186565 Return | LabWindows/CVI distributions cannot install fonts on Windows Vista or Windows 7. Workaround: N/A
| |||||
| 309112 Return | LabWindows/CVI 8.0 distributions cannot include the ActiveX container merge module if LabWindows/CVI 2009 or later is installed on the same system. This issue occurs because the name of the merge module changed in LabWindows/CVI 2009, and LabWindows/CVI 8.0.x attempted to find merge modules by name. Workaround: Create a copy of C:\Program Files (x86)\Common Files\Merge Modules\ActiveX_Container.msm and rename the copy to C:\Program Files (x86)\Common Files\Merge Modules\ActiveX Container.msm.
| |||||
| 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.
| |||||
| 440951 Return | When building a 64-bit installer, there is no installation directory option for LabVIEW (64-bit). When specifying Installation Files & Directories in the Edit Installer dialog box, you can choose [LabVIEW], but there is no option for [LabVIEW (64-bit)]. Workaround: When creating the installer, select [NationalInstruments] as the root for the component, and create the LabVIEW directory hierarchy underneath that directory.
| |||||
| User Interface | ||||||
| 126708 Return | PlotArc lacks accuracy for drawing a small angle with a large radius. 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.
| |||||
| 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
| |||||
| 194450 Return | LabWindows/CVI windows do not support Aero Shake. Shaking the title bar of the LabWindows/CVI environment or LabWindows/CVI panels or pressing <Windows-Home> when a LabWindows/CVI window is active does not minimize other open windows. When Aero is enabled in Windows 7, the other windows should be minimized by the Aero Shake feature. Workaround: N/A
| |||||
| 209745 Return | Very large maximum stack sizes cause the "My Documents" button of LabWindows/CVI file select popup panels to fail. After you click the My Documents button, only a white background displays. Your drives and network locations will not display. Workaround: Reduce the maximum stack size.
| |||||
| 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
| |||||
| 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
| |||||
| 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.
| |||||
| 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
| |||||
| 316397 Return | Saving a file with the FileSelectPopup function displays a "file already exists" error when another file with the same basename and no extension exists in the selected directory. The file is saved despite the error. Workaround: N/A
| |||||
| 329405 Return | Numeric control radix does not resize with control text size. N/A Workaround: N/A
| |||||
| 335982 Return | MultiFileSelectPopupEx cannot select multiple files if the first file in the list does not exist and the second file does. The selection error occurs only if the first file in the selection list does not exist and an existing file appears later in the list. Workaround: Ensure that the first file in the selection list exists.
| |||||
| 351981 Return | Dimming ActiveX control does not terminate mouse tracking. This behavior can cause problems if you dim the ActiveX control while doing a click and drag operation on the control. In this scenario, the mouse interaction continues even after the control is dimmed. Workaround: N/A
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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.
| |||||
| 369944 Return | The canvas control creates some undesired artifacts when rotated or moved around. Workaround: N/A
| |||||
| 382278 Return | The save button cannot be used in the Attribute Browser toolbar. Workaround: To save changes made in the Attribute Browser, use File»Save or <Ctrl-S>.
| |||||
| 404129 Return | After rotating the markers of a gauge control, the needle becomes misaligned with the center of the gauge. Workaround: N/A
| |||||
| 421591 Return | Active tooltips do not update when the tooltip text changes programmatically. Workaround: N/A
| |||||
| 423072 Return | The two panel attributes, ATTR_HEIGHT and ATTR_WIDTH, cannot be sized beyond a certain value, which depends on monitor resolution. Workaround: Use a child panel, which does not have the same height and width limitations.
| |||||
| 427065 Return | The maximum window size is limited by screen resolution. This maximum value is imposed during the LabWindows/CVI WM_GETMINMAXINFO message handler. Workaround: Intercept the WM_GETMINMAXINFO message and change the maximum values as demonstrated in the following code snippet: //Custom window procedure static LRESULT CALLBACK MsgrWndProc (HWND hwnd, UINT message, WPARAM wParam, LPARAM lParam ) { switch(message) { case WM_GETMINMAXINFO: { if(largeSize) { //Modify lParam such that it uses the correct sizes MINMAXINFO FAR *lpmmi = (MINMAXINFO FAR*)lParam; lpmmi->ptMaxTrackSize.y = customHeight; lpmmi->ptMaxTrackSize.x = customWidth; largeSize = 0; //Return 0 to swallow the event return 0; } } } //Call the default window procedure and pass it the parameters passed to it return CallWindowProc((WNDPROC)DefaultWndProc, hwnd, message, wParam, lParam); }
| |||||
| 431566 Return | In the User Interface Editor, if you rotate a text message that has the Size to text option disabled, the resulting text message is drawn incorrectly, selected incorrectly, and inoperable. Workaround: N/A
| |||||
| 432165 Return | Under specific graph setting conditions, the fat line plot style renders incorrectly. Instead of a solid line, the line appears half solid, half broken. Workaround: Disable anti-aliasing or y-axis labels, or add a plot legend. Resizing the graph sometimes resolves the rendering issue.
| |||||
| 437605 Return | Graphs containing multiple plots with different plot styles show incorrect plot styles in the graph legend. Workaround: Obtain the plot style programmatically.
| |||||
| 439046 Return | Toolbar click events do not cause numeric controls to leave edit mode. If you are editing a control using the keyboard and subsequently click a toolbar menu item, the control does not commit the edit before the toolbar menu item click event is processed. If the control loses focus, the edit is committed. Workaround: Commit control edits by calling SetActiveCtrl (GetActivePanel (), GetActiveCtrl (GetActivePanel ())); before reading the control value.
| |||||
| 460638 Return | The picture command button can incorrectly show the resizing frame when the Size control to image Fit mode is selected. The picture command button should not be allowed to change dimensions in this mode. Workaround: Close and reopen the UIR file.
| |||||
| 391647 Return | Changing focus from the graph control while you operate a cursor inside the control leaves the cursor at an intermediate position. Workaround: N/A
| |||||
| 402602 Return | The graph control plot can change size when the graph control changes size, even when the Fixed Plot Area attribute (ATTR_FIXED_PLOT_AREA) is enabled. Workaround: Track the plot area and restore it after a graph control resize operation causes the plot area to change.
| |||||
| 415654 Return | When scrolling a tree control and the currently selected item line moves to the top or bottom of the control, it seems as though multiple items are selected. Workaround: Change focus from the tree control. When the tree control loses focus, it redraws the item selection correctly.
| |||||
| 424549 Return | The default values for the ATTR_HIDE_HILITE and ATTR_HILITE_ONLY_WHEN_PANEL_ACTIVE attributes do not persist for table controls when set in the UIR file. Workaround: Set the values programmatically using SetCtrlAttribute.
| |||||
| 461922 Return | Enabling Show Grid and Auto Divisions in the Edit Axis Settings dialog box for the right y-axis causes incorrect x-axis tick marks to appear. Enabling these settings for the left y-axis does not result in incorrect tick marks. Workaround: Uncheck Auto Divisions in the Edit Axis Settings dialog box for the right y-axis and change the Divisions setting to a specific number.
| |||||
| 470189 Return | Resizing a knob control by operating a splitter control causes the digital display of the knob control to be positioned at the wrong coordinates. Workaround: N/A
| |||||
| 484206 Return | The image quality of some images loaded in a picture command button degrades after saving and loading the user interface file multiple times. Reduction of quality is noticeable after 10 saves. Workaround: Reload the original image from disk. You can do this programmatically by setting the ATTR_IMAGE_FILE attribute with SetCtrlAttribute.
| |||||
| 489628 Return | Displaying a floating point number with more than 16 digits may cause the number to be displayed in scientific notation. When a floating point number with more than 16 digits is displayed in a numeric control with 2 digits of precision, the value will be displayed in scientific notation. For example, 1E-16 will display as 0.00, but 1E-17 will display as 1E-17. Workaround: If the value you are displaying in the numeric control is smaller than 1.0E-17, write a zero to the numeric control instead of the original value.
| |||||
| 494678 Return | EVENT_COMMIT is not raised when focus is changed from a table cell in edit mode to a different user interface panel. Workaround: Use a different event, such as EVENT_EDIT_MODE_STATE_CHANGE, to instruct your application to react to the table cell losing focus.
| |||||
| 498977 Return | Graph axis divisions may not be plotted when axis scale is set to certain values. This issue only occurs for certain axis scales. Data is correctly plotted on the graph, but the axis division markers are not displayed. Workaround: Change the axis scale to force the axis division markers to be plotted.
| |||||
| 514898 Return | LabWindows/CVI does not mark the UIR file as modified after changing the Frame Color of a decoration, which results in changing the Conform to System Color and Conform to System Theme panel attributes. Workaround: Make an additional change to the panel and explicitly save the UIR file to commit the changed attributes to the UIR file.
| |||||
| 526939 Return | You cannot directly change the tab order of initially dimmed controls in the Edit Tabbing Order dialog by clicking the dimmed controls. Workaround: Set the tab order of controls before enabling Initially dimmed.
| |||||