List of Figures

• . Synthetic resources provide for data conversion as well as information hiding.
• . The use of XmSYNTHETIC_LOAD and XmSYNTHETIC_NONE when importing synthetic resource values.
• . The hook mechanism encloses superclass-to-subclass chained widget methods like initialize().
• . The wrapper data stack keeps saved method pointers for a widget class.
• . The method wrappers enclose the non-chained widget methods like realize().
• . A close look at the widget extension data mechanism.
• . The widget extension data mechanism helps to organize and manage secondary objects within some widgets methods.
• . The widget extension data represents the link between a VendorShell and its extension object.
• . Entries on the grab list after a full application modal dialog popped up.
• . Entries on the grab list after a modeless dialog popped up.
• . Entries on the grab list after a full primary application modal dialog popped up.
• . Class hierarchy for extension objects.
• . The XmDesktopObjects form a tree of XmDesktopObjects with a XmScreen widget at the top.
• . The shadow shell tree is organized by XmScreen widgets which are in turn gathered under the hood of a XmDisplay widget.
• . Layout structures to mess around with when using the GeoUtils.
• . The ``DnD Flags'' signal various status conditions during a drag and drop operation.
• . Properties involved in the Drag & Drop game.
• . Overall structure of the _MOTIF_DRAG_RECEIVER_INFO property for the preregister mode.
• . Keyboard event processing.
• . The ``virtual bindings'' take care of some basic consistency between different keyboards.
• . Displays, Screens and the Virtual Bindings.
• . Internal representation of a ``compiled'' _XmString.
• . The big picture of all widget classes.