Showing results for 
Search instead for 
Did you mean: 

Monthly Bugs, November 2018

Continued from the October 2018 bug thread


The posting rules are as always:


  • Each post here should only contain a brief description of a bug, together with a link to the thread where it is being discussed.
  • One post/bug!
  • One bug/post!
  • No discussion of bugs. All discussions of a bug must take place in the original linked thread.
0 Kudos
Message 1 of 7
0 Kudos
Message 2 of 7

@altenbach wrote:

All buttons in the help generate script errors if the help is opened from within LabVIEW. (No CAR yet).

CAR now issued: CAR #718419

There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 3 of 7

Not so much a bug, but an error in the help text:


The Get Image invoke node (used to grab the image of a graph for example) is incorrectly stated as "Available in Real-time operating system" in LabVIEW 2018 (unlike in other versions), which is not the case (well, it might be available on some targets which support having a GUI, like cRIO-9030 for example, but on most systems the node will return an invalid reference error when running as an application on RT targets):



0 Kudos
Message 4 of 7

@Mads, please link to the thread where this bug (potential bug?) is being discussed.  This thread is just intended to aggregate other discussions taking place.  That being said, I too suspect that on Linux RT with the embedded UI enabled that this will function properly.

0 Kudos
Message 5 of 7

Continued here. This thread is now closed.

0 Kudos
Message 6 of 7

First mentioned here

LabVIEW stores information from for the Default data to import into the Application Builder rather than the Data from a Volume Licence Server when a License is checked out from the Volume License Server.


I understand a CAR is forthcoming.  Not a BIG problem until you start deploying a HAL MAL with ppls.  Those builds should have the right (C) info 😉

"Should be" isn't "Is" -Jay
0 Kudos
Message 7 of 7