This document contains the <product> <version> known issues that were discovered before and since the release of <product> <version>. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.
Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community.
This document contains all known issues for Measurement Studio Visual C++ support. 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:
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 category of issue, and sorted by the date the issue was added to the document. To view the issues organized by date, visit the document linked below:
Known Issues by Date
You can contact us through any of the normal support channels including phone, email, or the discussion forums. Visit the NI Website to contact us. If you are contacting NI in regards to a specific issue, be sure to reference the ID number given in the document to the NI representative.
The following items are known issues in Measurement Studio Visual C++ Support sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| Analysis | ||||||
| 133415 Return | The Analysis library calls the LoadLibrary function. Under most circumstances, it is unsafe to call LoadLibrary inside DllMain. Therefore, avoid calling any analysis functions inside DllMain.Workaround: N/A
| |||||
| DataSocket | ||||||
| 134358 Return | Disconnecting a Visual C++ Datasocket object sometimes results in a crash. This can happen if the Datasocket objects are wrapped in a class that exposes connect and disconnect methods. If multiple instances of these classes are instantiated, and then one of the objects is deleted before disconnecting all the Datasocket connections, the final call to Disconnect will crash.Workaround: Disconnect all instances before deleting any of the objects
| |||||
| Hardware Libraries | ||||||
| 33154 483FFE00 Return | The Parameter Assistant does not always show NI-VISA resources or NI-488.2 boards. The Parameter Assistant does not show NI-VISA resources or NI-488.2 boards if only Measurement Studio Visual C++ support is installed. Workaround: Install Measurement Studio .NET language support.
| |||||
| Licensing | ||||||
| 133318 Return | Measurement Studio controls might exhibit evaluation behavior. If you have installed Measurement Studio 8.5 on a machine that has earlier versions of the Measurement Studio user interface and 3D graph controls and then uninstall Measurement Studio 8.5, the controls might exhibit evaluation software behavior for 30 days. Note: Applications that install earlier versions of the Measurement Studio user interface and 3D graph controls include ComponentWorks 2.0, Measurement Studio 1.0 and later, and LabVIEW 6i and later. Workaround: Use the Measurement Studio ActiveX License Fixer Utility located on your CD in the ActiveX License Fixer Utility folder to fix this problem.
| |||||
| 257172 Return | If you have Measurement Studio 2010 and an earlier version installed on the same machine, Visual C++ code generation wizards might show a licensing dialog in the earlier version. Although the licensing dialog is shown, the code will still be generated if you contiue to evaluate Measurement Studio 2010. Workaround: Activate Measurement Studio 2010.
| |||||
| Product Documentation | ||||||
| 119969 Return | The Document/View Architecture in Visual C++ Test and Measurement Applications topic link is broken. Selecting the Document/View Architecture in Visual C++ Test and Measurement Applications topic in the Measurement Studio Help Table of Contents returns a page requesting a new info code. Workaround: N/A
| |||||
| 133222 451EGFBK Return | Windows Vista does not support use of help files with a .hlp file extension, including What's This? help. Workaround: If you want to view .hlp files, you must download and install the WinHlp.exe program from the Microsoft Download Center.
| |||||
| 133327 Return | In Visual C++, Measurement Studio user interface and 3D graph controls have What's This? help available, unless you are running Windows Vista. All code samples in the What's This? help are in Microsoft Visual Basic 6.0 syntax. Workaround: N/A
| |||||
| 133328 Return | In Visual C++, the What's This? help question mark is not always displayed. Workaround: In Visual C++, the What's This? help question mark that usually appears at the top right corner of a property page is not displayed until you right click an item in the property pages for a Measurement Studio control and choose to view What's This? help.
| |||||
| 133331 Return | Accessing the Help button in Visual C++ does not always show Measurement Studio help. Measurement Studio Visual C++ user interface and 3D graph control property pages include a Help button. However, you cannot use the button to access the NI Measurement Studio Help. Workaround: To access the NI Measurement Studio Help, click Start?All Programs?National Instruments?Measurement Studio?Measurement Studio Documentation, or from Visual Studio, select Help?Contents to view the Visual Studio table of contents, in which the NI Measurement Studio Help is listed.
| |||||
| 133386 Return | Measurement Studio Visual C++ properties that are defined by get and set methods do not show help in the Object Browser. Workaround: Refer to the NI Measurement Studio Help to view the help for these properties.
| |||||
| User Interface | ||||||
| 116253 Return | Programmatically changing the background color of a CWNumEdit control that has hidden increment/decrement buttons does not change the background for the entire control until you redraw it. Workaround: You can redraw the control by programmatically toggling the Enabled property of the CWNumEdit control after the background color has been updated.
| |||||
| 116288 Return | Resizing the font of the CWNumEdit control causes the text to flicker before it updates. When resizing the font of the CWNumEdit ActiveX control, the text flickers back to the default size momentarily and then updates. This behavior occurs in Visual C++ and Visual Basic 6 but does not occur in .NET. Workaround: N/A
| |||||
| 133392 Return | In Visual C++, if you have Measurement Studio windowless controls and any windowed controls together on an MFC dialog box, tabbing through the dialog box skips all windowless controls. Workaround: N/A
| |||||
| 133421 Return | Measurement Studio Visual C++ controls do not support being hosted in HTML dialogs. HTML dialogs use the CDHtmlDialog base class.Workaround: N/A
| |||||
| 133422 Return | The wrappers that Visual C++ generates for the Measurement Studio ActiveX controls are incomplete. Visual C++ generates wrappers only for the top-level objects in the controls. This causes some Visual C++ generated wrappers to produce compile errors. Workaround: N/A
| |||||
| 132143 Return | CNiNumEdit and CNiAxis error messages and documentation do not indicate that they support only absolute time and not time spans. CNiNumEdit and CNiAxis do not support time span values. Consequently, time values greater than "23:59:59"(hh:nn:ss) are invalid. Documentation and error messages do not describe this limitation. Workaround: N/A
| |||||
| 130937 Return | Dotted lines in ActiveX controls are printed as solid lines in some cases. GDI draws the dotted lines as solid if the width of the line is greater than 1. While printing a control, a metafile is created which normally involves scaling of the control and consequently scaling of the width of the line. This makes the width of the line greater than 1 and the print will have a solid line instead of a dotted line. Workaround: There are two workaround options:
| |||||
| 136196 Return | The gridlines (ticks) do not invert when the Inverted checkbox is selected on the Range tab of the CWGraph3D Properties dialog box. Workaround: N/A
| |||||
| 129864 Return | ControlImage and ControlImageEx may not fill multiple annotations on the CWGraph correctly. The annontations will not be filled correctly if the fill color or line color does not change. Workaround: Increase the line width to fill the annotation
| |||||
| 138093 Return | Changing the axis range on a CWGraph 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.
| |||||
| 143046 Return | The clipping region of the CWGraph changed between Measurement Studio versions 8.1.2 and 8.5 to use the plot bounds instead of the graph bounds. Workaround: N/A
| |||||
| 151406 Return | Setting the annotation style of a CWGraph to Range or Half Space causes the numbering to disappear for the X and Y axes. Workaround: N/A
| |||||
| 247775 Return | Measurement Studio .NET controls do not work in the MFC CWinFormsControl control. Workaround: Host Measurement Studio .NET controls in a .NET UserControl, and then use the UserControl in the CWinFormsControl MFC control.
| |||||
| 256349 Return | Zooming in multiple times on the ActiveX CWGraph can result in a hang in the application. Workaround: N/A
| |||||
| 282772 Return | Plotting many data points that contain NaN values may result in broken plot lines on the CWGraph. The decimation algorithms in the CWGraph do not correctly account for NaN values. Decimation does not happen until there are more than approximately five times as many points as there are pixels in the width of the plot area. Workaround: N/A
| |||||
| Utility Classes | ||||||
| 182150 Return | The Visual C++ VectorMatrix streaming example displays errors when the "Save to Binary File" button is pressed. Workaround: N/A
| |||||
| 182154 Return | The Visual C++ RegistryExplorer example may cause an access violation exception when trying to delete a registry key. Workaround: N/A
| |||||
| Visual Studio Integration | ||||||
| 127067 Return | Measurement Studio Support for Visual Studio 2005 Visual C++ examples do not compile when upgraded to Visual Studio 2008. If you upgrade a Visual Studio 2005 VCNET example or to Visual Studio 2008 by opening the Visual Studio 2005 solution in Visual Studio 2008, the upgraded application will not compile. The application will not compile because National Instruments defines the minimum system requirement through the symbol _WIN32_WINNT, which is set to 0x0400 (WINNT). This value conflicts with the SDK 6.0 default value of _WIN32_IE, which is used by Visual Studio 2008 Visual C++.Workaround: You should make the values of _WIN32_WINNT and _WIN32_IE compatible for usage with SDK 6.0. To do this, either increase the value of _WIN32_WINNT to 0x0500 (Win2k) or decrease the value of _WIN32_IE to a value <0x0601.
| |||||
| 133416 Return | If you have created a Visual C++ Console Application and are linking statically to MFC, you may encounter LNK2005 and LNK1169 errors. This problem happens when MFC static libraries and CRT static libraries link in the wrong order. To correct this problem, ensure that the #include <afx.h> statement is the first include statement in the generated stdafx.h header file. For more information, refer to Microsoft Knowledge Base Article 148652.Workaround: N/A
| |||||
| 156506 Return | The Microsoft C++ Add Variable wizard throws a script error when Internet Explorer 8 is installed. This is a bug that has been reported to Microsoft. Workaround: Microsoft has now released a security update that fixes this issue. Information about the security update can be found here.
| |||||
Document last updated on 8/25/2011