Form Core Support

PML defined forms now have a new qualifier attribute ‘control type’, with values PML or CORE. A form is PML managed by default, but can be declared core managed by means of the ‘CORE’ keyword in the FSETUP command. This is applicable to any form type except MAIN forms, for example:

LAYOUT FORM !!myform blockingdialog resi CORE

When a form is first displayed, if it is declared as core managed, then F&M builds the DRUID widget, and then notifies core code so that it can take over the form’s management.

Note:
This is guaranteed to precede any core gadget or core menu notifications.

Core code may plug in its own callback functions to DRUID for certain form events which will then no longer go to F&M.

Typically core code will need to manage the following:

• Form UI_QUIT event.

• The OK, CANCEL, and APPLY buttons if present.

• Showing and hiding the form.

In general the PML form definition for a core managed form should not define the following PML callbacks:

• INITCALL

• AUTOCALL

• OKCALL

• CANCECALL.

  If OK, CANCEL or APPLY buttons are present they should also be declared as CORE managed.