Difference between revisions of "DISPLAYDATAMETACLASS"
m (moved DisplayDataMetaClass to DISPLAYDATAMETACLASS) |
|||
(5 intermediate revisions by the same user not shown) | |||
Line 2: | Line 2: | ||
| title = Display Data MetaClass | | title = Display Data MetaClass | ||
| name = DISPLAYDATAMETACLASS | | name = DISPLAYDATAMETACLASS | ||
− | | internalname = | + | | internalname = - |
| namespace = System.Display | | namespace = System.Display | ||
| image = [[File:SY_DISPLAYDATAMETACLASS.png|220px]] | | image = [[File:SY_DISPLAYDATAMETACLASS.png|220px]] | ||
− | | imagecaption = Display | + | | imagecaption = Display data MetaClass |
| purpose = Display data of MetaClasses | | purpose = Display data of MetaClasses | ||
| version = 2+ | | version = 2+ | ||
+ | | typestring = UBIK.Kernel.MetaClass | ||
+ | | runtimetype = UBIK.Display.DisplayDataMetaClass | ||
}} | }} | ||
+ | Implementing customer specific code or assigning an icon to a [[MetaClass]] creates a display data object for the specific class. | ||
− | [[Category: | + | Usually the system creates a display data object for each MetaClass, hence stores the code or icon information separately. Whenever a MetaClass is missing this particular information, the system looks up the inheritance line and tries to find a parent’s display data object. |
+ | |||
+ | [[Category:Metaclasses]] |
Latest revision as of 08:59, 24 March 2015
Implementing customer specific code or assigning an icon to a MetaClass creates a display data object for the specific class.
Usually the system creates a display data object for each MetaClass, hence stores the code or icon information separately. Whenever a MetaClass is missing this particular information, the system looks up the inheritance line and tries to find a parent’s display data object.