• In LabVIEW 7.x and earlier, when you wire an error cluster to a Case
structure, the True case becomes the Error case and the False case
becomes the No Error case. In LabVIEW 8.0, when you wire an error
cluster to a Case structure, the True case becomes the No Error case
and the False case becomes the Error case.
When you drop the Compound Arithmetic function from the Numeric
palette, the default mode is Add. When you drop the Compound
Arithmetic function from the Boolean palette, the default mode is OR.
• In LabVIEW 7.x, if LabVIEW cannot find a VI, you must replace the
missing VI with a VI of the same name. In LabVIEW 8.0, you can
replace a missing VI with a VI of any name. LabVIEW replaces all
instances of the missing VI with the VI that you select.
• You can configure when LabVIEW loads a subVI. Right-click a subVI
and select Call Setup from the shortcut menu to display the VI Call
Configuration dialog box. This shortcut menu item is available only
calls—not for functions, Express VIs, polymorphic VIs, or
an application instance that does not support VI Server calls, such as
PDA and FPGA targets. If you have a large caller VI, you can save load
time and memory by selecting the Load and retain on first call option
in the dialog box. When you select this option, the subVI does not load
until the caller VI needs it, and you can release the subVI from memory
after the operation completes.
Great finds Ben. 🙂 Another is the Find and replace you just posted in a different thread. Lots of this stuff really enhances the usability of the product, but gets buried far down the list of marketing bullets, particularly in a release as large as LabVIEW 8.0.
The ability to choose a VI of a different name when something can't be found on load is extremely useful, but you also need to be a little more careful now - if you pick the wrong VI and then save (especially if the wrong VI you picked has the same connector pane) you can find yourself in a world of hurt. As always, pay attention when you see the "The VI expected to be at location X was loaded from location Y." 🙂