ProcExec.PortletBlocking Attribute Added
Note: No changes to previous portlet blocking behavior occur by default. This promotes compatibility with existing applications that use portlets.
A new attribute was added to the ProcExec system class (which is an ancestor to both GhostExec and FrameExec classes): PortletBlocking. If a FrameExec’s PortletBlocking attribute is set to PB_HOSTFRAME, the FRAMEEXEC—when activated and displayed through a CALLFRAME—will block interactions with the portlet’s host and guest frames and display the "wait" cursor whenever the mouse pointer is above any of these frame’s fields.
The following are possible values for the PortletBlocking attribute:
• PB_GUESTFRAME (value = 0) – Only the guest frame is blocked (default)
In the following example, the mouse pointer is over a non-portlet field in the portlet host frame. Non-portlet field activated events and scripts behave as usual.
In the following example, the mouse pointer is over a portlet field (guest field) in the portlet host frame. Portlet field-activated events and scripts are deferred until after the blocking frame is closed.
• PB_HOSTFRAME (value = 1) – The host and guest frames are blocked and shielded.
In the following example, the mouse pointer is over a non-portlet field in the portlet host frame. The non-portlet field is blocked (disabled) and shielded (the wait cursor is displayed).
In the following example, the mouse pointer is over a portlet field (guest field) in the portlet host frame. The non-portlet field is blocked (disabled) and shielded (the wait cursor is displayed).
• PB_GUESTFIELD (value = 2) – The hosted portlet field (guest field) becomes inactive (disabled) and shielded (a "wait" cursor is displayed when the mouse pointer is over them). The guest frame is blocked and shielded. The host frame and its fields (except the hosted portlet field) are not blocked or shielded.
In the following example, the mouse pointer is over a non-portlet field in the portlet host frame. Non-portlet field-activated events and scripts behave as usual.
In the following example, the mouse pointer is over a portlet field (guest field) in the portlet host frame. The non-portlet field is blocked (disabled) and shielded (the wait cursor is displayed).
The PortletBlocking attribute can also be set on a CALLFRAME-by-CALLFRAME basis by using "WITH PortletBlocking = value" as a modifier to the CALLFRAME command.
For more information about the ProcExec.PortletBlocking attribute, see the Language Reference Guide.
