Control

The basic idea for Type Definitions and Strict Type Definition in LabVIEW is that they are custom controls (*.ctl file) that can be placed in any VI. When the *.ctl file is changed, every VI that uses that control will also be changed which eliminates the need to go change each VI yourself. When a type definition control is used, LabVIEW ensures that the data type is the same anywhere the control is used. A strict type definition is more restrictive and LabVIEW ensures that almost everything about the control remains the same

Type Definition
A Type Definition can have a different name, description, default value, size, color, or style of control, as long as the data type matches the master copy of the control. A type definition only identifies the correct type for each instance of a custom control. The type does not include things like data range for a numeric controls, or item names in a ring control. So if you change the data range on a numeric control or an item name on a ring control that are part of a type definition control, it will not change these properties on all instances of the control. However, if you change the item name in a type definition for an enumerated type (enum), all instances change as well, since the item name is part of the type for an enum. You can also use normal property nodes with type definitions as you would with a non-custom control

Strict Type Definition

A Strict Type Definition forces almost everything about the control to be identical, including its size, color, and appearance. Strict type definitions are more restrictive and unlike general type definitions, they define other values, such as range checking on numeric controls and item names on ring controls. The only flexibility to a strict type definition is the name, description, and default value which all can be different for separate instances of the same control. The only properties available for a strict type definition control are those that affect the appearance of the control such as Visible, Disabled, Key Focus, Blinking, Position, and Bounds. For example, if you have a strict type definition which is made up of a cluster of various controls, properties for each individual control would not be available. Only appearance properties for the overall custom control would be allowed.