Archived: Measurement Studio 8.6 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.


The following items are changes from Measurement Studio 8.5 to Measurement Studio 8.6.

If you have a Bug ID, you can search this list to validate that the issue has been fixed.


Bug Fixes in Measurement Studio 8.6

Bug IDFixed Issue
96837Fixed an issue where examples that reference .NET hardware class libraries cause Measurement Studio to prompt you to upgrade assembly references.
99334Fixed an issue where the .NET controls do not persist changes to their Cursor properties.
101538Fixed an issue where silently installing Measurement Studio to a custom directory fails.
105609Fixed an issue where the font size of annotation text in the ActiveX graph control decreases after rendering to a device context other than the screen context, such as a printer context.
107630Fixed an issue with the printed image quality when printing .NET controls that do not use 3D styles.
107860Fixed an issue where the PreferredSize property of the .NET legend control does not update when new items are inserted.
108205Fixed an issue where the ActiveX 3D graph sometimes draws too few edges around points on a surface plot. This causes the shapes of the areas surrounding some points to be unnecessarily different than shapes of the areas surrounding other points.
113612Fixed an issue where non-visible plots in .NET graph controls incorrectly continue to affect axis ranges when using AutoScaleVisible options.
114942Fixed an issue where Measurement Studio .NET ControlArray-derived controls do not show focus when you select or tab to them.
118146Fixed an issue where Visual Studio generates an unhandled exception when you close the Designer window for a user control that contains a Measurement Studio control.
118411Fixed an issue where panning the scatter graph results in the plot looking distorted.


Glossary of Terms


  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on  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).