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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Built-in named parameters<br />

2<br />

The named parameter should be followed with the equal/greater than signs (=>), which point to the<br />

actual parameter that follows the named parameter. For example, if you intend to change the<br />

milliseconds in the SET_TIMER Built-in you can directly use that parameter with the following syntax:<br />

SET_TIMER(timer_name => ’my_timer’, milliseconds => 12000,<br />

iterate => NO_REPEAT);<br />

Also, you can continue to call the built-in with the following syntax:<br />

SET_TIMER(’my_timer’, 12000, NO_REPEAT);<br />

Built-in code examples<br />

Examples have been included for the built-in subprograms. Some examples are simple illustrations of<br />

the syntax. Others are more complex illustrations of how to use the Built-in either alone or in<br />

conjunction with other built-ins. A few points to keep in mind regarding the syntax of examples:<br />

• Examples are shown exactly as they can be entered.<br />

• Casing and use of italics can be ignored and is included for readability.<br />

• Built-in names and other PL/SQL reserved words, such as IF, THEN, ELSE, BEGIN, and END are<br />

shown in capital letters for easier readability.<br />

• Named parameters, when illustrated, are shown in an italic typeface. If you choose to use named<br />

parameters, enter these parameter names exactly as shown, without quotes and follow them with the<br />

equal/greater than symbols (=>).<br />

• CHAR type arguments must be enclosed in single quotes.<br />

• Any other data type argument should not be enclosed in quotes.<br />

• Special characters other than single quotes (’), commas (,), parentheses, underscores (_), and<br />

semicolons(;) should be ignored.<br />

Built-in object IDs<br />

Some built-in subprograms accept object IDs as actual parameters. An object ID is an internal, opaque<br />

handle that is assigned to each object when created in the <strong>Form</strong> <strong>Builder</strong>. Object IDs are internally<br />

managed and cannot be externally viewed by the user. The only method you can use to retrieve the ID is<br />

to define a local or global variable and assign the return value of the object to the variable.<br />

You make the assignment by way of the FIND_ built-in functions. Once you have used FIND_ within a<br />

PL/SQL block, you can use the variable as an object ID while still in that block. The valid PL/SQL type<br />

for each object is included in the syntax descriptions for each parameter. The description for the<br />

FIND_BLOCK built-in provides an example of how to obtain an object ID.<br />

Built-in form coordinate units<br />

Many built-in subprograms allow you to specify size and position coordinates, using properties such as:<br />

• HEIGHT

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

Saved successfully!

Ooh no, something went wrong!