The application may choose to use Intuition's rendering facilities to
display the requester, or it may define its own custom bitmap.  The
requester structure is initialized differently according to the rendering
method chosen.

To use Intuition's rendering facilities, you supply a list of one or more
display objects with the requester structure and submit the requester  to
Intuition, allowing it to draw the objects.  These objects can include
independent lists of borders, intuitext, images and gadgets.  note that
the abilty to provide a list of Image structures is new in V36, and the
usereqimage flag must be set for them to be rendered.  for more about
Intuition rendering see the chapter on
"intuition images, line drawing and text".

The gadgets in a requester also have their own borders, images and text to
add to the display imagery.  Intuition will allocate the buffers,
construct a bitmap that lasts for the duration of the display, and render
the requester into the window.  This rendering is all done over a solid
color, filled background specified by the backfill pen in the requester
structure.  The backfill may be disabled by setting the noreqbackfill flag
(this also a new feature of V36).

On the other hand, a custom requester may be designed with pre-defined,
bitmap imagery for the entire object.  The image bitmap is submitted to
Intuition through the imagebmap field of the requester structure.  the
bitmap should be designed to reduce user confusion; gadgets should line up
with their images, and the designer should attempt to use glyphs (symbols)
familiar to the user.

To provide imagery for the requester, applications should always try to
use data structures attached to the requester structure as described
above.  Although, rendering directly into the requester layer's rastport
is tolerated, it must be done with great care.

First, a requester is allowed to have gadgets that automatically close the
requester when they are selected (gact_endgadget).  if such a gadget is
selected, the requester, its layer, and its layer's rastport will be
deleted asynchronously to your application.  If your application is trying
to render directly into the requester at that time, the results are
unpredictable.  Therefore, do not put GACT_ENDGADGET gadgets into a
requester if you plan on rendering directly into its RastPort.

Second, recall that requesters are clipped to the inside of the window
(not including the borders).  If the window can be sized smaller such that
the requester would be entirely clipped, the requester's layer may be
deleted by Intuition.  If your window's minimum size and the requester
size and position are such that the requester can be completely clipped,
then reading requester.reqlayer is unsafe without additional protection.
It would be correct to locklayerinfo() the screen's layer_info, then check
for the existence of the requester's ReqLayer, then render, then unlock.

For reasons such as these, direct rendering is discouraged.