RECORD GROUP
This object represents an internal Form Builder data structure that has a column/row framework similar to a database table.
Query record group
A query record group is a record group that has an associated SELECT statement. The columns in a query record group derive their default names, data types, and lengths from the database columns referenced in the SELECT statement. The records in a query record group are the rows retrieved by the query associated with that record group. Query record groups can be created and modified at design time or at runtime.
Non-query record group
A non-query record group is a group that does not have an associated query, but whose structure and values can be modified programmatically at runtime. Non-query record groups can be created and modified only at runtime.
Static record group
A static record group is not associated with a query; instead, you define its structure and row values at design time, and they remain fixed at runtime. Static record groups can be created and modified only at design time.
LOV [ LIST OF VALUES ]
An LOV is a scrollable popup window that provides the end user with either a single or multi-column selection list. Default Key for LOV – F9
LOVs provide the following functionality:
v LOVs can be displayed by end user request (when an LOV is available), when the end user navigates to a text item with an associated LOV, or programmatically, independent of any specific text item.
v LOV auto-reduction and search features allow end users to locate specific values.
v LOV values that are selected by the end user can be assigned to form items according to the return items you designate.
v At design time, an LOV can be attached to one or more text items in the form.
v LOV values are derived from record groups.
PROPERTY CLASS
This object is a named object that contains a list of properties and their associated settings. Once you create a property class you can base other objects on it. An object based on a property class can inherit the settings of any property in the class that is appropriate for that object.
The Property Palette is where you set the properties of objects you create in form and menu modules.
There are 2 ways to creating property class
a. Object Navigator method.
b. Property Window method
Property class can not be change programmatically.
VISUAL ATTRIBUTES
Visual attributes are the font, color, and pattern properties that you set for form and menu objects that appear in your application's interface. Visual attributes can include the following properties:
Font properties: Font Name, Font Size, Font Style, Font Width, Font Weight Color and pattern properties: Foreground Color, Background Color Fill Pattern, Charmode Logical Attribute, White on Black It can be changed dynamically.
Visual attribute name is connected to an object by setting visual attribute name property
Set_item_property(‘text1’,current_record_attribute,’v1’);
Visual Attribute Types
1. Default
Setting the Visual Attribute Group property to Default specifies that that the object should be displayed with default color, pattern, and font settings. When Visual Attribute Group is set to Default, the individual attribute settings reflect the current system defaults. The actual settings are determined by a combination of factors, including the type of object, the resource file in use, and the window manager.
2. Custom
When the attribute of an objects are changed at design tome, they are custom VAT
3. Named
Setting the Visual Attribute Group property to a named visual attribute defined in the same module specifies that the object should use the attribute settings defined for the named visual attribute. A named visual attribute is a separate object in a form or menu module that defines a collection of visual attribute properties. Once you create a named visual attribute, you can apply it to any object in the same module, much like styles in a word processing program.
EDITOR
This object enables the operator to edit text. There are three types of editor objects:
default editor, system editor, and user-named editor.
1. System Editor
The system editor to be used is defined by the FORMS60_EDITOR environment variable. The editor specified must use the ASCII text format. For information on environment variables and system editor availability, refer to the Form Builder documentation for your operating system.
FORMS60_EDITOR = C:\WINDOWS\NOTEPAD.EXE
2. Default Editor
Default editor is invoked at runtime, Form Builder determines its display size and position dynamically based on the size and position of the text item from which the editor was invoked.
3. User-Named Editor
A user-named editor has the same text editing functionality as the default editor. You create a user-named editor when you want to display the editor programmatically with SHOW_EDITOR, or when you want to specify custom editor attributes such as scroll bar and title.
SHOW_EDITOR(editor_name, message_in, x, y, message_out, result);
The SHOW_EDITOR procedure displays a user-named editor at the specified display coordinates. SHOW_EDITOR takes message_in and message_out parameters that allow you to pass a text string in to the editor and to get the edited text string back when the operator accepts the editor.
No comments:
Post a Comment