LabVIEW NXG 3.0 Known Issues by Date

Aperçu

This document contains known issues for the LabVIEW NXG 3.0 Application Software. 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. The LabVIEW 2018 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.

Fields

Each Issue appears as a row in the table and includes these fields:
  • Issue ID
  • Issue Title
  • Problem Description
  • Workaround
  • Reported Version - the earliest version of LabVIEW NXG in which the issue was reported
  • Resolved Version - version the issue was resolved or was no longer applicable
  • Date Added - the date the issue was added to the document (not reported date)


Document Organization

There are two versions of the known issues list available:

LabVIEW NXG Known Issues by Category
LabVIEW NXG Known Issues by Date

Please refer to Developer Zone Article "LabVIEW Known Issues Categories Defined" for an explanation of the categories and what types of issues are in each category.

Contacting NI

You can contact us by 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 this document. If you have feedback on this specific document, please contact NI on this NI Developer Zone post.

Known Issues by Date

The following items are known issues in LabVIEW NXG 3.0 sorted by Date.

482816 Selection in Array of Clusters of Arrays constant loses focus.
596295 Measurement Panel created for an array of task constants does not propagate name.
630075 IO constants cannot be resized when contained within a cluster connected to a G Type.
644397 Workbooks do not restore maximized after minimizing the environment window with a maximized workbook open.
599881 Empty folders in project don't show up in the files pane when opening a project
631907 Some keyboard shortcuts don't work with an AZERTY keyboard
643608 Right clicking on a tunnel of queue of numeric type shows the numeric palette
660805 Windows "line per notch" scroll wheel settings do not apply to NXG
662414 Error & Warnings Panel continuously expands and collapses after repeated pinning and unpinning
599434 Dynamic dispatch controls are not supported inside structures
605135 Some strings remain in English rather than localized language when converted to LabVIEW NXG
620473 Element names inside Typedef Clusters or Rings may not show localized names
641719 Projects with large file hierarchy error out during conversion with unclear error message
678830 Dictionaries are only found in specific language culture
706310 Shared Library Interface documents that use Type Definitions as the type for function parameters are broken following conversion
682314 Interop node claim VI is invalid if containing Python node
724916 Scan String for Tokens does not return a token count of -2 after reaching the end of a string



ID Known Issue
482816

Return
Selection in Array of Clusters of Arrays constant loses focus.
Selecting an array inside a cluster inside another array loses focus when hovering over another element of the top array. This makes it difficult to edit the items in the inner-most array.

Workaround: N/A

Reported Version: 1.0    Resolved Version: N/A    Added: 05/22/2017
596295

Return
Measurement Panel created for an array of task constants does not propagate name.
When a Measurement Panel is created from an empty task constant inside of an array, a new task will be generated for it and a name will be assigned. However, this name will not be automatically updated on the original task constant inside the array.

Workaround: Manually rename the task constant.

Reported Version: 1.0    Resolved Version: N/A    Added: 05/22/2017
630075

Return
IO constants cannot be resized when contained within a cluster connected to a G Type.
IO constants can be resized manually when contained within a cluster constant. However, IO constants cannot be resized once the containing cluster is connected to a G Type. The IO control in the G Type can be resized but this change is not reflected in any connected constants.

Workaround: Disconnect the cluster from the G Type, resize the IO constant, and then reconnect to the G Type.

Reported Version: 1.0    Resolved Version: N/A    Added: 05/22/2017
644397

Return
Workbooks do not restore maximized after minimizing the environment window with a maximized workbook open.
A maximized workbook window will minimize when the environment window is minimized. Restoring the environment window will also restore the workbook window but not in the maximized view.

Workaround: Maximize the workbook window manually after restoring the environment window.

Reported Version: 1.0    Resolved Version: N/A    Added: 05/22/2017
599881

Return
Empty folders in project don't show up in the files pane when opening a project
When you open a project with empty folders, those don't show up in the files pane.

Workaround: N/A

Reported Version: 1.0    Resolved Version: N/A    Added: 01/23/2018
631907

Return
Some keyboard shortcuts don't work with an AZERTY keyboard
The following shortcuts do not work properly when using an AZERTY keyboard:

Ctrl-' (Toggle the diagram grid on/off)
Shift-Ctrl-; (Toggle Smart Guides on/off)
Ctrl-[ (Set or delete Breakpoint)
Ctrl-] (Set or Delete Probe)
Ctrl-. (Abort )

Workaround: N/A

Reported Version: 2.0    Resolved Version: N/A    Added: 01/23/2018
643608

