Volume Four: X Toolkit Intrinsics Programming ManualList of Figures
| Table of Contents | List of Figures | List of Examples | List of Tables |
- Figure 1-1. An X application, and an application on a traditional text terminal
- Figure 1-2. A three-button mouse directing the pointer to select a menu item
- Figure 1-3. Screen layout of a typical user's X Window System
- Figure 1-4. Applications can run on any system across the network
- Figure 1-5. The software architecture of Xt Intrinsics-based applications
- Figure 2-1. A widget-based application (simulated)
- Figure 2-2. A Motif widget-based application (simulated)
- Figure 2-3. Two ways to think about a class
- Figure 2-4. Class hierarchy of the Motif widget set
- Figure 2-5. Several Athena Label widgets configured using resources
- Figure 2-6. Widgets operate independently of the application
- Figure 2-7. XtSetValues lets the application set how a widget will operate itself
- Figure 2-8. Application registers a function with Xt during startup phase
- Figure 2-9. Xt calls the function during the event-loop phase in response to an occurrence
- Figure 2-10. xhello: appearance on screen
- Figure 2-11. The appearance of xgoodbye when the pointer is in the window
- Figure 2-12. xgoodbye run with new resource settings
- Figure 3-1. xrowcolumn: appearance on the screen
- Figure 3-2. Two configurations of xrowcolumn
- Figure 3-3. Incorrect results upon resize of ScrollBar widgets inside a RowColumn widget
- Figure 3-4. The xmh application and its instance hierarchy
- Figure 3-5. Effect of the Form XmATTACH_WIDGET constraint resource
- Figure 3-6. xmainwindow: an application with standard Motif screen layout
- Figure 3-7. xmainwindow with the File pulldown menu displayed
- Figure 3-8. xmainwindow with the Help dialog box displayed
- Figure 3-9. The widget instance and X window hierarchies are different only for popups
- Figure 4-1. xbitmap1: how it looks on the screen
- Figure 4-2. xbitmap2: true-scale normal and reverse bitmaps added
- Figure 4-3. Application draws into Pixmap and copies it to widget window
- Figure 4-4. Two-stage mapping with translation table and action table
- Figure 5-1. A Command widget
- Figure 5-2. A FileSelectionDialog widget
- Figure 5-3. A SelectionDialog widget
- Figure 5-4. A TextField widget
- Figure 5-5. A menu containing buttons separated by Separator widgets
- Figure 5-6. ToggleButton widgets used in a RadioBox and a CheckBox
- Figure 5-7. A Scale widget
- Figure 5-8. A List widget containing selectable strings
- Figure 5-9. Dialog boxes with the five standard symbols
- Figure 5-10. xcomstring.c: how it looks on the screen
- Figure 6-1. The class hierarchy of the BitmapEdit widget (with other classes shown dotted)
- Figure 6-2. Order of code in widget .c file
- Figure 7-1. compress_exposure: 2 rectangles if XtExposeNoCompress; bounding box and region if XtExposeCompressSeries or XtExposeCompressMultiple
- Figure 8-1. xbox1: two Command widgets in a Box
- Figure 8-2. Key event propagation in xbox
- Figure 9-1. xtetris in play
- Figure 10-1. Typical resource setting search path on UNIX-based systems
- Figure 10-2. The quit widget in a sample widget hierarchy
- Figure 10-3. Steps in matching resource entries for one resource of widget being created
- Figure 11-1. The process of selection transfer
- Figure 12-1. Role of border width in widget geometry
- Figure 12-2. Initial geometry negotiation, assuming sufficient shell space
- Figure 12-3. Initial geometry negotiation, if resizing is necessary
- Figure 12-4. A widget requesting a size change
- Figure 12-5. A ScrollBox widget at two different sizes
- Figure 12-6. Geometry negotiation by the set_values_almost method
- Figure 13-1. Athena Command widgets in an Athena Box widget, and the same commands as a SimpleMenu
- Figure 13-2. xmenu1: application with spring-loaded popup menu
- Figure 13-3. xmenu2: a pulldown menu
- Figure 13-4. xmenu5: cascaded spring-loaded menus
- Figure 13-5. xmenu7: a menu using the Athena SimpleMenu widget
- Figure 13-6. Class hierarchy derivation of Core
- Figure 14-1. editres immediately after startup
- Figure 14-2. editres with widget tree displayed
- Figure 14-3. editres display window IDs of widget tree
- Figure 14-4. Flashing widget in application by selecting it in editres
- Figure 14-5. Resource box for the selected Label widget
- Figure 14-6. Generalizing the widgets affected by the resource specification
- Figure A-1. An OPEN LOOK application
- Figure A-2. Class inheritance hierarchy of the AT&T OPEN LOOK widgets
- Figure A-3. An OPEN LOOK ControlArea with OblongButton and ButtonStack widgets
- Figure A-4. OPEN LOOK RectButtons controlled by Exclusives and Nonexclusives widgets
- Figure A-5. An OPEN LOOK CheckBox widget
- Figure A-6. An OPEN LOOK Slider widget
- Figure A-7. An OPEN LOOK Scrollbar
- Figure A-8. An OPEN LOOK ScrollingList widget
- Figure A-9. An OPEN LOOK Notice
- Figure A-10. An OPEN LOOK PopupWindow
- Figure A-11. An OPEN LOOK Help window
- Figure A-12. Look of a Motif application
- Figure A-13. Class inheritance hierarchy of the Motif widget set
- Figure A-14. Motif DrawnButton and PushButton widgets
- Figure A-15. A Motif RowColumn widget configured as a MenuBar
- Figure A-16. A Motif RowColumn widget configured with four RadioBoxes
- Figure A-17. A Motif RowColumn widget configured as a drop-down window
- Figure A-18. A Motif Form widget and children
- Figure A-19. A Motif ScrollBar
- Figure A-20. A Motif SelectionBox
- Figure B-1. Multiple planes used to index a colormap
- Figure B-2. A font name
- Figure B-3. A typical font server configuration