11.01.2013 Views

Oracle Forms Developer – Form Builder Reference, Volume 1

Oracle Forms Developer – Form Builder Reference, Volume 1

Oracle Forms Developer – Form Builder Reference, Volume 1

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

24<br />

Background Color The color of the object’s background region.<br />

Fill Pattern The pattern to be used for the object’s fill region. Patterns are rendered in the two colors<br />

specified by Background Color and Foreground Color.<br />

Character Mode Logical Attribute Specifies the name of a character mode logical attribute defined<br />

in an <strong>Oracle</strong> Terminal resource file that is to be used as the basis of device attributes for a character<br />

mode version of your application.<br />

White on Black Specifies that the object is to appear on a monochrome bitmap display device as<br />

white text on a black background.<br />

Not all attributes are valid for each object type. For example, setting font attributes for a window<br />

object has no effect. (The font used in a window’s title bar is derived from the system.)<br />

A new object in a new form has Default visual attributes. The default settings are defined<br />

internally. Override the default font for new items and boilerplate by setting the optional<br />

FORMS60_DEFAULTFONT environment variable. For example, On Microsoft Windows, set<br />

this variable in the ORACLE.INI file, as follows:<br />

FORMS60_DEFAULTFONT="COURIER.10". The default font specified determines the font<br />

used for new boilerplate text generated by the New Block window, and for any items that have<br />

Visual Attribute Group set to Default.<br />

When you create an item in the Layout Editor, its initial visual attribute settings are determined by the<br />

current Layout Editor settings for fonts, colors, and patterns, as indicated by the Font dialog and<br />

Color and Pattern palettes.<br />

On Microsoft Windows, the colors of buttons, window title bars, and window borders are controlled<br />

by the Windows Control Panel color settings specified for these elements. You cannot override<br />

these colors in <strong>Form</strong> <strong>Builder</strong>.<br />

When the Use 3D Controls form property is set to Yes on Microsoft Windows (the default), items are<br />

rendered with shading that provides a sculpted, three-dimensional look. A side effect of setting this<br />

property is that any canvases that have Visual Attribute Group set to Default derive their color<br />

setting from the Windows Control Panel (gray for most color schemes). You can override this<br />

setting by explicitly applying named visual attributes to the canvas.<br />

An item that has Visual Attribute Group set to Default, or that has individual attribute settings left<br />

unspecified, inherits those settings from the canvas to which it is assigned. Similarly, a canvas that<br />

has Visual Attribute Group set to Default, or that has individual attribute settings left unspecified,<br />

inherits those settings from the window in which it is displayed. For example, if you set a window’s<br />

Background Color to CYAN, and then leave Background Color unspecified for the canvas assigned<br />

to the window, at runtime, that canvas will inherit the CYAN background from its window. Visual<br />

attribute settings derived through window canvas or canvas item inheritance are apparent only at<br />

runtime, not at design time.<br />

You can apply property classes to objects to specify visual attribute settings. A property class can<br />

contain either the Visual Attribute Group property, or one or more of the individual attribute<br />

properties. (If a property class contains both Visual Attribute Group and individual attributes, the<br />

Visual Attribute Group property takes precedence.)<br />

If you apply both a named visual attribute and a property class that contains visual attribute settings to<br />

the same object, the named visual attribute settings take precedence, and the property class visual<br />

attribute settings are ignored.<br />

Logical attribute definitions defined in the resource file take precedence over visual attributes<br />

specified in the <strong>Form</strong> <strong>Builder</strong>, local environment variable definitions, and default <strong>Form</strong> <strong>Builder</strong><br />

attributes. To edit the resource file, use the <strong>Oracle</strong> Terminal utility.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!