Print
PDFOverview
This document contains the LabWindows/CVI 2012 known issues that were discovered before and since the release of LabWindows/CVI 2012. 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.
Each known issue includes these fields:
- Issue ID
- Legacy ID - The issue's legacy ID from NI's deprecated bug reporting database (if applicable)
- Issue Title
- Problem Description
- Workaround
- Reported Version - the earliest version of LabWindows/CVI the issue was reported in
- Resolved Version - version the issue was resolved or was no longer applicable
- Date Added - the date the issue was added to the document (not the reported date)
Modules and Toolkits
The Known Issues for toolkits and modules can be found in the LabWindows/CVI Modules and Toolkits Known Issues document.
Document Organization
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 date they were added to this document. To view the issues organized by category, visit the document linked below:
Known Issues by Category
Contacting NI
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.
Known Issues by Date
The following items are known issues in LabWindows/CVI 2012 sorted by Date.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 126708 Return |
PlotArc lacks accuracy for drawing a small angle with a large radius. Workaround: N/A
|
|||||
| 128084 Return |
Uninstalling LabWindows/CVI from Windows Vista does not completely remove context menu file associations. 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.
|
|||||
| 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 moduleand cviauto.lib(implib.obj) : fatal error LNK1103: debugging information corrupt; recompile moduleare indications your projects are affected by this problem. Workaround: Apply the VS2005 SP1 hotfix included for KB949009.
|
|||||
| 186565 Return |
LabWindows/CVI distributions cannot install fonts on Windows Vista or Windows 7. 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.
|
|||||
| 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
|
|||||
| 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.
|
|||||
| 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
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 210086 Return |
The LabWindows/CVI environment may hang while debugging with the Variables or Watch windows open. Workaround: N/A
|
|||||
| 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.
|
|||||
| 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}.
|
|||||
| 236157 Return |
Opening a TDMS file that is at the same time open in another process can result in an error/ This issue occurs even if the file is opened in read-only mode. 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.
|
|||||
| 256488 Return |
Duplicate "Could not expand variable" dialog boxes may display while debugging. If you step over code while a watchpoint is expanded, you may see multiple "Could not expand variable" dialog boxes. Workaround: Disable extended Variables/Watch window displays.
|
|||||
| 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.
|
|||||
| 257004 Return |
You cannot remote debug a multithreaded program with extended variable displays enabled. Workaround: Disable the Enable extended Variables/Watch window displays option in the Environment dialog box.
|
|||||
| 257264 Return |
Watchpoints might not be able to run after manually suspending a multithreaded program. Workaround: N/A
|
|||||
| 237998 Return |
Cannot link some uuid.lib symbols in a 32-bit program. Workaround: N/A
|
|||||
| 257397 Return |
Debugging a multithreaded real-time program with watchpoints may cause the real-time target to hang. The watchpoints must be in update continuously mode or set to break when the value changes. Workaround: Disable Update display continuously and Break when value changes for watchpoints.
|
|||||
| 44669 4HK7LF7K Return |
The WordRpt_SetHeader function might not always work as expected. Embedding pictures in a header does not work. Workaround: N/A
|
|||||
| 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.
|
|||||
| 283594 Return |
clang does not recognize the _export and _import qualifiers. Workaround: Use __declspec(dllexport) and __declspec(dllimport) instead.
|
|||||
| 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
|
|||||
| 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
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 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
|
|||||
| 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.
|
|||||
| 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
|
|||||
| 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
|
|||||
| 304359 Return |
Attaching to a process that loads a debuggable LabWindows/CVI DLL can result in LabWindows/CVI crashing if you open an unrelated project after debugging the process. Workaround: N/A
|
|||||
| 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
|
|||||
| 306206 Return |
The clang external compiler does not correctly handle the long double data type.All long double variables will have a value of 0.Workaround: Use double instead of long double.
|
|||||
| 298025 Return |
Setting the inputMode parameter of SetInputMode to 0 blocks user interaction when events are processed, not when the user interacts with the UI.This can be seen by calling SetInputMode(...,...,0) inside a callback function, delaying for one second, and then calling SetInputMode(...,...,1) before exiting the callback function. If you click the dimmed button during the 1 second delay, that click event will be processed the next time events are processed by the LabWindows/CVI Run-Time Engine.Workaround: Ensure that events are being processed when the inputMode parameter of SetInputMode to is set to 0.
|
|||||
| 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.
|
|||||
| 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:
|
|||||
| 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.
|
|||||
| 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
|
|||||
| 257160 Return |
The LabWindows/CVI debugger can hang when LoadPanel fails in a DLL with variables expanded using the Specific Type option in the Variables window. 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];Workaround: Change the Debugging level option (Options»Build Options) to No run-time checking.
|
|||||
| 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
|
|||||
| 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)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.
|
|||||
| 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
|
|||||
| 331932 Return |
Partially selecting an attribute value in the Attribute Browser and then resizing the Attribute Browser causes the entire text in that field to be selected. 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
|
|||||
| 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.
|
|||||
| 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
|
|||||
| 311364 Return |
Function name displays twice in the function prototype tooltip when the return value is const or volatile. N/A Workaround: N/A
|
|||||
| 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
|
|||||
| 344028 Return |
Program can hang when a graph or strip chart is on screen and axis labels are visible For this problem to occur at least one axis label must visible. When label strings get too close to the edge of the control, they will attempt to reposition themselves inward to avoid being cut off, but in some cases the repositioning algorithm will reposition to the same value and cycle endlessly. On Linux this problem can manifest itself as a hang that requires you to end the process. This problem is most likely to occur with one of the x-axis label strings if the x-axis has negative values or ATTR_FIXED_PLOT_AREA is enabled and ATTR_PLOT_AREA_LEFT is set too close to the edge. Workaround: There are two workarounds: 1) Disable the axis label string. 2) Enable ATTR_FIXED_PLOT_AREA and then set ATTR_PLOT_AREA_LEFT (if the problem is happening with the left x-axis) to a value a few pixels over to the right until the problem stops occurring. The value this needs to be set to is dependent on the font and min/max of the affected scale so a precise value can't be given.
|
|||||
| 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
|
|||||
| 334992 Return |
Watch expressions become inactive after switching configurations. Watch expressions are tied to a specific executable or DLL. If the target settings for two different configurations point to different paths, then the watch expression cannot be shared between the two configurations. 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
|
|||||
| 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
|
|||||
| 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
|
|||||
| 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
|
|||||
| 329405 Return |
Numeric control radix does not resize with control text size. N/A Workaround: N/A
|
|||||
| 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.
|
|||||
| 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
|
|||||
| 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
|
|||||
| 359402 Return |
Third-party compilers do not enable C99 extensions even if you enable the Build with C99 extensions option in the Build Options dialog box. This behavior can cause problems in some LabWindows/CVI headers that require _CVI_C99_EXTENSIONS_ to be defined. Workaround: In the Advanced Compiler Options dialog box for the third party setup, add -D_CVI_C99_EXTENSIONS_=1 to the C99 Flags field. While this flag is enabled, the C99 extensions checkbox will work for this third party compiler.
|
|||||
| 360351 Return |
NI Automotive Diagnostic Command Set and NI ECU Measurement and Calibration Toolkit cannot be activated through NI License Manager. Workaround: Activate the toolkit through the NI Activation Wizard in LabWIndows/CVI. To launch the NI Activation Wizard, click the Activate Products button in the LabWindows/CVI Message that displays when you launch LabWindows/CVI.
|
|||||
| 362376 Return |
The Programmer's Toolbox function ListCreate leaks memory. The memory leak occurs only in a debug build. Workaround: N/A
|
|||||
| 360485 Return |
Passing NULL to SingleToneSignal for the searchType input parameter causes a fatal run-time error. Workaround: Pass an invalid input instead.
|
|||||
| 360745 Return |
Cannot launch the LabWindows/CVI Help from the Help menu when a help tooltip is visible. Workaround: N/A
|
|||||
| 361054 Return |
Attribute not valid error when auto-declaring a variable from ANSI C Library Formatted Input/Output functions such as printf or sprintf. The error occurs only when auto-declaring the Target String or the Format String. The error can be ignored. 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
|
|||||
| 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
|
|||||
| 362403 Return |
Saving a copy of the UIR as an older version causes the currently loaded copy to switch to that version. Using the Save Copy of UIR As option will create a copy of the UIR in the specified version. However, the currently loaded UIR also changes to the specified version. If the UIR is then saved, it is saved as the earlier version. Workaround: Close the current UIR without saving changes. Reopen the UIR, and it will be in the correct version.
|
|||||
| 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.
|
|||||
| 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
|
|||||
| 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
|
|||||
| 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
|
|||||
| 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.
|
|||||
| 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
|
|||||
| 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.
|
|||||
| 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
|
|||||
| 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
|
|||||
| 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
|
|||||
| 340055 Return |
Breakpoints may be missed when attaching to a non-debuggable process that calls a debuggable DLL in multiple threads. 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
|
|||||
| 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
|
|||||
| 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.
|
|||||
| 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
|
|||||
| 351155 Return |
LoadExternalModule does not guarantee that the module loaded is 16-byte aligned. This behavior may cause errors when using third-party compilers. 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
|
|||||
| 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: Follow the instructions in KnowledgeBase 5A6C270U: Cannot Update Custom Icon of an Executable in Windows 7 or Vista to remove the cached icon.
|
|||||
| 355331 Return |
Editing the RGB values of an RGB color in the Watch window doesn't also update the overall value of the variable in the parent node. The value is updated, but the displayed value of the parent node is not updated. Workaround: N/A
|
|||||
| 356421 Return |
Entries in the Watch window may be dimmed incorrectly if multiple entries have the same symbol name. Multiple entries with the same symbol name may exist because they have different scope. Workaround: N/A
|
|||||
| 356470 Return |
Building the sdk\stdio\demo.prj example project in a 64-bit configuration against the clang compiler causes an unrecoverable internal error. Building the project located at C:\Users\Public\Documents\National Instruments\CVI2012\samples\sdk\stdio\demo.prj causes the unrecoverable error. 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
|
|||||
| 357245 Return |
Local array in a thread that has exited may appear as still active in the Watch window. This behavior can occur if the thread exited using the CmtExitThreadPoolThread function instead of return.Workaround: N/A
|
|||||
| 358560 Return |
Function name is not reported in Break On Library Errors message. 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
|
|||||
| 360314 Return |
The LabWindows/CVI environment crashes when showing a time_t variable in the Watch or Variables window while debugging a 64-bit application with extended debugging enabled.Workaround: N/A
|
|||||
| 335983 Return |
Tooltip for symbol values during debugging may appear on top of the editor's scrollbar. 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.
|
|||||
| 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
|
|||||
| 339287 Return |
The Default index for combo box cell types in the Edit Table dialog box expands too far down if the value has multiple lines. Workaround: N/A
|
|||||
| 364220 Return |
Welcome Page PDF links do not work unless you are using Adobe Acrobat. Most of the links in the What's New in LabWindows/CVI section of the Welcome Page do not work as expected. The link to See All Feature Descriptions works correctly. Workaround: Set your default PDF reader to be Adobe Acrobat.
|
|||||
| 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
|
|||||
| 362404 Return |
The LabWindows/CVI Run-Time Engine displays incorrectly in LabVIEW Application Builder and TestStand Deployment Utility. The Run-Time Engine will appear as "NI LabWindows/CVI Run-Time Engine @package.release.year@" instead of "NI LabWindows/CVI Run-Time Engine 2012". The incorrect text will appear in the LabVIEW Application Builder and TestStand Deployment Utility, but will appear correctly in the LabWindows/CVI Edit Installer dialog box. Workaround: Refer to KB 5ZPDLIQW: Why does the LabWindows/CVI Run-Time Engine Display Incorrectly in LabVIEW Application Builder and TestStand Deployment Utility? for more information.
|
Document last updated on 8/1/2012
Reader Comments | Submit a comment »
Legal
This tutorial (this "tutorial") was developed by National Instruments ("NI"). Although technical support of this tutorial may be made available by National Instruments, the content in this tutorial may not be completely tested and verified, and NI does not guarantee its quality in any way or that NI will continue to support this content with each new revision of related products and drivers. THIS TUTORIAL IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND AND SUBJECT TO CERTAIN RESTRICTIONS AS MORE SPECIFICALLY SET FORTH IN NI.COM'S TERMS OF USE (http://ni.com/legal/termsofuse/unitedstates/us/).