Archived: LabWindows™/CVI™ 2010 SP1 Bug Fixes

NI does not actively maintain this document.

This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.

Overview



The following items are changes from LabWindows/CVI 2010 to LabWindows/CVI 2010 SP1. If you have a Bug ID, you can search this list to validate that the issue has been fixed.

Table of Contents

  1. Development Environment
  2. Performance
  3. User Interface
  4. Compiler
  5. Stand-Alone Applications and Distributions
  6. .NET and ActiveX
  7. Analysis
  8. Miscellaneous
  9. Related Links

 

Development Environment

Bug ID

Fixed Issue

Has Run-Time Impact?

299976LabWindows/CVI can corrupt files on some network shares when saving a file after deleting some of its contents.No
299674Pasting unicode data copied from the clipboard can cause a crash.No
295529Changing only the type of a custom configuration does not trigger a rebuild of your project.No
295228Add Watch Expression context menu item incorrectly dimmed in watch window.No
294443"Index out of range" error in Edit Columns/Cells dialog.No
294960Switching execution target and starting to debug project crashes LabWindows/CVI when a watchpoint exists.No
293875Debugging a project in an unnamed workspace results in duplicate save dialog boxes.No
292892The LabWindows/CVI Visual Studio wizards add the version-specific ProgramData include path incorrectly.No
291368Line numbers are missing from Standard I/O window.Yes
290057Copying a control from one panel to the other in the User Interface Editor can cause the Attribute Browser to display incorrectly.No
289945Selecting a .lib instead of a .dll from the Generate DLL Import Library file dialog box causes LabWindows/CVI to crash.No
288104Changing any environment option while in an untitled workspace results in an error.No
283634The LabWindows/CVI Visual Studio Conversion Wizard fails for some projects that reference National Instruments modular instruments drivers.No
282844LabWindows/CVI does not allow users to save files following an exception.No
282612Editing a menu associated with a panel on an unsaved UIR can cause LabWindows/CVI to crash.No
279028Enabling or disabling profiling does not trigger a rebuild of your project.No
277640The User Interface Browser may not update when Find UI Object is selected from a source file.No
258506The Attribute Browser Find text box might incorrectly filter attributes when double-clicking a control in the User Interface Browser.No
258505Selecting Create New File on a project folder results in an invalid file.No

 

Performance

Bug ID

Fixed Issue

Has Run-Time Impact?

 
285633LabWindows/CVI might crash if you create a panel with a very long title.No
302494Memory leak when using ATTR_COPY_ORIGINAL_DATA=0 and getting a scaled bitmap of a graph control.Yes
290737InetSendMail can crash if the To: field exceeds 250 bytes.Yes
283981Performance of many TDMS functions deteriorates more quickly than expected as total group and channel counts become very large.Yes
253304TDMS Files with very high channel counts might be slow to open.Yes

 

User Interface

Bug ID

Fixed Issue

Has Run-Time Impact?

284842The GetTableCellRangeVals and SetTableCellRangeVals functions do not work for string cell types in a 64-bit application.Yes
294725Adding or removing an item from a tree that is not in edit mode might, in rare circumstances, cause a crash.Yes
286688The menu text for a menu using a non-metafont rotates when a panel with Scale Contents on Resize enabled is resized.Yes
282946Right justified numeric controls can draw their text incorrectly.No
281083The y-axis name of a strip chart control might be drawn incorrectly when the y-axis autoscales.Yes
281082A strip chart legend may not be drawn correctly if it overlaps the strip chart plot area.Yes
280705You cannot enter numbers in scientific notation into numeric controls holding 64-bit integers.Yes
280320Table scroll bars do not redraw when scrolling a table with the keyboard.Yes
279916The defaultFileSpec parameter of the FileSelectPopup function does not work correctly.Yes
276443A tab inserted anywhere but the end of the list will use the wrong image.Yes
276442Displaying a file select popup panel from a panel with a tab control might disrupt the panel z-plane order.Yes
258827Block and sweep strip chart modes do not scroll properly.Yes
303247Strip chart x-axis divisions do not maintain proper spacing during scrolling.Yes
302870UI Localizer can crash when clicking Next on the last item of a tree control.No

 

Compiler

Bug ID

Fixed Issue

Has Run-Time Impact?

257782The Resource Tracking window does not track thread local variable handles.No
298184Non-Fatal UP errors can sometimes display with only the message %%s.Yes
275934Including the http.h Win32 API header file can result in missing function prototype compile errors.No
295530Watch points created for custom configurations might not work without modifications.No
258835Using clang 1.0 as your active release compiler might result in link errors if you include windows.h from more than one source file.No

 

Stand-Alone Applications and Distributions

Bug ID

Fixed Issue

Has Run-Time Impact?

292539Opening a distribution that was created in LabWindows/CVI 7.1 and earlier can cause a crash during conversion.No
292805An application whose installer includes only the Network Variable Support sub-item might not run correctly in a minimally configured target computer.Yes
292521An application whose installer includes only the Network Variable Support sub-item might run slower than expected in a minimally configured target computer.Yes
291813Distributions with .inf files fail to install after checking module dependencies.Yes
291452An application whose installer includes only the Standard Run-Time sub-item might run with a Mesa.dll could not be found error in a minimally configured target computer.Yes
290986A 32-bit application whose installer includes only the ActiveX Container Support sub-item might not run correctly in a minimally configured target computer.Yes
290386Uninstalling LabWindows/CVI distributions from some non-English operating systems fails.No
286606In 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.No
278742In a distribution, the path to the CHM help file for an ActiveX server file is incorrect.No

 

.NET and ActiveX

Bug ID

Fixed Issue

Has Run-Time Impact?

296663DIAdem automation example reports ActiveX error.Yes
296660ActiveX Iedemo example does not work with newer versions of IE.Yes
283042A LabWindows/CVI ActiveX server can crash while shutting down if there are open client connections to the server.Yes

 

Analysis

Bug ID

Fixed Issue

Has Run-Time Impact?

248829The function GaussHG returns NaN for X values less than 0.Yes
280209Calling IIRCascadeFiltering in a loop produces erroneous results.Yes

 

Miscellaneous

Bug ID

Fixed Issue

Has Run-Time Impact?

287394HTML and XML files generated from source code contain an extra asterisk for output parameters in function prototype.No
277253Non-void pointer types in function prototypes have an extra asterisk in the LabWindows/CVI help.No
258354CNVProcessIsRunning may incorrectly report that the process is running if the program is run as a startup program.Yes

 

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).