G Web Development Software 2022 Q3 Known Issues

Overview

This document contains the G Web Development Software known issues that were discovered before and since the release of G Web Development Software 2022 Q3. 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; see Additional Resources.

Bug Number

Legacy ID

Description

Details

2051855

Components Licensed with the G Web Command Line Interface Cannot Be Used

G Web Development Software includes a Command Line Interface (CLI). One of the CLI operations is "applylicensing," but if you use it to add licensing to a library component, that library cannot be used by G Web. G Web reports an error in dependency even when the license is activated.

Workaround:

Do not use the applylicensing command in the G Web Development Software CLI (Command Line Interface).

Reported Version:

G Web Development Software 2022 Q3

Resolved Version:

N/A

Added:

Jul 28, 2022

1894804

Unable to Use Addons with Hyphen in the Name

If you build a package/installer with a hypen in the name of the specification (.lvdist) file or in the display name for the package, then when you place contents from that installed package into a WebVI, the WebVI is broken.

Workaround:

Do not use hyphens in the distribution file name or display name.

Reported Version:

G Web Development Software 2022 Q1

Resolved Version:

N/A

Added:

Jul 28, 2022

1948960

WebVI Graph "Show Value on Hover" Does Not Match Axis Format

When a graph on a WebVI panel has a plot with the "Show value on hover" option enabled, the displayed value will not always match the display formatting used for the corresponding graph axis.

Workaround:

If possible, use graph cursors instead of the "Show value on hover" option.

Reported Version:

G Web Development Software 2022 Q1

Resolved Version:

N/A

Added:

Jul 28, 2022

Final Time Issue Listed

Issues found in this section will not be listed in future known issues documents for this product.

Bug Number

Legacy ID

Description

Details

1141236

Event Structure Does Not Execute Value Changed Case If Timeout Value Changed After Value (Signaling) Property Set

If a WebVI's diagram sets a control's Value (Signaling) property within the Timeout case of an Event Structure and then changes the Event Timeout to -1, the Event Case for the control's Value Changed event will not execute immediately. The event is queued, however. When another event is fired, the Event Structure will execute the Value Changed case, erroneously leaving the new event queued. 

Workaround:

After setting a control's Value(Signaling) property in the timeout case, set the Event Timeout to a positive number. Change to a timeout of -1 using the case for the Value Changed event.

Reported Version:

G Web Development Software 2021

Resolved Version:

N/A

Added:

Aug 12, 2021

Additional Resources

Explore Support Content and Product Documentation 

 

 

Ask the NI Community

 

 

Request Support from an Engineer

 

A valid service agreement may be required, and support options vary by country

 

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