Type Definition: Difference between revisions

Revision as of 17:59, 2 January 2008

A type definition [TD] is a custom control (CTL) file that has been marked as a type definition.

Instances of the TD are linked to their definition. You cannot edit functional properties of TD's instances, but only visual properties. To change functional properties you have to edit their TD. All changes in a TD are propagated to all of its instances, when you save the TD or choose to 'apply changes'.

Type definitions may be nested, i.e. may contain other TDs. You use this to define clusters of different data, which are defined as well and as such can be accessed on different levels. Review the properties of, say, a waveform chart, using a property node. You'll find a property 'Bounds' for the chart itself as well as for its caption, label, scales, even the scales' markers and so on.

External Links

Creating Type Definitions and Strict Type Definitions

@@ Line 1: / Line 1: @@
-A type definition [TD] is a custom control (CTL) file that has been marked as a type definition.  Instances of the TD are linked to their definition.  You cannot edit functional properties of TD's instances, but only optical properties. To change functional properties you have to edit their TD. All changes in a TD are propagated to all of its instances, when you save the TD or choose to 'apply changes'.<br />
+A type definition [TD] is a custom control (CTL) file that has been marked as a type definition.
-Type definitions can be stacked, e.g. can contain other TDs as well. You use this to define clusters of different data, which are defined as well and as such can be accessed on different levels. Review the properties of, say, a waveform chart, using a property node. You'll fiond a property 'Bounds' for the chart itself as well as for its caption, label, scales, even the scales' markers and so on.
+<center>[[Image:Type_Def_Status.png]]</center>
+Instances of the TD are linked to their definition.  You cannot edit functional properties of TD's instances, but only visual properties. To change functional properties you have to edit their TD. All changes in a TD are propagated to all of its instances, when you save the TD or choose to 'apply changes'.
+Type definitions may be nested, i.e. may contain other TDs. You use this to define clusters of different data, which are defined as well and as such can be accessed on different levels. Review the properties of, say, a waveform chart, using a property node. You'll find a property 'Bounds' for the chart itself as well as for its caption, label, scales, even the scales' markers and so on.
 ==See Also==