Addressing Inconsistent Type Definition Behavior in LabVIEW 2014

Monday, September 15, 2014

In every LabVIEW release, the LabVIEW team works to address pain points and areas of confusion in LabVIEW. One change you might have missed in LabVIEW 2014 is improving the handling of default values in type definitions. Type definitions allow you to save a custom control so that it can be reused in multiple places in an application. When changes are made to the type definition, all instances of the control will automatically update to reflect those changes. In addition to data representation and appearance, type definitions also keep track of a set of default values.

LabVIEW 2013 and previous versions of LabVIEW were inconsistent in what happened to the default value of an instance when changes were made to its type definition – sometimes the default value of an instance was overwritten and sometimes it was preserved.

In LabVIEW 2014, in most cases the default values of each instance of a type definition are automatically preserved. When an instance can’t be automatically updated (for example, when a type-defined string control is changed to an enum), LabVIEW breaks the VI and dims the instance so you can right click on the element and open the new “Review and Update from Type Def.” dialog box. This will allow you to make sure you don’t lose track of a default value you have already customized.



Hopefully this new dialog and behavior will help you keep track of the default values in your type-defined instances and avoid a potentially frustrating debugging situation.

>> Learn more about new features and changes in LabVIEW 2014.