Whenever the
region manager detects an error during the resizing of a
component, the components are all restored to the location and size that they had before the
component was resized. Here are the most common reasons that resizing a component
fails:
-
When the component is resized, the component becomes too small for the
object that it contains.
-
An attachment cannot be honored.
Check all your attachments for conflicts.
-
Honoring an attachment requires resizing the master component. The master component
can only initiate a resize
event and cannot be resized as a result of resizing another component. Check all your attachments
to the master component.
-
Resizing the component results in a component being placed outside of the boundaries
of its parent (unless
its parent is a viewport component, as used by the work area object). This typically
implies that a required attachment is missing.
-
Resizing the component results in a component being smaller than allowed by the region
manager (eight pixels). This situation does not necessarily imply that the attachments
are
in error. You may simply be attempting to shrink the original component too much.
-
Resizing the component causes components that contain text objects to overlap, which
usually implies an
error in the way the attachments are defined.
If, after examining the attachments and the results of attempted resizes, you do not
understand the attachment problem, use the region manager to trace the handling of
the resizing by issuing the command RM GROW DEBUG. The next
time you try to resize the component, diagnostic messages will be sent to the Log
window.