Print
PDFOverview
This document contains the LabWindows/CVI 2010 and 2010 SP1 known issues that were discovered before and since the release of LabWindows/CVI 2010. 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 2010 and 2010 SP1 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
|
|||||
| 243203 Return |
LabWindows/CVI file dialog boxes cannot open files accessed through the Libraries button on Windows 7. Windows 7 introduced the Libraries button to the common file dialog boxes. LabWindows/CVI cannot open files that have been accessed by browsing through this button. Workaround: Do not browse to files with the Libraries button.
|
|||||
| 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.
|
|||||
| 258354 Return |
CNVProcessIsRunning may incorrectly report that the process is running if the program is run as a startup program. CNVProcessIsRunning checks only if the process is configured to run when the Variable Engine is started. In most cases, this check is a good indicator of whether the process is running because the Variable Engine--a Windows service that automatically starts when Windows starts--loads all the processes configured to run. Workaround: Try to browse to the process using the functions in the Browser Functions class of the Network Variable Library. If you are able to browse to the process using CNVBrowse, the process is running. The following code is an example of browsing to a process:
|
|||||
| 258376 Return |
Mousing over an ActiveX control when the title bar is not visible causes the control to disappear. Workaround: If the control has a windowless mode, use the windowless mode.
|
|||||
| 258505 Return |
Selecting "Create New File" on a project folder results in an invalid file. If you right-click a folder in a LabWindows/CVI project and select Create New File, you will not be able to create an Empty file. Workaround: N/A
|
|||||
| 248829 Return |
The function GaussHG returns NaN for X values less than 0. Workaround: N/A
|
|||||
| 254291 Return |
LabWindows/CVI will hang when building a distribution for an executable that is signed with a certificate that is not available. Workaround: N/A
|
|||||
| 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
|
|||||
| 257782 Return |
The Resource Tracking window does not track thread local variable handles. Workaround: N/A
|
|||||
| 258506 Return |
The Attribute Browser Find text box might incorrectly filter attributes when double-clicking a control in the User Interface Browser. If you enter text in the Attribute Browser Find text box and double-click a control in the User Interface Browser when a panel is active in the Attribute Browser, the available attributes in the Attribute Browser will be filtered. Workaround: N/A
|
|||||
| 253304 Return |
TDMS Files with very high channel counts might be slow to open. Workaround: N/A
|
|||||
| 258835 Return |
Using clang 1.0 as your active release compiler might result in link errors if you include windows.h from more than one source file. If you use clang 1.0 as your active release compiler and you disable C99 extensions, you will get link errors if you include windows.h from more than one source file.Workaround: Enable the Build with C99 extensions option in the Configuration Options tab of the Build Options dialog box.
|
|||||
| 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
|
|||||
| 276026 Return |
LabWindows/CVI can generate code into the wrong source file without asking for confirmation. The following steps will reproduce this issue:
Notice the callback and header files were placed in the unrelated example's source file. Workaround: Ensure you always have zero or at least 2 source files open when generating code.
|
|||||
| 277253 Return |
Non-void pointer types in function prototypes have an extra asterisk in the LabWindows/CVI help. All function prototypes in the LabWindows/CVI help contain an extra asterisk for non-void pointer type parameters. For example, the function GetNumListItems is written asint GetNumListItems (int panelHandle, int controlID, int **count);in the LabWindows/CVI help. However, it should be written as int GetNumListItems (int panelHandle, int controlID, int *count);This issue is only present in the compiled help accessed through the Help menu. The Function Panel help does not have this issue. Workaround: Do the following to resolve this issue:
|
|||||
| 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.
|
|||||
| 285633 Return |
LabWindows/CVI might crash if you create a panel with a very long title. LabWindows/CVI might crash during some operations in the User Interface Editor if the .uir file you are editing contains a panel with a very long title.Workaround: Avoid titles longer than ~150 characters.
|
|||||
| 286276 Return |
The frame of the increment and decrement buttons on numeric controls may not draw entirely. When using Windows visual styles, the top portion of the frame of the increment button or the bottom portion of the frame of the decrement button may not be drawn depending on the font that is used. Workaround: Slightly alter the font size or font face you are using.
|
|||||
| 286688 Return |
The menu text for a menu using a non-metafont rotates when a panel with Scale Contents on Resize enabled is resized. Depending upon how the text rotates, it may not even be visible, appearing as if the text has disappeared completely. Workaround: Create a metafont from the desired font. For example, the following solves this issue for a panel with a panel handle named panelHandle and a single menu bar:
|
|||||
| 283527 Return |
LabWindows/CVI carets ignore Windows keyboard settings. Through the Keyboard Settings applet in the Windows Control Panel, you can adjust the blink rate of the caret, or you can disable blinking altogether. LabWindows/CVI ignores this setting. Workaround: N/A
|
|||||
| 283594 Return |
clang does not recognize the _export and _import qualifiers. Workaround: Use __declspec(dllexport) and __declspec(dllimport) instead.
|
|||||
| 283634 Return |
The LabWindows/CVI Visual Studio Conversion Wizard fails for some projects that reference National Instruments modular instruments drivers. If the modular instruments driver references any files relative to IVI Standard Root, IVI Standard Root 64-bit, VXIPlug&Play 64-bit, or VXIPlug&Play kbase 64-bit, the LabWindows/CVI Conversion Wizard fails. Workaround: Open the LabWindows/CVI .prj file in a text editor and change entries that look like the following:Note that values in project files are limited to 82 characters (including the quotes), and if the path is going to exceed that amount, you'll need to split up the path into multiple lines.
|
|||||
| 284362 Return |
When you select a value from a combo box table cell in edit mode, the table cell might not display the value you select. Workaround: N/A
|
|||||
| 284771 Return |
When using third-party compilers, linker errors refer to temporary object files. If link errors are found for multiple modules, the link errors will all be reported in the same temporary object file. Workaround: N/A
|
|||||
| 284842 Return |
The GetTableCellRangeVals and SetTableCellRangeVals functions do not work for string cell types in a 64-bit application. Workaround: Set the value of each cell individually with SetTableCellVal.
|
|||||
| 285074 Return |
Previewing substitutions in the Version Info dialog box sometimes does not show correct values. By default, the %application variable expands to the value of the Application Title field in the Target Settings dialog box. If this field is empty, the target file base name is used to expand the %application variable. However, when Preview Substitutions is selected in the Version Info dialog box, if the Application Title is blank, the %application variable is replaced with an empty string.Workaround: N/A
|
|||||
| 285102 Return |
Modifying a custom build configuration might not update version information. If you edit a custom build configuration and change it from Debug to Release, or from 32-bit to 64-bit, the %rel_dbg and %arch flags may not update appropriately.Workaround: Modify a field in the Version Info dialog box and rebuild.
|
|||||
| 282844 Return |
LabWindows/CVI does not allow users to save files following an exception. When the LabWindows/CVI environment experiences an exception, it should allow you to save your files before it crashes. However, because of this bug, LabWindows/CVI disappears when an exception occurs. Workaround: N/A
|
|||||
| 282946 Return |
Right justified numeric controls can draw their text incorrectly. If a right justified numeric control is the active control on a panel, the text of the control may be draw incorrectly when the panel receives focus. Workaround: N/A
|
|||||
| 283042 Return |
A LabWindows/CVI ActiveX server can crash while shutting down if there are open client connections to the server. Workaround: N/A
|
|||||
| 283065 Return |
LabWindows/CVI cannot generate wrappers for .NET Framework 4.0 assemblies. The Create LabWindows/CVI .NET Controller dialog box cannot generate wrappers for .NET Framework 4.0 assemblies. When trying to create a wrapper for .NET Framework 4.0 assemblies, the error Error occurred while generating .NET controller code. The method or operation is not implemented. will be shown.Workaround: Paste the following XML into a file named cvi.exe.config. Place this file next to cvi.exe in the LabWindows/CVI directory. <?xml version="1.0"?> <configuration> <startup useLegacyV2RuntimeActivationPolicy="true"> <supportedRuntime version="v4.0"/> </startup> </configuration> After you've done this, restart LabWindows/CVI.
|
|||||
| 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
|
|||||
| 287394 Return |
HTML and XML files generated from source code contain an extra asterisk for output parameters in function prototype. Parameters that are marked as output parameters by using the /// OUT tag will contain an extra asterisk in the function prototype.Workaround: N/A
|
|||||
| 275934 Return |
Including the http.h Win32 API header file can result in missing function prototype compile errors. If you have enabled the Require function prototypes option in the Build Options dialog box, including http.h can result in a missing function prototype compilation error. Workaround: If the function reported as missing a prototype does not take any parameters, ensure the keyword void is added to the parameter list in the function declaration.
|
|||||
| 276442 Return |
Displaying a file select popup panel from a panel with a tab control might disrupt the panel z-plane order. If a panel has both a tab control and child panels, and the child panels overlap the tab control, the child panel can be overlapped by the tab control after displaying a file select popup panel or a directory select popup panel. Workaround: N/A
|
|||||
| 276443 Return |
A tab inserted anywhere but the end of the list will use the wrong image. A tab that is inserted into a tab control at any position but the end of the list will result in the new tab using the image from tab that is in the next position. For example, if a tab control has three tabs, inserting a tab into the second position will cause the new tab to use the same image as the now third tab. Workaround: N/A
|
|||||
| 276524 Return |
compile.exe may report link errors for National Instruments libraries. If the LabWindows/CVI development environment has not been launched, compile.exe might report link errors for some libraries, such as the LabWindows/CVI SQL Toolkit or the Programmer's Toolbox. Workaround: Run LabWindows/CVI before using compile.exe.
|
|||||
| 276799 Return |
Numeric table cells do not coerce values when values are pasted from the clipboard. If a table cell or range of cells is not in edit mode when a value is pasted from the clipboard, the cell will not coerce the value to the specified minimum or maximum values. Workaround: N/A
|
|||||
| 277640 Return |
The User Interface Browser may not update when Find UI Object is selected from a source file. If you right-click a control constant name in a source file and select Find UI Object, the User Interface Browser might not redraw. Workaround: Switch away from the User Interface Editor and then switch back.
|
|||||
| 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.
|
|||||
| 278742 Return |
In a distribution, the path to the CHM help file for an ActiveX server file is incorrect When creating a distribution for an ActiveX server, the distribution builder looks in the wrong location for the CHM help file that belongs to the ActiveX server. The distribution should look in the target output directory, but instead looks in the Release or Release64 directory. Workaround: Manually copy the CHM help file to the Release or Release64 directory after regenerating the ActiveX server.
|
|||||
| 279028 Return |
Enabling or disabling profiling does not trigger a rebuild of your project. If you enable execution profiling in the Build Options dialog box, LabWindows/CVI does not mark your project for recompilation. This means that the next time you run your project, you will not get profiling information. Workaround: After enabling or disabling profiling, select Build»Mark Project for Compilation.
|
|||||
| 279916 Return |
The defaultFileSpec parameter of the FileSelectPopup function does not work correctly. The defaultFileSpec parameter does not filter on the actual filename, only on extensions. This behavior is a bug. However, there was also a behavioral change introduced in all versions of Windows Vista and later. For example, passing *.c as the defaultFileSpec will show files test.c, test.cws, and test.cfg. This is an issue with the underlying file dialog box and will not be fixed by LabWindows/CVI. Workaround: N/A
|
|||||
| 280209 Return |
Calling IIRCascadeFiltering in a loop produces erroneous results. Workaround: Call the FreeIIRFilterPtr function after every IIRCascadeFiltering function.
|
|||||
| 280320 Return |
Scroll bar thumbs of table controls do not redraw when scrolling the table with the keyboard. Workaround: N/A
|
|||||
| 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.
|
|||||
| 281082 Return |
A strip chart legend may not be drawn correctly if it overlaps the strip chart plot area. If a strip chart legend overlaps the plot area for the strip chart it is associated with, the legend will not redraw correctly if its visibility is toggled. Workaround: Place a transparent control on top of the strip chart's plot area.
|
|||||
| 281083 Return |
The y-axis name of a strip chart control might be drawn incorrectly when the y-axis autoscales. When the data on a strip chart causes the y-axis to autoscale, the y-axis name may be drawn incorrectly. Workaround: Do not enable autoscaling for the strip chart.
|
|||||
| 282253 Return |
Data tooltip is too small to hold negative zero floating-point values. Workaround: N/A
|
|||||
| 282612 Return |
Editing a menu associated with a panel on an unsaved UIR can cause LabWindows/CVI to crash. This crash can occur if the following conditions are true:
Workaround: Save the panel before editing the menu.
|
|||||
| 282794 Return |
You cannot add a type library for a project that defines multiple functions that differ only in case. If the function panel for your DLL project specifies multiple functions whose names differ only in case, you will not be able to embed a type library in your DLL. Workaround: Modify the function names so that they are different in aspects other than case-sensitivity.
|
|||||
| 285443 Return |
The run-time movable custom control (movectrl.fp) leaks memory. Workaround: N/A
|
|||||
| 287954 Return |
The progress bar might not draw correctly when it is overlapped by other controls. If your progress bar is updating automatically, a common mistake is to not process events for the thread that owns the progress bar as the progress bar is updating. For more information, refer to the help for the VAL_PROGRESSBAR_AUTO_MODE value for the ATTR_PROGRESSBAR_UPDATE_MODE attribute here. However, even if you are processing events, the progress bar may not draw correctly.Workaround: Toggle the visibility of the progress bar before it needs to redraw. For example, if you are manually updating the progress bar, you could do the following: Otherwise, if the progress bar is updating automatically, you would toggle the visibility of the progress bar before you processed events, similar to the following:
|
|||||
| 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.
|
|||||
| 258827 Return |
Block and sweep strip chart modes do not scroll properly Plotting to a strip chart in block or sweep mode does not work. Once data reaches the end of the plot bounds, data no longer displays, and the plot area flickers. Workaround: Download and install the updated version of the LabWindows/CVI Run-Time Engine.
|
|||||
| 288099 Return |
The ProgressBar_GetPercentage function panel defines the percentage parameter to be an input parameter. Because the percentage parameter is actually an output parameter, declaring a variable from the function panel will result in a variable of the wrong type being declared. It will be declared as a double * instead of a double.Workaround: Add the percentage variable manually instead of declaring it from the function panel.
|
|||||
| 288104 Return |
Changing any environment option while in an untitled workspace results in an error. If you are in the LabWindows/CVI environment and have not specified a workspace name, changing any environment option will result in the error message Badly formed pathname.Workaround: N/A
|
|||||
| 288389 Return |
The splitter control can disappear after is it dragged. This issue occurs only on Windows 7 or Windows Vista with Aero enabled. Workaround: Create a callback function for your splitter controls. In the EVENT_DROPPED case, hide the control, delay for a short amount of time, and then display the control. For example, adding the following code to the EVENT_DROPPED case of the splitter callback function should cause the splitter to display whenever it is dropped.
|
|||||
| 289945 Return |
Selecting a .lib instead of a .dll from the Generate DLL Import Library file dialog box causes LabWindows/CVI to crash. Workaround: Select a .dll file to generate an import library from, not a .lib.
|
|||||
| 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.
|
|||||
| 278151 Return |
A breakpoint with a pass count and a condition will never break execution as a result of the pass count. If a breakpoint has both a condition and a pass count, the pass count will be ignored. As a result, if the condition is never met, the breakpoint will never break execution. Workaround: N/A
|
|||||
| 290386 Return |
Uninstalling LabWindows/CVI distributions from some non-English operating systems fails. Uninstalling a LabWindows/CVI distribution from the Add/Remove Software control panel applet causes the National Instruments uninstaller to crash immediately. No uninstallation occurs. Workaround: Go to Control Panel»Clock, Language, and Region»Region and Language»Format and pick English (United States). Then uninstall the distribution.
|
|||||
| 280705 Return |
You cannot enter numbers in scientific notation into numeric controls holding 64-bit integers. Workaround: Enter a decimal number instead of a number in scientific notation.
|
|||||
| 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
|
|||||
| 290057 Return |
Copying a control from one panel to the other in the User Interface Editor can cause the Attribute Browser to display incorrectly. The Attribute Browser displays information for the wrong control. Workaround: Edit the control by double-clicking it to open the Edit Control dialog box.
|
|||||
| 290737 Return |
InetSendMail can crash if the "To:" field exceeds 250 bytes. Workaround: If the "To:" field is longer than 250 bytes because you need to email multiple people, call the InetSendMail function multiple times so that the "To:" field doesn't exceed 250 bytes.
|
|||||
| 309109 Return |
When installing a LabWindows/CVI distribution with a private RTE install, the mesa and instrsup merge modules do not install locally. LabWindows/CVI performs a private RTE install if you enable the Install LabWindows/CVI Run-Time Engine in the application directory option in the Edit Installer dialog box. The instrsup merge module has not installed privately since LabWindows/CVI 2009. The mesa merge module has not installed privately since LabWindows/CVI 2010. Workaround: N/A
|
|||||
| 309184 Return |
compile.exe can crash when passed a project path that can't be found on disk. If you pass a .prj file and one or more .c files to compile.exe and the .prj file cannot be found on disk, compile.exe will crash. Workaround: Ensure the .prj file can be found.
|
|||||
| 299976 Return |
LabWindows/CVI might corrupt files if they are stored on some types of network storage. If contents are deleted from the file, additional lines will be appended to the end of the file when it is saved. This has currently been seen only when saving files on a VirtualBox shared drive, but may occur on other network shares as well. Workaround: Share the files over some other type of network storage.
|
|||||
| 300075 Return |
Editing instrument driver attributes using the Attibute Editor tool can cause attributes to be duplicated in the .sub file. Workaround: Edit a driver's attributes using LabWindows/CVI 8.5 or earlier.
|
|||||
| 300534 Return |
compile.exe does not work in evaluation mode without launching LabWindows/CVI once. If you have not yet launched LabWindows/CVI, compile.exe will return -1. Workaround: Launch LabWindows/CVI once before running compile.exe.
|
|||||
| 302494 Return |
Memory is leaked when calling GetScaledCtrlDisplayBitmap on graph control with ATTR_COPY_ORIGINAL_DATA set to 0.Workaround: Complete the following steps:
|
|||||
| 302870 Return |
User Interface Localizer can crash when you click "Next" on the last item of a tree control. If your UI contains a tree control, the User Interface Localizer will crash when you click next to reach the last item of the tree control for localization. Workaround: Click the last item to localize its label.
|
|||||
| 303247 Return |
Strip chart x-axis division spacing does not remain while plotting. If your axis label ticks line up with your division markers, you will see the spacing change in the division markers. This results in the division markers no longer lining up with the axis label ticks. 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
|
|||||
| 303721 Return |
Table row and column header separators do not line up with the row and column marker lines when Windows visual styles are enabled. In Windows 7, the row lines do not match up. In Windows XP, the column lines do not match up. Workaround: Disable Windows visual styles for controls.
|
|||||
| 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
|
|||||
| 304541 Return |
The Run-Time Movable Control (movectrl.fp) custom control does not display a hand when moving numeric controls. Normally, when moving a control by using the movable control custom control, a hand is displayed as the mouse cursor. However, an I-beam cursor is displayed for numeric controls. Workaround: N/A
|
|||||
| 305258 Return |
GetScaledCtrlDisplayBitmap can hang for some scaling ratios.For instance, scaling a graph from 400x801 pixels to 200x200 pixels will cause a hang. Workaround: Modify the scaling factor until the hang does not occur.
|
|||||
| 306036 Return |
Calling RegisterDDEServer and then UnregisterDDEServer results in the report of a resource leak in the Resource Tracking window.No memory is actually being leaked. Workaround: Ignore the report of the leaked resource.
|
|||||
| 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.
|
|||||
| 306560 Return |
VAL_SIZE_TO_PICTURE can significantly degrade the resolution of pictures if the pictures must shrink. Workaround: N/A
|
|||||
| 306648 Return |
Some controls in the LabWindows/CVI environment do not dim properly when they have different values between build configurations. For example, if the File Version and Product Version controls have different values for 32-bit and 64-bit configurations, they will not be dimmed when the All Configurations option is selected. Workaround: N/A
|
|||||
| 306727 Return |
LabWindows/CVI can crash when attempting to rename a file belonging to a project that is under source code control. If the project that belongs to source code control is not checked out, LabWindows/CVI can crash if you try to rename a file in that project. Workaround: Rename the file outside of the LabWindows/CVI source code control interface.
|
|||||
| 306728 Return |
Attempting to rename a file under source code control fails. When using a source code control (SCC) provider in LabWindows/CVI, you might not be able to rename a file under SCC through the SCC interface. Workaround: Rename the file outside of the LabWindows/CVI source code control interface.
|
|||||
| 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
|
|||||
| 308500 Return |
You cannot view predefined macros through the Manage Configurations dialog box. Try to view the predefined macros for a build configuration by selecting Build»Configuration»Manage Configurations»Edit»Build Options»Predefined Macros. Workaround: Select Options»Build Options and select a configuration from the Configuration ring. Then select the Predefined Macros button.
|
|||||
| 308664 Return |
The bottom of some characters on the y-axis of a strip chart can be clipped incorrectly. For example, the bottom half of the letter g will be clipped. Workaround: N/A
|
|||||
| 308967 Return |
A 64-bit LabWindows/CVI distribution allows the end user to override the 32-bit National Instruments directory, but not the 64-bit National Instruments directory. Even though you have built a 64-bit distribution in LabWindows/CVI, the end user will be presented with the option to change the 32-bit National Instruments directory. They will not be allowed to change the 64-bit National Instruments directory. Workaround: N/A
|
|||||
| 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.
|
|||||
| 298184 Return |
Non-fatal user protection errors can sometimes display only the message &%%s&. This can happen when there is a mismatch in the release vs. debug build configuration between a LabWindows/CVI EXE and its DLLs. Workaround: Ensure all LabWindows/CVI binaries in a process are either in debug configuration or release configuration.
|
|||||
| 298366 Return |
There are miscellaneous problems with code comment tags. The following are known issues when automatically generating stub source code comments with <Ctrl+Shift+G>:
When a project is built, the following are known issues with the HTML and/or XML that can be generated for the comments:
Workaround: N/A
|
|||||
| 298456 Return |
A program that has called EnableDragAndDrop might crash if closed from the Windows taskbar.Workaround: N/A
|
|||||
| 298632 Return |
Full ticks are not consistently drawn for many numeric controls. When full ticks are enabled for numeric slides, knobs, gauges, dials, or meters, some full ticks will be drawn darker than others. This is because the full ticks are drawn multiple times at once, leading to darkening because of the alpha blending done by ClearType. Workaround: Disable ClearType.
|
|||||
| 298790 Return |
Tree items with ATTR_CELL_DIMMED can be toggled and do not draw completely dimmed.If a tree item has ATTR_CELL_DIMMED set, you should not be able to alter its draw state, and the check box or radio button should also be drawn as dimmed.Workaround: See the workaround proposed by jared here.
|
|||||
| 299606 Return |
The LabWindows/CVI ActiveX Controller Wizard does not display all registered ActiveX servers. Servers registered with paths of type REG_EXPAND_SZ are not listed. Workaround: Manually browse to the server object containing a type library.
|
|||||
| 299674 Return |
Pasting unicode text into the LabWindows/CVI Source window can cause LabWindows/CVI to crash. Workaround: N/A
|
|||||
| 299688 Return |
Some items in the LabWindows/CVI status bar require a double-click to toggle, while others require a single-click. Workaround: N/A
|
|||||
| 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.
|
|||||
| 309627 Return |
LabWindows/CVI can crash when compiling some K&R style functions. This crash occurs only if you disable the Require function prototypes option. For example, if you attempt to compile a file with the following code, LabWindows/CVI crashes. void foo (a) int a(enum {x,y}); { } Workaround: Enable the Require function prototypes option and add a prototype for the function.
|
|||||
| 295246 Return |
A source file containing a very large array of structures might fail to compile. For example, if you declare an array of 5000000 NIComplexNumber structures, LabWindows/CVI will fail to compile the file without any error message. Workaround: Either:
|
|||||
| 295507 Return |
Undoing after hiding and showing panels can cause LabWindows/CVI to crash. The following steps will result in LabWindows/CVI crashing:
Workaround: N/A
|
|||||
| 295529 Return |
Changing only the type of a custom configuration does not trigger a rebuild of your project. This will cause link errors if you change the type of your configuration from debug to release. This will cause you not to be able to debug if you change the type of your configuration from release to debug. Workaround: After changing the type, select Build»Mark Project for Compilation.
|
|||||
| 295530 Return |
Watch expressions that evaluate global variables might not work when debugging a custom build configuration. If the custom build configuration's build settings specify a different build target name than the corresponding default configuration, the watch expression will not work without modifying the Executable/DLL option associated with the watch expression. Workaround: N/A
|
|||||
| 295654 Return |
Building a project with the same name as a previously loaded project can cause LabWindows/CVI to crash. This crash can occur if you complete the following steps:
Workaround: N/A
|
|||||
| 296155 Return |
Network variable and ActiveX support do not automatically get selected when building 64-bit distributions. If you are building a 64-bit distribution that depends on network variable or ActiveX, their dependencies should automatically be selected when building a distribution. Workaround: Manually check the network variable and/or ActiveX support components.
|
|||||
| 296380 Return |
EVENT_SORT does not appear in the User Interface Editor. If you interactively sort tree items in the User Interface Editor, the only event that appears in the status bar is EVENT_GOT_FOCUS. EVENT_SORT does not appear. Workaround: N/A
|
|||||
| 296381 Return |
You cannot use the Edit Text Tool to edit the last cell in a table column. If you click <Enter> after editing the last cell, it looks as if the value that you entered has been committed, but if you change to operate mode, or if you click on a different cell, you'll notice that the changes have been lost. Workaround: Instead of clicking <Enter>, click a different cell instead. Or, use the Edit Table dialog box instead of the Edit Text Tool to enter values in edit mode.
|
|||||
| 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.
|
|||||
| 297271 Return |
Some analysis files are left behind after uninstalling LabWindows/CVI. Files are left in the directories C:\ProgramData\National Instruments\CVI<version>\bin and C:\ProgramData\National Instruments\CVI<version>\extlib. Workaround: N/A
|
|||||
| 294281 Return |
Making a change to a project that is under source code control in LabWindows/CVI does not result in checking out the project. LabWindows/CVI does not acknowledge that the project has been checked out after making a change. This means that you are unable to save the project. Workaround: Close and re-open the project. Then make your changes.
|
|||||
| 294282 Return |
Files added to a project cannot be added to source code control. When you add a file to a project under source code control (SCC), a dialog box will be shown asking if you want to add the file to SCC. If you select yes, you will be shown the file checkout dialog, but it is empty. Workaround: Close and re-open the project. Then add the file to SCC.
|
|||||
| 294443 Return |
"Index out of range" error in the Edit Columns/Cells dialog box. This error can be shown when trying to select a cell by specifying its coordinates in the Edit Columns/Cells dialog box. Workaround: N/A
|
|||||
| 294650 Return |
Undo in the User Interface Editor can change the z-plane order of controls. Workaround: N/A
|
|||||
| 294725 Return |
Adding or removing an item from a tree that's not in edit mode might, in rare circumstances, cause a crash. Workaround: N/A
|
|||||
| 294960 Return |
Switching execution targets after debugging and then beginning a new debugging session can result in LabWindows/CVI crashing. This crash will occur only if there is an existing watch expression in the project, and if the project has build steps. Workaround: Remove any watch expressions before switching execution targets.
|
|||||
| 295228 Return |
You cannot select Add Watch Expression from the Watch window context menu until a watch expression has been added another way. Workaround: Add a watch expression by another method, such as dragging an expression into the Watch window or by right-clicking a variable or expression in the Source window and selecting Add Watch Expression.
|
|||||
| 292521 Return |
An application whose installer includes only the "Network Variable Support" sub-item might run slower than expected on a minimally configured target computer. Under this scenario, the components necessary for LogosXT are not installed. Workaround: Distribute the entire LabWindows/CVI Run-Time Engine.
|
|||||
| 292539 Return |
Opening a distribution that was created in LabWindows/CVI 7.1 and earlier can cause a crash during conversion. Workaround: Convert the files first in a version of LabWindows/CVI earlier than 2010, such as LabWindows/CVI 2009. Then open the distribution in LabWindows/CVI 2010.
|
|||||
| 292805 Return |
An application whose installer includes only the "Network Variable Support" sub-item might not run correctly on a minimally configured target computer. Workaround: Distribute the entire LabWindows/CVI Run-Time Engine.
|
|||||
| 292892 Return |
The LabWindows/CVI Visual Studio Conversion wizards will fail for projects that depend on the Analysis Library. This is a problem only for LabWindows/CVI service pack releases. Workaround: In the Visual Studio project properties dialog box, modify the added include paths to include c:\ProgramData\National Instrument\CVI<version>\Include, instead of c:\ProgramData\National Instruments\CVI<version> SP1\Include.
|
|||||
| 292939 Return |
If a running instance of LabWindows/CVI is minimized, it will not be listed in the Just-In-Time Debugger Selector dialog box. Workaround: N/A
|
|||||
| 292992 Return |
Users cannot completely disallow creating directories in FileSelectPopup and DirSelectPopup. If you pass 0 as the AllowMakeDirectory parameter of FileSelectPopup or DirSelectPopup, the icon for creating a folder is not present in the dialog box. However, users can still right-click the file list and select New»Folder.Workaround: N/A
|
|||||
| 293467 Return |
The LabWindows/CVI 2010 title bar can change to use a classic style Windows theme after saving files. This issue happens only on Windows XP. Workaround: Click the LabWindows/CVI title bar to restore the correct theming to the title bar.
|
|||||
| 293672 Return |
Some user interface controls do not draw Windows styles on mouse-over. For example, the following controls and control parts should display as a highlighted blue on Windows Vista and later, but do not:
Workaround: N/A
|
|||||
| 293859 Return |
The Floating Style attribute of a child panel can cause displayed panels to display as modal behind other displayed panels. Workaround: Change the Floating Style panel attribute of all child panels to Never.
|
|||||
| 293875 Return |
Multiple confirmation dialog boxes can be shown for the same operation. Multiple confirmation dialog boxes can be shown under the following circumstances:
Workaround: N/A
|
|||||
| 294008 Return |
New files added in the Edit Project dialog box do not use the Project Tree Font. If you use a non-standard font for the Project Tree Font and add files to a project in the Edit Project dialog box, the new files will be drawn with the wrong font. Workaround: N/A
|
|||||
| 294159 Return |
<Ctrl-Left Arrow> and <Ctrl-Right Arrow> do not work correctly in text controls on multibyte versions of Windows. The text cursor does not correctly move to work breaks. Workaround: N/A
|
|||||
| 294161 Return |
Controls can be added to control arrays to which they already belong. When you right-click a control in the User Interface Editor, you can select to add the control to a control array it already belongs to. The control is not actually added, but the option should not be available. Workaround: N/A
|
|||||
| 294217 Return |
The Edit Breakpoint dialog box incorrectly maintains a reference to old files. If you place breakpoints in one workspace and then debug a project, the source files those breakpoints were placed in will not be removed from the Edit Breakpoint dialog box when a new workspace is loaded. Workaround: N/A
|
|||||
| 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
|
|||||
| 286606 Return |
In a multi-project workspace, when editing a distribution, the output files of a project might incorrectly refer to the output files of a different project. Workaround: N/A
|
|||||
| 290986 Return |
A 32-bit application whose installer includes only the "ActiveX Container Support" sub-item might not run correctly on a minimally configured target computer. Workaround: Distribute the full LabWindows/CVI Run-Time Engine.
|
|||||
| 291368 Return |
Line numbers are missing from the Standard I/O window. Workaround: N/A
|
|||||
| 291452 Return |
An application whose installer includes only the "Standard Run-Time" sub-item might run with a "Mesa.dll could not be found" error on a minimally configured target computer. Workaround: Distribute the full LabWindows/CVI Run-Time Engine.
|
|||||
| 291813 Return |
Distributions with .inf files fail to install after checking module dependencies.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.
|
|||||
| 292030 Return |
Passing NULL to the DefaultFileSpec parameter causes your application to crash.This issue occurs for the following functions:
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
|
|||||
| 292130 Return |
Calling GetPanelAttribute with ATTR_TITLEBAR_ACTUAL_THICKNESS returns undefined results if the panel titlebar is not visible.The function should return 0 when the titlebar is not visible but instead returns an undefined value. Workaround: Verify that the titlebar is visible using ATTR_TITLEBAR_VISIBLE before getting the actual thickness of the titlebar.
|
|||||
| 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.
|
|||||
| 326213 Return |
The Go to Line button causes an internal assert to be triggered. When execution is suspended on a breakpoint, pressing Go to Line in the Breakpoints dialog box for a breakpoint that has a valid location but an invalid condition causes an assert to be triggered. Workaround: N/A
|
|||||
| 327730 Return |
LabWindows/CVI crashes during compilation when a very long variable name is used. Variables with names of roughly 500 characters or longer will cause LabWindows/CVI to crash when compiling. Workaround: N/A
|
|||||
| 328422 Return |
64-bit distributions are not detecting dependencies automatically when using merge-module components of the LabWindows/CVI Run-Time Engine. When selecting a sub component of the LabWindows/CVI Run-Time Engine in the Edit Installer dialog box, dependent components are not automatically selected for a 64-bit configuration. Workaround: N/A
|
|||||
| 328679 Return |
Graph legend items are highlighted after calling RecallPanelState under some conditions. This behavior can occur even if the ATTR_LEGEND_INTERACTIVE attribute is disabled. Workaround: N/A
|
|||||
| 328823 Return |
Toolbox.c and toolbox.h are not added to a Microsoft Visual Studio project if LabWindows/CVI is not run at least once after installation. N/A Workaround: N/A
|
|||||
| 328896 Return |
Debugging a DLL built in LabWindows/CVI that defines DllMain crashes the RT target. Debugging a DLL that defines DllMain crashes LabVIEW Real-Time on the RT target when the entry point function returns. Workaround: Do not define DllMain in a DLL that will be debugged on an RT target.
|
|||||
| 328940 Return |
LabWindows/CVI DLL projects converted to Microsoft Visual Studio projects do not properly link ANSI C functions. N/A Workaround: After converting the project to a Visual Studio project, open the project properties in Visual Studio, and browse to Linker>>Command Line. Remove "/NODEFAULTLIB:MSVCRT" from the "Additional options:" field.
|
|||||
| 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
|
|||||
| 329406 Return |
LabWindows/CVI crashes when setting the Offset option for a graph if the Absolute Time Display Format is set to a very large number. N/A Workaround: N/A
|
|||||
| 329461 Return |
Printing UIR files resizes the table control in the print output. N/A Workaround: N/A
|
|||||
| 331534 Return |
The scroll bars in the User Interface Editor do not appear when changing the panel size using the cursor. When you expands a panel to fill the User Interface Editor using the cursor and click the inside edge of the border of the panel, the panel border may be partially outside the editor. In this case the scroll bars do not appear and part of the panel is inaccessible. Workaround: Move the panel and the scroll bars will appear properly.
|
|||||
| 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
|
|||||
| 319377 Return |
SavePanelState causes a General Protection Fault when called in a 64-bit application. After the crash, the state of the save file is unknown. The crash occurs because of header information in the save file. Workaround: Create a save file in a 32-bit application and use it for the 64-bit application. The save file created in the 32-bit application will have the correct header information. The missing information occurs when creating a new file, but does not occur when modifying an existing file. The save file created in the 32-bit application does not need to be related to the 64-bit application.
|
|||||
| 323520 Return |
LabWindows/CVI saves files with the FILE_ATTRIBUTE_TEMPORARY attribute set. The FILE_ATTRIBUTE_TEMPORARY is only set on files that are not created in LabWindows/CVI. The attribute has effects on system caching and is mostly harmless. However, the attribute has been reported to cause Microsoft Visual Studio to skip searching the file when using the Find in Files tool.Workaround: The temporary file attribute can be removed using the command line.
|
|||||
| 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.
|
|||||
| 313512 Return |
Ring control label/value pairs precision does not persist when changed. When the precision of a double or float label/value pair is modified in the User Interface Editor, the precision attribute is restored to its original value when the Edit Label/Value Pairs dialog box is opened again. Workaround: This behavior occurs only if there is only 1 label/value pair. Multiple label/value pairs persist the precision attribute. If you want only 1 label/value pair, add a second label/value pair and then change the precision attribute. Close the Edit Label/Value Pairs dialog box by clicking OK. Return to the Edit Label/Value Pairs dialog box and remove the second label/value pair. The precision attribute will now persist this value.
|
|||||
| 314106 Return |
The x-axis of the digital graph displays improper divisions. Large digital graphs with engineering or scientific display format set for the x-axis may display divisions and division labels that are inconsistent with other display formats. Workaround: N/A
|
|||||
| 310362 Return |
LabWindows/CVI may crash when rebuilding a project with a precompiled header file. LabWindows/CVI crashes when rebuilding a portion of a project that depends on a precompiled header file that includes a header file with a warning. Workaround: Mark project for compilation before rebuilding.
|
|||||
| 310600 Return |
FileToArray function does not support 64-bit data types. N/A Workaround: N/A
|
|||||
| 310781 Return |
The table control displays a gap between the table cells and the bottom and right edges of the control when resized. This is an effect of the control's 3D style and not a bug. Future versions will allow the frame to be made invisible with the ATTR_FRAME_VISIBLE attribute.Workaround: Disable the Use Windows Visual Styles for Controls option for the panel.
|
|||||
| 310817 Return |
Table control triggers a general protection fault after not cleaning up resources from an Out of Memory error. If a table is made so large that an Out of Memory error is triggered, the table control does not properly recalculate the number of rows and columns. Any access to the table can cause a general protection fault. Workaround: N/A
|
|||||
| 311281 Return |
Graph controls display the x-axis name at an angle if you set the ATTR_XYNAME_FONT attribute to a metafont that rotates text. The graph should not display fonts that specify an angle of rotation for text for the x-axis name. Workaround: N/A
|
|||||
| 311356 Return |
Changes to the font persist in the Font dialog box when the action is canceled. If you make changes in the Font dialog box, but cancel your changes, the changes are not applied. However, if you open the Font dialog box again, the changes will still be active in the dialog box and will be applied if you then click OK. This behavior does not affect changes to the Source Window font. Workaround: N/A
|
|||||
| 311364 Return |
Function name displays twice in the function prototype tooltip when the return value is const or volatile. N/A Workaround: N/A
|
|||||
| 312084 Return |
Setting an incorrect working directory in the Specify Executable to Debug dialog box provides an incorrect error message. Setting an incorrect working directory reports "Bad executable file pathname", but the executable file pathname may be correct. Workaround: N/A
|
|||||
| 312179 Return |
Some Microsoft DLLs are automatically included in distributions built with LabWindows/CVI. Some Microsoft dependencies are operating system dependent and should not be included in distributions. These dependencies typically already exist on most targets. If not, then they should be installed from a Microsoft distribution. Workaround: N/A
|
|||||
| 312398 Return |
Deleting all lines from a text box control with no lines available to delete causes a nonfatal runtime error. Passing -1 for the Number of Lines parameter of the DeleteTextBoxLines function deletes all lines from the index to the end. However, if there are no lines after the index, a nonfatal runtime error will occur.Workaround: N/A
|
|||||
| 313299 Return |
CVI_AppGetLinesFromFile returns a string with maximum length of INT16_MAX characters. The maximum puts too small of a limit on the amount of source code text that can be returned from a single call to CVI_AppGetLinesFromFile .Workaround: N/A
|
|||||
| 313765 Return |
The LabWindows/CVI Run-Time Engine may crash when unloading a DLL that contains a panel in a thread other than the main thread. N/A Workaround: N/A
|
|||||
| 314344 Return |
Changing the panel title from a different thread can cause a hang. Changing the panel title from a thread other than the thread that the panel was created in can cause a hang. Workaround: N/A
|
|||||
| 314631 Return |
MultiFileSelectPopup removes leading spaces from file names and returns an error. The MultiFileSelectPopup function assumes that files do not have a leading space in the file name, but this is not always true. Workaround: N/A
|
|||||
| 314876 Return |
The LabWindows/CVI Run-Time Engine can hang when calling CloseCVIRTE in a secondary thread. The CloseCVIRTE function can cause a hang if called from a thread other than the main thread. Workaround: N/A
|
|||||
| 316246 Return |
LabWindows/CVI changes foreground lock timeout to 0 when debugging. When debugging an application, the debugger changes the HKEY_CURRENT_USER\Control Panel\Desktop\ForegroundLockTimeout registry key to 0. This is necessary to control which window is in the foreground when debugging. The debugger should restore the registry key to its previous state when it is done debugging.Workaround: N/A
|
|||||
| 316361 Return |
The LabWindows/CVI low-level support driver CVINTDRV.sys contains a security vulnerability. Refer to KnowledgeBase 5Q5FJ4QW: How Does National Instruments Security Update 5Q5FJ4QW Affect Me? for more details. Workaround: N/A
|
|||||
| 316365 Return |
Panel toolbars are not fully discarded when created and discarded in a thread other than main. Calling the Toolbar_Discard function in a thread other than the main thread will cause a Non-Fatal Run-Time Error to occur when exiting the main function.Workaround: The error can be ignored because it only occurs when the application is exiting. Call SetBreakOnLibraryErrors (0) as the last statement in the main function to hide this error.
|
|||||
| 316626 Return |
The physdemo.cws example uses functionality that is removed with Security Update 5Q5FJ4QW. The physdemo.cws example is not installed with LabWindows/CVI 2010 SP1 or later. Workaround: N/A
|
|||||
| 316930 Return |
Possible to see 100% CPU usage 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. There is no visible behavior issue caused by this problem on Windows other than high CPU usage. 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.
|
|||||
| 317147 Return |
The fgetpos function writes only 4 bytes to the Current File Position output parameter in a 64-bit application. In a 64-bit application, the fpos_t data type used for the Current File Position parameter is 8 bytes long, but the function fills only the lower 4 bytes of the variable passed in.Workaround: Initialize the fpos_t variable to 0 before passing it to the fgetpos function.
|
|||||
| 318200 Return |
The Edit Tabbing Order dialog box does not allow you to modify the tabbing order of controls that are behind overlapping controls. N/A Workaround: N/A
|
|||||
| 319561 Return |
SetCursorAttribute does not return an error when passed an annotation attribute. The SetCursorAttribute function will attempt to set an attribute that does not exist and can produce undefined errors. Workaround: Do not pass annotation attributes to SetCursorAttribute.
|
|||||
| 320396 Return |
Replacing a file in the Edit Project dialog box that is not yet part of the project causes the development environment to crash. If you add a file to the project in the Edit Project dialog box and then replace that file before exiting the dialog box by clicking OK to submit the change, the development environment will crash. Workaround: N/A
|
|||||
| 321793 Return |
Adding multiple files with the same name in the Edit Project dialog box can cause LabWindows/CVI to crash. This behavior can occur if you use the Edit Project dialog box to add two files to the project with the same filename but different paths. When you select OK to confirm the changes, a warning will appear stating that a file with the same name already exists in the project. If you remove the duplicate file and click OK again, the development environment will crash. Workaround: N/A
|
|||||
| 322063 Return |
The project settings for certificate signing are not saved in the project file. When the Signing Info settings are modified, an empty string is saved as the certificate store in the project file. Workaround: Manually modify the project file in a text editor after configuring certificate signing in the Signing Information dialog box. Change the Store value from the empty string to the name of the certificate store (typically "My"). If you reopen the Signing Information dialog box and save the project, LabWindows/CVI saves the store as empty string again. Access the Signing Information dialog box through the Target Settings dialog box.
|
|||||
| 322203 Return |
If you change a breakpoint due to an invalid condition while you are debugging, LabWindows/CVI ignores the next breakpoint. If your code contains a breakpoint with an invalid condition followed by another invalid breakpoint (either with an invalid condition or set on a line containing no executable code), LabWindows/CVI displays the Invalid Condition dialog box for the first breakpoint. If you make the condition valid and click Replace or click Delete to delete the breakpoint, LabWindows/CVI ignores the next breakpoint. Workaround: N/A
|
|||||
| 322458 Return |
Changes to configuration options entered in the Manage Configurations dialog box may not be persisted under rare circumstances. N/A Workaround: Modify configuration options by selecting the configuration in Build»Configuration. Then use the Option»Build Options and Build»Target Settings menu items to modify configurations.
|
|||||
| 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
|
|||||
| 324351 Return |
Canceling from the Invalid Breakpoint dialog box causes the LabWindows/CVI debugger to ignore all remaining breakpoints and continue execution. If you have a breakpoint with an invalid condition when you begin debugging, LabWindows/CVI displays the Invalid Condition dialog box for that breakpoint. However, if you click Cancel in this dialog box, LabWindows/CVI resumes execution of the program. All other breakpoints following this breakpoint will be skipped and debugging will continue. Workaround: N/A
|
|||||
| 329376 Return |
The graph legend does not always match the angle of text plots. The angle of the text in the sample plot of the graph legend may or may not match the angle of the text plot. Different behavior is demonstrated for various angles, font sizes, and fonts. Some conditions may cause the sample plot to display an underlined font when the plot does not use an underlined font. Workaround: N/A
|
|||||
| 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.
|
|||||
| 324499 Return |
Clicking Cancel in the Invalid Condition dialog box can cause a breakpoint to be deleted. While you are debugging, if you add an invalid condition to an existing breakpoint using the Edit Breakpoint dialog box and then click Cancel in the Invalid Condition dialog box, the breakpoint is deleted. Workaround: Do not use the Edit Breakpoint dialog box to add a condition to an existing breakpoint. Use the Breakpoints dialog box to edit the breakpoint instead.
|
|||||
| 324786 Return |
Adding an invalid condition to an existing breakpoint during debug from the Breakpoints dialog box and then clicking Delete in the Invalid Condition dialog box does not delete the modified breakpoint. During debug (when the program is running or suspended), adding an invalid condition to an existing breakpoint from the Breakpoints dialog box and then clicking Delete in the Invalid Condition dialog box, either replaces the edited breakpoint with the next breakpoint in the breakpoints list or assigns the invalid condition to the edited breakpoint in the breakpoints list if there is no breakpoint after it in the list. Either way, after submitting changes by clicking OK in the Breakpoints dialog box, the edited breakpoint will not be present in the source file. Workaround: Click Cancel in the Invalid Condition dialog box and delete the breakpoint manually from the Breakpoints dialog box.
|
|||||
| 324806 Return |
Adding a breakpoint on an invalid line from the Breakpoints dialog box and then moving the breakpoint creates a breakpoint that you cannot interact with. While you are debugging (and execution is not suspended), if you add a breakpoint on an invalid line from the Breakpoints dialog box, LabWindows/CVI prompts you to resolve the conflict. If you select to move the breakpoint, LabWindows/CVI moves the breakpoint in the source file immediately. If you cancel the dialog box, LabWindows/CVI does not remove the breakpoint in the source file, and you cannot operate the breakpoint. Workaround: To remove the broken breakpoint, open the Breakpoints dialog box again and click OK to refresh all breakpoints.
|
|||||
| 324829 Return |
LabWindows/CVI crashes while debugging when adding a conditional breakpoint to the Interactive Execution window if the window doesn't contain any executable code. N/A Workaround: N/A
|
|||||
| 325065 Return |
The Line option and Add button are not updated when the file is changed in the Edit Breakpoint dialog box. If the Add button is disabled because you are editing a breakpoint from a file that does not allow a breakpointand then witch to a file that does, the Add button is not enabled. Also, if the line number is set to a line that does not exist in the file that you switch to, the line number does not update to an existing line number. Workaround: N/A
|
|||||
| 325547 Return |
Error message in the Invalid Condition dialog box may overflow text region. When debugging and a breakpoint with an invalid condition is hit, the Invalid Condition dialog box opens. Replacing the condition with a longer but still invalid condition causes the error message to be longer, but the dialog box does not expand to accomodate the longer message. Workaround: N/A
|
|||||
| 325813 Return |
The Replace File in Project option crashes the development environment if a file with same base name is specified. Replacing a file in the Project Tree with another file that has the same base name using the Replace File in Project context menu option causes the development environment to crash. Workaround: N/A
|
|||||
| 326195 Return |
The active function panel is incorrectly detected when multiple function panels are being edited in the Function Panel Editor window. If you create multiple function panels in the Function Panel Editor and attempt to add a control to a panel other than the original, the control is not always added to the selected function panel. Workaround: Select the original function panel then the function panel that you want to create a control on before adding a control.
|
|||||
| 326378 Return |
LabWindows/CVI crashes when a long condition is entered in the Condition text field of the Invalid Condition dialog box. When you are debugging and hit a breakpoint with an invalid condition, LabWindows/CVI launches the Invalid Condition dialog box. If you enter a new condition that is very long and click Replace, the development environment crashes. Workaround: N/A
|
|||||
| 329410 Return |
Unable to resize Attribute Browser and User Interface Browser back after resizing them very near to the right side of the User Interface Editor. N/A Workaround: Close and reopen LabWindows/CVI.
|
|||||
| 329411 Return |
User interface control labels appear to resize when switching from Windows XP to Windows Vista or Windows 7. The font size of the labels actually remains the same, but the rendering of the labels is handled differently in Windows XP than it is in Windows Vista and Windows 7. The larger label size causes the controls to resize. Workaround: For the labels, disable the Size to text option in the Label Appearance section of the Edit Control dialog box.
|
|||||
| 331365 Return |
UIR save version can change when saving the project file or workspace file. A UIR file that is saved for an older version can change to the current version when the project or workspace is saved with File»Save As. Workaround: N/A
|
|||||
| 331714 Return |
Saving a UIR file while editing a text field in the Attribute Browser marks the UIR file as changed. The UIR file is not saved, but displays that the file has changes since the last save in the Project Tree and in the File menu. Workaround: N/A
|
|||||
| 332654 Return |
Changing a panel's width or height from the Attribute Browser doesn't update corresponding workspace status bar values. The panel size values displayed on the right side of the workspace's status bar do not update when the panel's width and height attributes are modified from the Attribute Browser. Workaround: Modify the panel width and height from the Edit Panel dialog box.
|
|||||
| 332770 Return |
The control or panel constant name in the Workspace status bar does not update when a panel or control is selected and the user moves another panel or control. N/A Workaround: N/A
|
|||||
| 332772 Return |
Workspace status bar displays outer frame width and height when resizing panel. When resizing a panel in the User Interface Editor, the status bar displays both the previous width and height and the new width and height. Both the previous and new values are calculated based on the outer selection frame rather than the actual panel width and height. Workaround: N/A
|
|||||
| 333069 Return |
Workspace status bar and property browser panel width and height are not updated when you undo a panel resize or cut/delete a panel.. If you resize a panel in the User Interface Editor, the workspace status bar and the property browser update with the new panel width and height. If you then undo the resize, the status bar and the property browser do not update the width and height to the old values. Workaround: N/A
|
|||||
| 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
|
|||||
| 334352 Return |
The registry key used to locate the just-in-time debugger may be removed or point to an incorrect version. When installing LabWindows/CVI, the just-in-time debugger is installed to the \bin directory of the LabWindows/CVI installation directory and a registry key is modified to point to that version of the just-in-time debugger. Installing multiple versions of LabWindows/CVI in reverse version order or uninstalling LabWindows/CVI may cause the registry key to point to the incorrect location or to be removed. Workaround: If the registry key is removed or doesn't match the version of LabWindows/CVI you want to use for debugging, you can complete the following steps: 1) Open LabWindows/CVI. 2) Select Tools»Register Just-In-Time Debugger.
|
|||||
| 334681 Return |
Setting the Label text in the Edit Tree dialog box to a string greater then 250 characters can crash LabWindows/CVI. N/A Workaround: N/A
|
|||||
| 334683 Return |
The window number is displayed in the title bar of maximized windows when switching between tabbed and non-tabbed workspace. N/A Workaround: N/A
|
|||||
| 334917 Return |
LabWindows/CVI evaluates the Drivers & Components dependencies before rebuilding the project. When you create a distribution, LabWindows/CVI automatically checks the dependencies of your project outputs to recommend which drivers and components need to be included. This check occurs before checking if the project needs to be rebuilt. If changes have been made to the project since it was last built, this can result in an inaccurate list of driver and component dependencies. Workaround: Rebuild the project before creating a distribution configuration.
|
|||||
| 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
|
|||||
| 335241 Return |
The Workspace status bar disappears in the Source Editor after opening a project. Opening an existing project while a source file is already opened and unsaved causes the status bar to disappear. Workaround: If you open another file in the development environment, the status bar reappears.
|
|||||
| 335299 Return |
Multiple calls to ClipboardPutBitmap in a multithreaded application causes temporary hang. Calling the ClipboardPutBitmap function from a thread other than the main thread can cause a temporary hang.Workaround: N/A
|
|||||
| 335358 Return |
Using the bit shift operator multiple times on the same line of code produces incorrect results for 64-bit integers in a 32-bit application. This issue occurs when the result of one bit shift is used for another bit shift in the same line of code. For example: unsigned int a = 1, b = 62; unsigned long long result = 1ULL << a << b; Workaround: Separate the two bit shift operations into two separate lines of code.
|
|||||
| 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
|
|||||
| 318253 Return |
False positive user protection error when using an Interface to Win32 API struct. N/A Workaround: Refer to the Disabling User Protection section in the LabWindows/CVI Help. Access this section through the Table of Contents by selecting Programmer Reference»LabWindows/CVI Compiler Overview»User Protection»Disabling User Protection.
|
|||||
| 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
|
|||||
| 332690 Return |
The Source Window background is not painted gray when a non-tabbed workspace is opened. If the Show tabbed Workspace option is disabled and you open LabWindows/CVI, the background of the Source Window is painted partially white. Moving windows across the white region causes them to be painted gray. Workaround: N/A
|
|||||
| 333287 Return |
Cursor does not change back to arrow after operating the splitter in the Watch Window while debugging. This occurs only when debugging an application and execution is not suspended. Similar behavior occurs for both the vertical and horizontal splitters. Workaround: N/A
|
|||||
| 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
|
|||||
| 333578 Return |
The Attribute Browser Width field doesn't coerce the value to the minimum control width. If a value is entered in the Width field in the Attribute Browser for a control with a minimum width and the value is smaller than the minimum Width, the value is not coerced to the minimum. The coercion does occur for the Height property. The actual Width of the control is correctly coerced to the minimum width. Workaround: N/A
|
|||||
| 333580 Return |
The selection around the control does not redraw after setting a field from the Attribute Browser that changes the control size. N/A 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.
|
|||||
| 333983 Return |
Non project C files loaded by function panels are not unloaded when switching projects. When loading a project or switching the active project in a workspace, the function panels that were explicitly loaded by the previous project (not the dependency Function Panels) are unloaded, but the corresponding non project C files remain linked. Workaround: Restart LabWindows/CVI.
|
|||||
| 334574 Return |
Installing multiple versions of LabWindows/CVI on the same system can cause the wrong versions of the LabWindows/CVI Help to be associated with the development environment. N/A Workaround: N/A
|
|||||
| 334920 Return |
Corners of Source Editor windows are painted black in non-tabbed Workspace when opened. When opening a workspace that has the Show Tabbed Workspace option disabled and at least one source code window open, the top corners of the Source Editor windows are painted black. Workaround: N/A
|
|||||
| 335301 Return |
Disabling tabbed workspace doesn't restore windows to their original unmaximized state. N/A Workaround: N/A
|
|||||
| 335499 Return |
Unmaximizing windows after loading a workspace leaves inactive windows without a number in front of the title in the title bar. N/A Workaround: N/A
|
|||||
| 329405 Return |
Numeric control radix does not resize with control text size. N/A Workaround: N/A
|
|||||
| 342459 Return |
Installing LabWindows/CVI 2009 or 2010 when a later version is already installed may cause the installation to fail. If the later version already installed on the system was installed with the IVI Installer Creator component selected in the installer feature tree, then installing LabWindows/CVI 2009 or 2010 will fail. Workaround: Rerun the installer for the later version of LabWindows/CVI or modify the installation through Add or Remove Programs in Windows XP or Programs and Features in Windows Vista/7. Then remove the IVI Installer Creator feature from the installation. Once the feature is removed, install LabWindows/CVI 2009 or 2010. If the feature is needed in the later version, you can add it to the installation using the same process you used to remove the feature.
|
|||||
| 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.
|
|||||
| 336341 Return |
Cannot assign Interface to Win32 API function GetProcAddress to a function pointer without a type cast. The following code results in a "Operands of = have illegal types" compile error: #include <windows.h> int __stdcall (*my_FP)(int x, char y[], char z[], char *m, int g, char A[], char B[]); my_FP = GetProcAddress(0, "DLL_FUNCT");Workaround: Create a typedef for the function pointer and use it to cast the return value of GetProcAddress.
|
|||||
| 345272 Return |
Tree control may crash when more than 200,000 items are inserted. Workaround: N/A
|
|||||
| 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
|
|||||
| 358837 Return |
The alloca function is not defined for the clang third party compiler in a 64-bit configuration. Workaround: Add #define alloca __builtin_alloca after including ansi_c.h.
|
|||||
| 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.
|
|||||
| 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
|
|||||
| 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.
|
|||||
| 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
|
|||||
| 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
|
|||||
| 342838 Return |
Loading a project from LabWindows/CVI 2009 or earlier reverses the value of the LoadExternalModule option in the Target Settings dialog box. The default value for this option was changed from true to false in LabWindows/CVI 2010. Workaround: N/A
|
|||||
| 344033 Return |
Sweep Line Color attribute for a strip chart is not saved when the UIR is saved. Workaround: Modify the value of the Sweep Line Color attribute (ATTR_SWEEP_LINE_COLOR) programmatically.
|
|||||
| 344688 Return |
Workspace status bar does not update properly with various Function Tree Editor user actions. Workaround: N/A
|
|||||
| 344947 Return |
The LabWindows/CVI development environment crashes when you cut, copy, or delete a function panel tree item if it is the active item, but not selected. The active tree item has a dotted border around it but is not highlighted in blue. Workaround: N/A
|
|||||
| 345003 Return |
Deselecting a control by clicking the mouse in the the User Interface Editor's white space does not update the Workspace status bar to show that no control is selected. Workaround: N/A
|
|||||
| 345074 Return |
Passing an incorrect panel attribute to the GetPanelAttribute function causes a general protection fault.For example, passing ATTR_LABEL_TEXT to the GetPanelAttribute function will cause a crash because it is not a valid attribute of a panel.Workaround: N/A
|
|||||
| 345185 Return |
When switching to a different UIR tab, the User Interface Editor status bar does not update to reflect that the second UIR file does not have any controls or panels selected. Workaround: N/A
|
|||||
| 346432 Return |
Child panels in a tab control do not resize when the tab is resized and Scale Contents on Resize is enabled. Workaround: N/A
|
|||||
| 347326 Return |
The digital graph control does not limit the Line Label and Bus Label values string size to 255 characters. Workaround: N/A
|
|||||
| 348249 Return |
The LabWindows/CVI Conversion Wizard may fail with an error if LabWindows/CVI project contains an FP file. Workaround: Remove the FP file from the LabWindows/CVI project before using the LabWindows/CVI Conversion Wizard to convert a LabWindows/CVI project to a Visual C++ project.
|
|||||
| 348756 Return |
The CVI GUI Localization Utility will not advance to the Right Y Axis of strip charts if the Next button is clicked. Workaround: Select the Right Y Axis item with the mouse.
|
|||||
| 348758 Return |
The Clear Translations menu item does nothing in the CVI GUI Localization Utility. Workaround: N/A
|
|||||
| 349644 Return |
ActiveX controls cannot be selected in the User Interface Editor with a mouse click if the control is dimmed. Workaround: N/A
|
|||||
| 349930 Return |
Mouse tracking is not aborted during a mouse click event if the control callback causes the panel to lose focus. For example, a string control handles the EVENT_LEFT_DOUBLE_CLICK event and during the callback the panel loses focus by displaying a popup dialog. When the popup dialog is closed, the mouse will continue to highlight the string control text. Workaround: N/A
|
|||||
| 350416 Return |
ExcelRpt_WriteDataFromTableControl function does not support combo box, ring, or button cell types.Picture cell types are also not supported, but Microsoft Excel does not have an equivalent cell type to accept the conversion. Workaround: N/A
|
|||||
| 350848 Return |
The font used in some parts of the LabWindows/CVI environment may not be readable on a Japanese OS. This illegible font is a result of the font size being too small. Workaround: Increase the font size in the Environment Font Preferences dialog box (Options»Font).
|
|||||
| 352341 Return |
Status bar does not always change color on OS theme change. Workaround: N/A
|
|||||
| 352775 Return |
Sorting an empty column in the Modules window causes an error. The LabWindows/CVI environment will throw the "The index passed is out of range" error when a column is selected that has no items in it. This can happen when you are not debugging because the modules list is empty. Workaround: N/A
|
|||||
| 355436 Return |
The InetTelnetOpen function limits connections to 100. If you exceed this limit, a non-fatal run-time error occurs. Workaround: N/A
|
|||||
| 290770 Return |
Popup dialogs appear in the same location where they were located the last time the dialog appeared in that process. The file dialog will appear centered in the monitor of the active panel the first time a process with this name is executed. From this point on, it will remember where you have moved it and it will always appear in that same location. Workaround: N/A
|
|||||
| 309845 Return |
Tree control tooltip does not use the character set of the tree. Hovering over an item with the mouse shows a tooltip with the item label if the label is longer than the visible area of tree control. That tooltip uses the native character set instead of the character set specified for the tree control. Workaround: N/A
|
|||||
| 315800 Return |
The Find in files search will display a warning if a line it attempts to search is greater than 1024 characters. Lines greater than 1024 characters are truncated at 1024 characters and the rest of the line is not searched. The warning does not provide any information on which file is causing the problem. Workaround: N/A
|
|||||
| 333273 Return |
Using column selection mode in the Source window over a collapsed region of code will cause the region to be improperly selected. Workaround: N/A
|
|||||
| 333324 Return |
Function panel controls in a disabled function may not be dimmed when the function panel is reopened for editing. Workaround: N/A
|
|||||
| 334682 Return |
Deleting a column from the Edit Columns/Cells dialog box does not set the Label field to the value of the active cell. Workaround: N/A
|
|||||
| 335556 Return |
The Word Report WordRpt_GoToCell function will always go to the first column when used in a Microsoft Word 2007 file or later.Workaround: Load an existing file saved as a Word 97-2003 document. Or, use the WordRpt_WriteToCell function with an empty string instead of the WordRpt_GoToCell function.
|
|||||
| 335717 Return |
The right scroll bar of the Watch window is clipped on the right side by a few pixels. Workaround: N/A
|
|||||
| 335805 Return |
Calling the ListCompact function with a preallocated empty list causes the list structure to become corrupted. Workaround: N/A
|
|||||
| 336312 Return |
Calling the GetCtrlVal function for the picture ring control may cause an "Assertion failed" error in the Event Viewer if the picture ring data type is set to " string (char *)".Workaround: Use "int" as the data type for the picture ring control then use an enum or switch statement to reference the desired string.
|
|||||
| 336446 Return |
Entering more than 255 characters into the Line Label or Bus Label fields of the Edit Digital Graph dialog box will cause the LabWindows/CVI environment to crash. Workaround: N/A
|
|||||
| 336721 Return |
Switching the active application while a control is being moved by the mouse causes the selection outline to not be undrawn. This behavior occurs if you press <Alt-Tab> while dragging a control. Workaround: Minimize and then maximize the LabWindows/CVI environment to remove the drawing errors.
|
|||||
| 337804 Return |
Changing the label of a tree item from the Label control or the Quick Edit Window does not update the corresponding entry in the Default Index option for that tree item. Workaround: N/A
|
|||||
| 337953 Return |
The LED control is rendered poorly when using default size. The default size of 20x20 pixels causes the LED to look more like an octagon than a circle. Workaround: Adjust the size of the LED to a different size. 17x17, 19x19, and 21x21 pixel sizes are recommended.
|
|||||
| 338093 Return |
Not moving the mouse when using Zoom to rectangle mode triggers EVENT_ZOOM with ZOOM_RESTORE for the eventdata1 parameter of the callback.Workaround: N/A
|
|||||
| 340111 Return |
Selecting the "Install LabWindows/CVI Run-Time Engine in the application directory" checkbox option in the Edit Installer dialog box does not work for 64-bit distributions. The LabWindows/CVI Run-Time Engine DLL files will be placed in the system32 directory instead of the application directory. Workaround: N/A
|
|||||
| 340396 Return |
When moving a tree control, the tree item being edited will not move with the tree. This behavior can occur if the tree is connected to a splitter that is set to move the control. This will also occur in the Attribute Browser if the LabWindows/CVI environment is resized from the right side of the window. Workaround: N/A
|
|||||
| 341151 Return |
Workspace folders with very long names can cause the LabWindows/CVI environment to crash when loading or saving. Workaround: Avoid workspace folder names with over 100 characters.
|
|||||
| 341569 Return |
The index counts in the Default index option can have the wrong value if items are inserted in the tree out of order. Workaround: N/A
|
|||||
| 341708 Return |
Inserting a tree column in Edit Columns/Cells dialog box does not update the currently selected column. This behavior will cause a mismatch between the Label field and the currently selected item. Workaround: N/A
|
|||||
| 342048 Return |
Typedefs with names that contain "char" are converted to "LPSTR" when generating an ODL. For example, a typedef named mychar is converted to myLPSTR. This will cause an error when the ODL is compiled using MIDL.Workaround: Avoid typedefs that contain "char" in the name.
|
|||||
| 343989 Return |
Some Programmer's Toolbox functions do not support Lab Style controls. The SizeRingCtrlToText, ConformCtrlBitmapToPanel, and RecessAllCtrlFrames functions do not support Lab Style controls.Workaround: N/A
|
Document last updated on 7/31/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/).