Consultor Eletrônico

Status: Unverified

GOAL:

Dynamics. What Procedure passes an exit request to its container.

FACT(s) (Environment):

Dynamics 2.1A

FIX:

exitObject passes an exit request to its container.

By convention, the standard routine always passes an exit request to its CONTAINER·SOURCE. The container that actually initiates the exit should define a local version and not call the standard one. That local exitObject is built into the SmartWindow template. This allows any SmartObject to initiate a destroy operation on its container. When it runs exitObject (for example, when a user pressing a Done button), this event is passed up through the Container link hierarchy until an object is found that is at the appropriate level to initiate a destroy of all its contents. As noted, this is normally the SmartWindow, where exitObject does APPLY ·CLOSE· TO THIS·PROCEDURE, that in turn runs destroyObject.

exitObject could be customized when you want behavior other than, or in addition to, invoking exitObject in the ContainerSource. As noted, the default localization in SmartWindows is to APPLY CLOSE to initiate a destroyObject sequence. A local version of this, in an object other than a SmartWindow, could do additional custom cleanup. Note that because exitObject is defined in the SmartWindow template, a localization of it in a SmartWindow must exclude the standard code to prevent a duplicate procedure definition.

&IF "{&PROCEDURE-TYPE}" EQ "SmartWindow" &THEN

RUN exitObject.

&ELSE

APPLY "CLOSE":U TO THIS-PROCEDURE.

&ENDIF