Modeled Component

Modeled components are used to speed development and ensure consistency between components with a similar purpose. A modeled component defines a pattern for a specific type of component, including its structure, properties, and layout, and this pattern is copied to components that are derived from it.

Characteristics

Characteristics
Object type code:	cpt
Main Development Object?	Yes
Part of:	—
Contains:	Component Entity, Label, Property, Code Container, Generic Entity, Generic Field
Generalization:	Main Development Object
Specializations	—
Compilation Output	—
Example URI:	cpt:ModeledComponentName

Specialization

Modeled Component specializes Main Development Object and Component in the following ways:

• The Modeled Component property is True. This causes Uniface to automatically define compile-time constants for any generic entities and fields.

• It can contain generic entities and fields.

• No runtime objects are generated.

Properties

Object Properties:

• Name
• Type
• Location
• Description
• Documentation

Source Properties:

• Date Modified

Configuration Properties:

• Library
• Is Modeled Component
• Modeled Component

Behavior Properties:

• Component Type
• Data Access
• Component Behavior
• State Managed By
• Self-Contained

Data I/O Properties:

• Input Translation
• Output Translation

Presentation Properties:

• Title

Character Mode Properties:

• Header Length
• Clear?
• Borderline
• Inverse
• Bright
• Underline
• Blink

Triggers

• trigger accept
• trigger clear
• trigger erase
• trigger getFocus (Form)
• trigger loseFocus (Form)
• trigger menu
• trigger retrieve
• trigger retrieveSequential
• trigger postActivate
• trigger preActivate
• trigger print
• trigger pullDown
• trigger receiveMessage
• trigger store
• trigger quit
• trigger userKey