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.

• WIDTH<br />

• DISPLAY_POSITION<br />

• VIEWPORT_X_POS<br />

• VIEWPORT_Y_POS<br />

• VIEW_SIZE<br />

• VIEWPORT_X_POS_ON_CANVAS<br />

• VIEWPORT_Y_POS_ON_CANVAS<br />

When you specify coordinates or width and height, you express these measurements in units of the<br />

current form coordinate system, set on the <strong>Form</strong> Module property sheet. The form coordinate system<br />

defines the units for specifying size and position coordinates of objects in the <strong>Form</strong> <strong>Builder</strong>. Use the<br />

Coordinate System form module property to set the form’s coordinate units:<br />

• character cells or<br />

• real units:<br />

inches<br />

centimeters<br />

pixels<br />

points<br />

When you design in the character cell coordinate system, all object dimensions and position coordinates<br />

are expressed in character cells, so <strong>Form</strong> <strong>Builder</strong> accepts only whole numbers for size and position<br />

properties.<br />

When you design using real units (inches, centimeters, or points), all object dimensions and position<br />

coordinates are expressed in the units you specify, so <strong>Form</strong> <strong>Builder</strong> will accept decimals as well as whole<br />

numbers for size and position properties. The precision of real units is three digits, so you can specify<br />

coordinates to thousandths. If you use pixels or character cells, coordinates are truncated to whole<br />

numbers.<br />

Built-in uppercase return values<br />

The GET_X_PROPERTY built-ins, such as GET_FORM_PROPERTY, return CHAR arguments as<br />

uppercase values. This will affect the way you compare results in IF statements.<br />

Restricted built-in subprograms<br />

Restricted built-ins affect navigation in your form, either external screen navigation, or internal<br />

navigation. You can call these built-ins only from triggers while no internal navigation is occurring.<br />

Restricted built-ins cannot be called from the Pre and Post triggers, which fire when <strong>Form</strong> <strong>Builder</strong> is<br />

navigating from object to another.<br />

Restricted built-ins can be called from the When triggers that are specific to interface items, such as<br />

When-Button-Pressed or When-Checkbox-Changed. Restricted built-ins can also be called from any of<br />

the When-New-"object"-Instance triggers and from key triggers.<br />

Unrestricted built-ins do not affect logical or physical navigation and can be called from any trigger.<br />

3

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

Saved successfully!

Ooh no, something went wrong!