The following items are known issues in LabVIEW NXG 2.1 Web Module sorted by Category.
ID | Known Issue | |||||
---|---|---|---|---|---|---|
Controls and Indicators | ||||||
663972 Return | Error messages from the HTTP Client API are truncated Workaround: Use the "Explain Error" method to receive the full message
| |||||
664047 Return | Internal error when creating an I64 ring with multiple items A JavaScript error occurs when adding multiple items to a Ring Control with an I64 representation Workaround: N/A
| |||||
665293 Return | Selecting a custom color for a plot on a Chart does not properly update the plot's color Workaround: N/A
| |||||
666046 Return | Radio Button Group does not resize when additional Radio Buttons are added Workaround: N/A
| |||||
666287 Return | Warning when copying a Graph from a VI's Diagram to a Web VI's Diagram When you copy a VI's Diagram contents and paste them on a Web VI's Diagram, a warning will appear if one of the items is a Graph indicator. Workaround: Delete the graph terminal and create a new Graph in the Web VI
| |||||
666581 Return | Dragging multiple arrays into a tab control can cause visual issues Workaround: Save the Web VI and reopen it, or drag a single element into the tab at a time
| |||||
666615 Return | A JavaScript error occurs when running a Web VI that uses a Queue reference inside of a Cluster Workaround: N/A
| |||||
666971 Return | A JavaScript error occurs when using a Data Grid on a Tab Control with paging enabled. If a Data Grid with paging enabled is placed on a tab that is not the default tab, a JavaScript error will occur when the tab is selected Workaround: N/A
| |||||
667678 Return | Error clusters always display information in the source string even if no error occurred Workaround: N/A
| |||||
669498 Return | Data Grid headers fail to render when running a Web VI or built Web Application Workaround: N/A
| |||||
External Code | ||||||
673324 Return | Adding items to the FrontPanelCanvas tags in the HTML panel always places the new items at the top of the section Because the items that are added are always at the top of the section, the content that is added will always appear behind the content that LabVIEW NXG creates Workaround: Set the z-index property for the item that is being added
| |||||
Functions, VIs, and Express VIs | ||||||
664268 Return | VI snippets do not create controls on the Panel when placed in a Web VI Workaround: N/A
| |||||
666182 Return | When attempting to create a sub VI from code on a Web VI, you can only create a sub Web VI Workaround: N/A
| |||||
669020 Return | String to Number functions may return incorrect values when converting to I64 or U64 data types in Web VIs When converting from strings to 64-bit numbers, the String to Number functions (Decimal String to Number, Hex String to Number, etc.) can return unexpected results Workaround: N/A
| |||||
671454 Return | Providing a username and password when a cross-origin request results in a 401 has varying behavior between browsers. In the LabVIEW NXG editor this will result in a timeout. Workaround: N/A
| |||||
659068 Return | Creating a Web VI in a project results in a broken run arrow on the Web VI Workaround: When a Web VI is created, it is targeted to the "This Computer" target. Web VIs must exist in a Web Application (application targeted to a Web Server target) in order to run. Create a Web Server target in SystemDesigner, then create an application on the target and add your Web VI to the application.
| |||||
681183 Return | In some cases code placed outside of a loop with no data dependencies on the loop will not run until the loop has stopped Workaround: N/A
| |||||
691224 Return | Case structures are unable to recognize " as a selector When a string selector is used, creating a case for the " character results in the default case running rather than the " case Workaround: Use an Equals primitive to check for the quote character instead of or in addition to the case structure
| |||||
LabVIEW Project | ||||||
667774 Return | The Output tab does not allow horizontal scrolling Workaround: Copy the text from the Output tab into another location and read the message there
|
Document last updated on 3/21/2018