Return
Right clicking on a tunnel of queue of numeric type shows the numeric palette
For most data types, the right click menu from the queue terminals shows the palette queue. Right clicking on a tunnel of numeric type shows the numeric palette.

Workaround: Manually drop from the queue palette instead of right-clicking.

Reported Version: 1.0    Resolved Version: N/A    Added: 01/23/2018
660805

Return
Windows "line per notch" scroll wheel settings do not apply to NXG
The scroll wheel movement amount does correlate to the scroll size defined in the Windows mouse settings. For example there's no difference in the amount of block diagram scrolled whether the set to 1 line per notch or 10 lines per notch.

Workaround: N/A

Reported Version: 2.0    Resolved Version: N/A    Added: 01/23/2018
662414

Return
Error & Warnings Panel continuously expands and collapses after repeated pinning and unpinning
Normally, The Error & Warnings panel pops up when the mouse is hovered over it. In some cases, the Errors and Warnings window may expand and collapsed continuously after pinning and unpinning the Errors and Warnings panel.

Workaround: Click the tab.

Reported Version: 2.0    Resolved Version: N/A    Added: 01/23/2018
599434

Return
Dynamic dispatch controls are not supported inside structures
Placing a dynamic dispatch control inside of a structure provides the following error:
The run-time type is not propagated from dynamic dispatch input to dynamic dispatch output. You must ensure that there is a wire path that flows to all dynamic dispatch indicators.

Workaround: Remove the control from the structure and the error will clear.

Reported Version: 1.0    Resolved Version: N/A    Added: 02/26/2018
605135

Return
Some strings remain in English rather than localized language when converted to LabVIEW NXG
When setting a localized dictionary and converting from LabVIEW to LabVIEW NXG, some strings may remain in English. Specifically, strings that are labels instead of captions will appear in English

Workaround: Set a caption for controls prior to conversion or update text after conversion

Reported Version: 1.0    Resolved Version: N/A    Added: 02/26/2018
620473

Return
Element names inside Typedef Clusters or Rings may not show localized names
When looking at names of elements contained within a Typedef Cluster or Ring, the name may appear in English rather than the appropriate localized language.

Workaround: Close out of NXG and re-open. Open from the project.

Reported Version: 1.0    Resolved Version: N/A    Added: 02/26/2018
641719

Return
Projects with large file hierarchy error out during conversion with unclear error message
The conversion tool adds hierarchy to the project structure during conversion that extends the length of the file path. As a result, file paths can become too long for Windows and create a situation where the conversion utility cannot find files at paths that do not exist. This will result in the following error: Conversion could not find this file at specified path
The reason for the file not found is not clear in the action being made.

Workaround: Make shorter file paths initially so the added hierarchy doesn't extend beyond Windows file path limits

Reported Version: 1.0    Resolved Version: N/A    Added: 02/26/2018
678830

Return
Dictionaries are only found in specific language culture
Parent cultures will not find the dictionary even if the language matches the parent culture. As a result, localization will not happen.

Workaround: Place the dictionary into a language-specific folder, e.g. de-DE, de-CH, de-LI, etc

Reported Version: 2.0    Resolved Version: N/A    Added: 02/26/2018
706310

Return
Shared Library Interface documents that use Type Definitions as the type for function parameters are broken following conversion
Opening a LabVIEW Communications 2.0 project in LabVIEW Communications 2.1 that contains a Shared Library Interface document using Type Definitions as the type for function parameters are broken following conversion.

Workaround: After conversion, click on each affected function parameter and on the Item tab click the GType dropdown and select the correct GType from the list.

Reported Version: 2.1    Resolved Version: N/A    Added: 08/17/2018
682314

Return
Interop node claim VI is invalid if containing Python node
Interop nodes will fail to load a VI containing a Python node with the message "The VI at the specified path is invalid. Select a valid VI for the VI interop node"

Workaround: Create a VI and call the Python node inside of a subVI. If the node is not in the top-level VI, the Interop node will successfully load it.

Reported Version: 2.0    Resolved Version: N/A    Added: 10/25/2018
724916

Return
Scan String for Tokens does not return a token count of -2 after reaching the end of a string
This bug will likely manifest as a "hang", as the recommended use of this node is inside of a while loop. Following the recommended pattern, a while loop checking for a token count of -2 will never stop.

Workaround: If you are using a token count of -2 to stop your while loop, use the "offset past token" output instead. "offset past token" will return -1 when there are no more tokens in the string.

Reported Version: 3.0    Resolved Version: N/A    Added: 1/14/2019

Document last updated on 1/14/2019

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).