Page 148	Table of Contents	Index	Page 150
	Chapters
	1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30 A, B, C, D, E

---

CHAPTER 16. OUTPUT RECORDING


16.3 Types of Output Records

This section discusses several types of output records, including two standard classes of output
records and the displayed output record protocol.

16.3.1 Standard Output Record Classes

=> standard-sequence-output-record [Class]
The standard class provided by CLIM to store a relatively short sequence of output records; a
subclass of output-record. The insertion and retrieval complexity of this class is O(n). Most
of the formatted output facilities (such as formatting-table) create output records that are a
subclass of standard-sequence-output-record.

=> standard-tree-output-record [Class]
The standard class provided by CLIM to store longer sequences of output records. Typically,
the child records of a tree output record will be maintained in some sort of sorted order, such as
a lexicographic ordering on the x and y coordinates of the children. The insertion and retrieval
complexity of this class is O(log n).

16.3.2 Graphics Displayed Output Records

Graphics displayed output records are used to record the output produced by the graphics
functions, such as draw-line*. Each graphics displayed output record describes the output
produced by a call to one of the graphics functions.
The exact contents of graphics displayed output records is unspecified, but they must store
sufficient information to be able to exactly redraw the original output at replay time. The
minimum information that must be captured for all graphics displayed output records is as
follows:

• The description of the graphical object itself, for example, the end points of a line or the
  center point and radius of a circle.
  
  
• The programmer-supplied ink at the time the drawing function was called. Indirect inks
  must not be resolved, so that a user can later change the default foreground and background
  ink of the medium and have that change affect the already-created output records during
  replay.
  
  
• For paths, the programmer-supplied line-style at the time the drawing function was called.
  
  
• The programmer-supplied clipping region at the time the drawing function was called.
  
  
• The user transformation. This may be accomplished by either explicitly storing the trans-
  formation, or by transforming the coordinates supplied to the drawing function and cap-
  turing the transformed coordinates.

---

Page 148	Table of Contents	Index	Page 150
	Chapters
	1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30 A, B, C, D, E