There are certain aspects of the behavior of GadTools gadgets that should
not be depended on. This will help current applications remain compatible
with future releases of the GadTools library.

When using gt_filterimsg() and gt_postfilterimsg(), never make assumptions
about the message before or after filtering.  I.e., do not interpret the
unfiltered message, assume that it will or will not result in certain
kinds of filtered message or assume it will result in a consumed message
(i.e., when GT_FilterIMsg() returns NULL).

idcmp_intuiticks messages are consumed when a scroller's arrows are
repeating.  That is, IDCMP_INTUITICKS will not be received while the user
is pressing a scroller arrows.  Do not depend or rely on this side effect,
though, it will not necessarily remain so in the future.

A single call to creategadget() may create one or more actual gadgets.
These gadgets, along with the corresponding code in GadTools, define the
behavior of the particular kind of GadTools gadget requested.  Only the
behavior of these gadgets is documented, the number or type of actual
gadgets is subject to change.  Always refer to the gadget pointer received
from CreateGadget() when calling gt_setgadgetattrs().  never refer to
other gadgets created by GadTools, nor create code which depends on their
number or form.

For text-display gadgets, the gttx_copytext tag does not cause the text to
be copied when the text is later changed with gttx_text.

The PLACETEXT ng_flags are currently ignored by generic_kind gadgets.
However, this may not always be so.

All GadTools gadgets set GADTOOL_TYPE in the gadget's gadgettype field.
Do not use this flag to identify GadTools gadgets, as this flag is not
guaranteed to be set in the future.

The palette gadget subdivides its total area into the individual color
squares. Do not assume that the subdivision algorithm won't change.