The Procedure Manager displays the procedure name, parameter type, and procedure type of every procedure defined for your interface. The procedure name is preceded by a lock symbol if the procedure is pre-defined. Callback routines are referenced from the Callback Editor; creation routines from the Creation Routine dialog.
By default, the Procedure Manager displays all of the Builder Xcessory pre-defined callbacks. These callbacks are designated on the Procedure Manager by a lock icon, since they cannot be deleted from Builder Xcessory.
- Defined by default when Builder Xcessory starts up. Their UIL and C/C++ equivalents are listed in the Type Manager, and appear "locked" so that they may not be cut.
- Appear unlocked in the Type Manager. A new type may be declared in the Procedure Editor by selecting the User Defined radio box and entering the new type in the Parameter Type text field. Builder Xcessory prompts you for confirmation and adds the new type to the Type Manager.
If the type is Undeclared, Builder Xcessory allows the user to declare the procedure parameter to be either no parameter or a parameter of any type. Otherwise, Builder Xcessory checks that the parameter passed to the procedure call is of the correct type. If the parameter type is None, Builder Xcessory will not allow the user to specify a procedure parameter when the procedure is added to a callback list or used in the Creation Routine editor. Refer to Creation Routine for more detailed information.
Set the Procedure Type as either Creation Routine or Callback. Creation Routine procedures may be referenced in the Creation Routine dialog. Callback procedures may be used in callback lists which are assigned as callback resource values.
A procedure's Parameter Type and Procedure Type fields may not be changed if the procedure's Reference Count is greater than zero. To decrement the count to zero, remove all references to the procedure from the current interface.
The Output File Option Menu allows you to specify the file to which the procedure will be written when Builder Xcessory generates UIL. See File Placement for more detailed information.