New Hidden Gems in LabVIEW 2019

[Darren]

In addition to the following hidden gems in LabVIEW 2019, there are several new (non-hidden) gems in Quick Drop/palettes that are generally useful for LabVIEW development. I suggest reading the LabVIEW 2019 Upgrade Notes (once they are posted) to learn more about those VIs. But for now, here are the new LabVIEW 2019 hidden gems:

1. Find Broken VIs in Project.vi (located in vi.lib/Utility/EditLVProj)
   Useful to run as a pre-flight to detect problems in your project source code before kicking off a very long build of an EXE, PPL, etc.
2. Commit All Source Only Changes.vi (located in vi.lib/Utility/EditLVProj)
   Loads a LabVIEW project from disk. Within the loaded project, the "source-only" setting on all VIs and libraries is suppressed. This means that anything loaded within the project will be marked as having unsaved changes if it needs to update due to LabVIEW version change, OS change, or any changes in dependencies. This VI will then save any VIs or libraries with changes, and optionally check out those files from source control.
3. New LabVIEW Class Data Type VIs (located in vi.lib/Utility/Data Type)
   There are two new hidden gems in the Data Type Parsing API that give you more information about LabVIEW class data types:
   • Get LabVIEW Class Default Palette Information.vi - Returns the default palette path.
   • Get LabVIEW Class Parent And Member VI Information.vi - Returns a type variant of the parent class, along with information about the member VIs of the class (name, path, access scope, and dynamic dispatch setting).
4. Hidden Gem Array VIMs (located in vi.lib/Array)
   We described several new Array VIMs in the examples folder in the hidden gems post from last year (see here). Many of these were moved into vi.lib/Array in LabVIEW 2019, including these:
   • Insert Into Sorted Array.vim
   • Search Sorted 1D Array.vim
   • Search Unsorted 1D Array.vim
   • Sort 1D Array.vim

Note that for LabVIEW 2019, there is not a new Hidden Gems package on the Tools Network. Version 1.0.0.10 continues to be the latest version.

[M.Lichtenheld]

Hi Darren,
its an old post, i know.
But regarding to 2.:
Why do we need to update all Project files when we change LV Version or OS?
I thought the LV Version or OS change will just effect the compiled code. And that is not in under version control.

[Darren]

---

@M.Lichtenheld wrote:
Hi Darren,
its an old post, i know.
But regarding to 2.:
Why do we need to update all Project files when we change LV Version or OS?
I thought the LV Version or OS change will just effect the compiled code. And that is not in under version control.

---

It's not required, but many LabVIEW teams like their code to be compiled and saved in the current editor version to improve load times, and to ensure that there aren't any issues with their code in the new version.