Abstract:
A stand-alone graphics workstation including a digital computer host and a graphics processing subsystem is disclosed. Address data relating to the graphics subsystem components is mapped into the host system virtual memory. The application processes residing in the host are thereby able to communicate directly with the graphics subsystem components, as, e.g. the structure memory, without the need of a direct memory access hardware arrangement or device drivers.

Description:
BACKGROUND OF THE INVENTION 
     A. Field of the Invention 
     The invention relates to a computer graphics workstation and, more particularly, to a high performance, stand-alone graphics workstation including a digital computer host and a graphics processing subsystem. The invention provides efficient control structures to obtain a maximum utilization of system resources and to effectively coordinate operation among essentially data-driven, asynchronous components and thereby enable both two-dimensional and three-dimensional high resolution graphics displays. 
     B. Prior Graphics Systems 
     In recent years considerable advances have been made in the utilization of computer systems to generate and visually display character and graphical output data. The earliest systems were limited to two-dimensional displays very often realized through the use of alphanumeric characters. The graphics data generation capability of such early systems was limited and certain character representations of predetermined size and shape were stored in a character data memory and were transferrable to a display memory by the user, when desired, to expand the display capability of the system. A noteworthy advance in the computer graphics art involved the use of a so-called &#34;bit mapped&#34; graphics display system to store output data in a display memory. The &#34;bit mapped&#34; approach visualizes the output data as a two-dimensional array of pixels, where each pixel corresponds to an individual picture element in the display device. In a two-dimensional, black and white graphics display, each pixel need only contain one bit of information, i.e. either 0 or 1 to represent either black or white, respectively. Accordingly, all of the pixels for a two-dimensional, black and white display may be in the form of a two-dimensional map where the bits of information in the map comprise the output data representing the display device. 
     As should be understood, the graphic display of a three-dimensional object in color, as opposed to a two-dimensional object in black and white substantially increases the amount of output data required to represent the display device and the processing capability of the graphics system required to process the output data for display on a cathode ray tube. For instance, with respect to color alone, eight bits of information per pixel may be required to store information on the red, green and blue components of the color and the intensity of the color for display. 
     The bit mapped approach was expanded by the prior art to a planar concept wherein a three-dimensional array is visualized with separate spaced, parallel planes, each plane corresponding to one attribute of the color information, i.e., a red plane, a green plane, a blue plane and an intensity plane. Each pixel comprises bits stored on the separate planes and data processing requires the graphics system to retrieve the separate bits of a pixel from among several memory locations. 
     When other attributes and display characteristics such as a three-dimensional display, shading, surface reflective qualities, object rotation, etc. are to be added to the graphics system, the memory structure and capacity and data processing capability of the system must be greatly expanded to represent and visually display an object. Such capacity, structure and processing capability requirements have generally limited the feasibility of implementing a high performance, three-dimensional graphics system as a stand-alone, workstation-type system particularly a graphics system with a multi-user capability. While technological advances such as a 32 bit word microprocessor provide a hardware basis for a stand-alone, workstation implementation for a graphics system, there remain formidable data structure and processing and system operational control requirements to achieve an effective high performance graphics workstation system capable of processing multiple application processes to permit a multi-user implementation. These requirements have not been adequately addressed by the prior art. 
     SUMMARY OF THE INVENTION 
     Accordingly, it is a primary objective of the invention to provide a stand-alone, graphics workstation that accomplishes the data structure and processing and system operational control necessary for high performance, high resolution graphics display with a multi-user capability. 
     Generally, the system of the invention comprises a host central processing unit connected by means of an intermediate processing unit and a bus arrangement to a graphics subsystem. The host subsystem is operable to execute one or more application programs residing in the host to build graphics data structures representing two dimensional and/or three-dimensional objects to be displayed. The graphics data structures are stored in a structure memory component in the graphics subsystem. The three-dimensional graphics data structures are each implemented as a hierarchical graphics data node structure in the structure memory. For a thorough discussion of the principal concepts of interactive computer graphics as generally employed by the system of the invention, reference should be made to Fundamentals of Interactive Computer Graphics by J. D. Foley and A. Van Dam (Addison-Wesley 1982). 
     Each node is defined as a fundamental memory unit to contain graphics data or commands relating to the primitives, transformations, attributes and so on of the graphics structure being built pursuant to a specific application program residing in the host through the utilization of preselected structured graphics routines stored in a memory library, also in the host. An asynchronously operational structure walker in the graphics subsystem traverses a special control structure stored in the structure memory on a continuing basis to read and process requests for traversal of the nodes of the graphics structures and to send the data and command information contained in the nodes down a graphics pipeline for processing, manipulation and display by the graphics processing components of the graphics subsystem. 
     Pursuant to an important feature of the invention, a traversal control function is partitioned among the host and graphics subsystem components to accept requests for graphics structure traversals made by competing application programs, and to subsequently schedule and perform such traversals in a manner such that each of the competing graphics applications views the graphics processing subsystem as its own and is able to be executed with a most efficient utilization of the system components. The hierarchical node memory structure, asynchronous memory traversal and supervising traversal control functions together facilitate a high performance three-dimensional display capability within the system by providing an efficient allocation of system resources to store complex graphics data structures and to process the graphics data structures in an ordered and coordinated fashion. The system of the invention effectively utilizes efficient coordination and control of ongoing, data driven, asynchronous operation of the graphics subsystem components to place all of the system resources equally at the disposal of a multiple of application programs residing in the host to thereby enable a multi-user functionality. 
     In accordance with known concepts of interactive computer graphics, the invention makes use of a windowing system to provide a conversion from the world coordinate system of the user to appropriate geometric coordinates suitable for the physical display device of the workstation, i.e. the cathode ray tube. A window is a rectangular array of pixels which may be partially or wholly visible on the display device depending upon the size of the window relative to the physical dimensions of the display screen. Windows are also in a hierarchy with a &#34;parent&#34; window and sub-windows or &#34;children&#34;. Windows may be resized and sub-windows used for clipping by the parent when a sub window is sized greater than the parent for detailed display of portions of a display device defined by a graphics structure. As will be described in more detail in the following description of a preferred embodiment of the invention, a highly advantageous windowing system for use in connection with the display of the graphic structures generated by the application programs is the X Window System developed under the auspices of the Massachusetts Institute of Technology as a royalty free industry standard. Pursuant to the invention, the data generated by the windowing system to create and define the window coordinates and attributes is uniquely identified by the traversal control system for correlation to the hierarchical graphics data node structure of the object to be displayed within the rectangular array of the window. 
     Accordingly, the asynchronous traversal by the structure walker is able to provide correlated graphics structure data and commands and window data to the graphics processing components. The window data-graphics structure correlation function of the traversal control further facilitates high performance three-dimensional graphics display by permitting the utilization of a highly effective window system such as the X Window System which was developed primarily for use in two dimensional, bit mapped graphics systems. The window identification data for correlation to the three-dimensional node memory structures systematically merges a three-dimensional functionality into the advantageous X Window System. 
     Pursuant to another significant feature of the invention, a separate two dimensional, bitmap graphics system is provided in parallel to the three dimensional components to process two dimension application programs. The bit map graphics system has resources suitable for two dimensional graphics including a bitmap memory and a rendering processor to traverse bitmap data commands in structure memory. Moreover, the structure memory is shared by the parallel three dimensional and two dimensional graphics systems to serve both as the three dimensional graphics structure memory and the two dimensional bit map memory. The rendering processor is also shared by the parallel graphics systems to process both bit map graphics and polygon rendering for three dimensional objects. In this manner, the system resources having three dimensional capabilities are not overburdened with processing tasks related to two dimensional displays and functional capabilities which overlap both the three dimensional and two dimensional processes are shared to reduce the number of hardware components in the system. 
     Further operating efficiency is achieved by mapping address data relating to the graphics subsystem components into the host system virtual memory. The application processes residing in the host are thereby able to communicate directly with the graphics subsystem components, as, e.g. the structure memory, without the need of a direct memory access hardware arrangement or device drivers. 
     Accordingly, the present invention achieves a high performance, three dimensional graphics capability feasible in a stand-alone workstation configuration by maximizing the processing capabilities of interactive components. Hierarchical data structures are built in memory to permit the definition of complex data structures representative of the primitives, attributes and geometric transformations of three dimensional objects. The asynchronous traversal of the data structures built in the memory together with the traversal control functions coordinate and control the flow of graphics data and commands to a graphics pipeline for ordered processing and display in a manner that readily permits efficient processing and display of a multiple of application processes. 
     For a better understanding of the above and other features and advantages of the invention, reference should be made to the following detailed description of a preferred embodiment of the invention and to the accompanying drawings. 
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS 
     FIG. 1 is a block diagram of a computer graphics system in accordance with the present invention. 
     FIG. 2 is a block diagram of the graphics subsystem of FIG. 1. 
     FIG. 3 is a block diagram of the software organization for the computer graphics system of the present invention. 
     FIG. 4 is a block diagram of the structure memory of the graphics of FIG. 2. 
     FIG. 5 is a block diagram of the organization of a node memory structure of a graphics data structure pursuant to the present invention. 
     FIG. 6 is a block diagram of the BI bus memory map of the invention. 
     FIG. 7 is an exploded view block diagram of the reserved I/O space of the block diagram of FIG. 6. 
     FIG. 8 is a block diagram of the graphics context and traversal model for bitmap graphics processing. 
     FIG. 9 is a block diagram of the bitmap root. 
     FIG. 10 is a block diagram of the bitmap graphics context. 
     FIG. 11 is a block diagram of the bitmap cell array. 
     FIG. 12 is a block diagram of the bitmap display context. 
     FIG. 13 illustrates, in block diagram form, the connection between a graphics context and the virtual root node of a data structure. 
     FIGS. 14a,b,c illustrate examples of various reference nodes. 
    
    
     DETAILED DESCRIPTION OF A PREFERRED EMBODIMENT OF THE INVENTION 
     System Overview 
     Referring now to the drawings and initially to FIG. 1, there is illustrated, in block diagram form, the graphics workstation system according to the invention. A first or host subsystem includes a host central processing unit 10, a host memory 11, a tape controller 12, a control processor 13 and a disk controller 14. The host subsystem components 10, 11, 12, 13 are interfaced with one another by means of a primary bus 15. 
     A preferred host subsystem for advantageous implementation of the teachings of the invention comprises a Scorpio or Digital KA825 host processor utilized as the host central processing unit 10, a 4-Mbyte MS820-BA memory module as the host memory 11, a DEBNx Ethernet local area network and TK50 95 Mbyte streaming tape drive as the tape controller 12, an RD54 150-Mbyte nonremovable-disk drive and an RX50 818-kbyte diskette drive as the disk controller 14, an Aurora or Digital KA800 control processor to function as the control processor 13 and a VAX Bus Interconnect or VAX BI synchronous, time-multiplexed, 32-bit primary bus as the bus 15. The Scorpio processor is a single board VAX processor which executes the complete VAX instruction set and runs either the VMS or ULTRIX operating system and applications. The Scorpio host processor, Aurora control processor, VAX BI bus and other host subsystem components are marketed by the Digital Equipment Corporation. 
     The control processor 13 is provided with a local or II 32 bus 16 to interface the control processor 13 with a graphics subsystem 17. The Aurora control processor 13 therefore acts as an interface between the graphics subsystem 17 and the BI bus (primary bus) 15. The control processor 13 also performs input and output pre-processing for interactive perphireal devices such as a keyboard 18, a button box 19, a mouse 20, a tablet 21 and a dial box 22 which are connected to the control processor 13 by means of a peripheral repeater box 23 through a serial data line 24, as illustrated in FIG. 1. The peripheral repeator box 23 is utilized to power the peripheral devices 18, 19, 20, 21, 22 at the monitor site and to collect peripheral signals from the peripheral devices 18, 19, 20, 21, 22. The peripheral repeater box organizes the collected peripheral signals by packetizing the signals and sending the packets to the host central processing unit 10 via the control processor 13. The peripheral repeater box 23 also receives packets from the host processing unit 10 via the control processor 13, unpacks the data and channels the unpacked data to the appropriate peripheral device 18, 19, 20, 21, 22. For a more detailed description of the input and output pre-processing functions of the control processor 13 and the peripheral repeator box 23, reference should be made to co-pending application Ser. No. 07/085,097, now U.S. Pat. No. 4,905,232, entitled Peripheral Repeater Box, filed on even date herewith. 
     Moreover, the Aurora control processor 13 is advantageously operable to emulate a console for the Scorpio host central processing unit 10. The console emulation is accomplished through the use of a serial data line 25 between the control processor 13 and the host central processing unit 10. The Aurora control processor 13 may therefore be used to run diagnostics and to debug the host subsystem without the need of additional equipment. For a more detailed description of the console emulation function of the control processor 13, reference should be made to copending application Ser. No. 07/084,930, now U.S. Pat. No. 4,903,218 entitle Console Emulation for Graphics Workstation, filed on even date herewith. 
     Pursuant to the preferred embodiment of the invention, the graphics subsystem 17 comprise a Shadowfox graphics card set marketed by the Evans &amp; Sutherland Computer Corporation. The primary function of the graphics subsystem 17 is to store graphics data structures built by a plurality of application programs residing in the central processing unit 10 and to process, manipulate and display the graphics data structures, as will appear. Referring to FIG. 2, the Shadowfax graphics card set includes a structure memory 26 interfaced with the control processor 13 by the local II 32 bus 16. As will be described in more detail below, the structure memory 26 comprises a 4-Mbyte memory to store the graphics data structures built by application programs in the host central processing unit 10. 
     An asynchronously operational structure walker 27 is interfaced with the control processor 13 by the II32 bus 16 and with the structure memory 26 by a structure memory bus 28. The structure walker 27 is a special-purpose, 32 bit, bit-slice microprocessor that traverses the graphics data structures stored in the structure memory 26 on a continuous basis and sends the graphics data to the graphics pipeline processor 29 through line 30. 
     In accordance with the design and mode of operation of the Shadowfax graphics subsystem, the graphics pipeline processor 29 organizes the data received from the structure walker 27 into packets and performs graphics transformations, matrix multiplication, clipping, perspective division and viewport mapping. Accordingly, the graphics data structures, as processed by the graphics pipeline processor 29, are transformed from the data structure world space data as implemented by a user through an application program in the host central processing unit 10 into displayable screen space data relative to the physical dimensions of the screen upon which the object is to be displayed. 
     A pair of data taps 31,32 examines each command and data packet received from the output of the graphics pipeline processor 29 to determine whether to send the packets further down the pipeline or to send the packets into a graphics data manager 33, which forwards the packets to the appropriate destinations. For example, X, Y, Z and color data packets are sent directly to a delta/depth cue calculator 34 for calculation of line slope, adjusted end points and status flags which describe the orientation of a line. Color data and Z data are mixed with background colors to determine relative red, green and blue values. The delta/depth cue calculator output is sent to a pixel processor 35 for calculations in line drawing algorithms. The graphics data manager 33 is used to load all valid draw commands for loading into the pixel processor 35 and further operates to buffer pipeline commands to a rendering processor 36 and to buffer data from the rendering processor 36 to the pixel processor 35. As will be described in more detail below, the rendering processor 36 is used in the three-dimensional graphics process to render polygons. 
     The pixel processor 35 comprises sixteen identical processors which draw antialiased and depth-cued lines using the endpoint and slope data produced by the delta/depth cue calculator 34 as well as the polygon rendering data provided by the rendering processor 36. The data from the pixel processor 35 is sent to a frame buffer 37 which comprises a 1024×1024 pixel memory to contain the pixel image generated for the system monitor 38. The frame buffer 37 provides a 1024×864, 60 hz noninterlaced, raster-scan display format. 
     A video controller 39 receives the output from the frame buffer 37 and converts the digital data to an analog signal to drive the monitor 38. In the preferred embodiment, the monitor 38 comprises a Digital VR290-DA/D3/D4 nineteen inch color monitor having a 1024×864 pixel image area. The video controller 30 also contains a window look up table to determine the video format for the display and a color look up table of color values to define the red, green and blue components of the pixels. A graphics data bus 40 is provided to interface the video controller 30 and the various other components of the graphics subsystem 17, as illustrated in FIG. 2. 
     Subsystem Mapping 
     Subsystem mapping refers to a technique utilized in the present invention to allow the host processor 10 to directly access local RAM in the control processor 13, structure memory 26 and various registers in the graphics subsystem 17. These components are directly mapped into host system virtual memory. Subsystem mapping is highly advantageous in the operation of the system of the present invention, which is a &#34;data-driven&#34; machine, as will appear. 
     In a conventional system, the method that is used to access hardware external to a CPU is through the use of a device driver. A device driver is a program which is specifically tailored to handle communications between a host CPU and a specific device, i.e., memory, disk unit, tape unit, etc. Thus, when the CPU wishes to access external device memory, it invokes a device driver which either loads device memory directly through the use of registers or sets up a direct memory access (DMA) operation. For DMA, the driver locks down the user&#39;s data into physical memory (DMA hardware requires that the data be locked into physical memory), sets up source and destination addresses, and then invokes DMA hardware to get the information transferred from source to destination. 
     Generally, this DMA approach is very acceptable. However, in a data-driven machine such as the present invention, the cost of such approach would be prohibitive. In the present graphics system, the host central processing unit&#39;s main function is to send commands to the graphics subsystem 17. This would require the host central processing unit 10 to utilize DMA hardware for almost every operation it performed. Thus, it was with this problem in mind that subsystem mapping scheme was devised. 
     The host central processing unit 10 shares the BI bus 15 with system memory 11 and the control processor 13 (See FIG. 1). The control processor&#39;s local bus is the II32 local bus 16. On bus 16 are the local control processor RAM (1 Mbyte), local registers, and components of the graphics subsystem 17 including structure memory 26, structure walker 27, graphics pipeline 29, graphics data manager 33 and rendering processor 36, pixel processors 35 and the frame buffer 37. Note that not all the above components are physically connected to the II32 bus (See FIG. 2). The subsystem mapping scheme permits the host central processing unit 10 to directly access II32 bus components. 
     To accomplish the direct access, the II32 bus 16 components are mapped into the reserved I/O space of the BI bus (primary bus) memory map. FIG. 6 illustrates the BI memory map and FIG. 7 sets forth the details of the reserved I/O space of the memory map of FIG. 6 where the components are mapped. Upon system initialization, a device driver of the host central processing unit 10 is invoked to perform the mapping. The first step it performs is to set up two mapping registers in the control processor 13. The mapping registers themselves are mapped into the host virtual address space by the operating system. The first register, SADR, reflects the starting address of the reserved I/O space in the BI memory map which is 20800000 HEX. The second register, EADR, reflects the ending address of the reserved I/O space in the BI memory map which is 22000000 HEX. This is accomplished by the device driver simply writing the start and end address into the respective registers. The control processor 13 microcode relocates its own local RAM to be within this address range. Once this step is performed the physical mapping has been accomplished. 
     The next step that the host device driver performs is to map each II32 component (control processor RAM, structure memory 26 and graphics subsystem 17 registers) into the host&#39;s system virtual address space (Sφ). This step is required because host software is incapable of specifying physical addresses due to the inclusion of memory management (MM) hardware on the host central processing unit 10. This hardware is always running and screening addresses output by the host central processing unit 10. Each address is assumed to be a virtual address, therefore, the memory management hardware will always try to perform a level of translation with that address to create a physical address. The level of translation depends on whether the address is a system virtual address or a process virtual address. This distinction is important because each goes through a different translation table and translation mechanism. Process virtual addresses are process specific and, if used for purpose of present invention, every process would have to map to the memory itself. This would give every process 4 MBytes of virtual address space added to its own address space. Thus, in accordance with the present invention, by selecting the II32 bus mapping to be system virtual addresses, every process on the system can have access to this bus without wasting memory resources. This also reduces the complexity of computations used to determine physical addresses referenced by the graphics subsystem. 
     The last step that the host device driver performs is to unprotect Sφ pages that contain the II32 bus component&#39;s virtual addresses. By unlocking these pages, any process on the system can access this system virtual address space. Generally, Sφ pages contain operating system software and data that not every process can access. If an Sφ page is locked, the only way to access these virtual addresses is through the use of system calls. This would add more complexity to the system and increase the overhead. Thus by unlocking the Sφ pages, the use of system calls are eliminated. 
     After the host device driver has performed the steps described above, the mapping is complete. Now each process has direct read/write access to any of the mapped II32 bus components because these components are directly mapped into the host&#39;s virtual memory. Each process can treat these components as its own local memory. Therefore, the need for the use of direct memory access hardware, device drivers or operating system calls is eliminated. 
     Memory and Software Organization 
     From the above description, it should be understood that the graphics subsystem 17 operates essentially in an asynchronous mode determined by the asynchronous operation of the structure walker 27 which, as described above, controls the flow of data from the structure memory 26 to the other components of the graphic subsystem 17 through the continuous, sequential traversal of the graphics data structures. The entire data flow through the graphics pipeline is a function of the structure walker operation. As will be described in more detail below, the host central processing unit 10 executes application programs to build graphics data structures in hierarchical node structures representative of the three dimensional objects to be displayed The node structures are stored in the structure memory 26. 
     Conditional Nodes of a Graphics Data Structure 
     A graphics data structure consists of all the data which describes an object and how it is displayed. A graphics data structure is a hierarchical collection of nodes and the paths that connect them. 
     A node is a set of executable commands and data. The structure walker 27 traverses each node in order, following one or more pointers in each node which link the node to the rest of the data structure. As it traverses the node, the structure walker 27 extracts the commands and data and sends them down the graphics pipeline, where they eventually result in the display of the object defined by the data structure. 
     The data structure exists in a graphics environment defined by a graphics context which will be described in more detail below. The graphics context is connected to the system data structure through a virtual root node. A virtual root node is simply the top-most node created by the user stemming from the graphics context that was created by the system as shown in FIG. 13. 
     While building a data structure, the nodes that form the data structure offer a wide range of functions i.e. from describing graphics primitives to controlling traversal flow. Nodes are linked together in groups or structures, by first calling the structure graphics routine (SGR): 
     SGR$BEGIN --  STRUCTURE (context); 
     and then calling the routines that create the node, and ending the sequence with the routine SGR$END --  STRUCTURE (context, handle). The result is that the pointers link the nodes together thus permitting the structure walker 27 to traverse the nodes in their correct order as described below. 
     There are six node classifications for creating data structures. The first three being: 
     Primitive nodes--Contain graphics data for vectors, polygons and strings. 
     Attribute nodes--Control the appearance of graphics primitives such as line color, line pattern, shading and lighting 
     Transformation nodes--Describe how data is viewed on the screen. Transformation nodes control the composition of matrices for graphics transformation and normal transformation, and for the viewport. For example, if a primitive node builds a cube, a transformation node can scale and rotate it to make a brick. 
     The next three nodes are used to create advanced graphics data structures. 
     REFERENCE NODES 
     Hierarchical structures are built with reference nodes. A reference node instructs the structure walker 27 to traverse another structure (referred to as a &#34;substructure&#34; of the calling structure) before continuing with the traversal of the structure containing the reference node. Reference nodes operate in three modes: restore, no restore and branch. The ref --  mode parameter of the routine that creates the node defines the mode. These modes control the manner in which changes to the hierarchical graphics state affect the traversal of other parts of the graphics data structure. 
     Restore Mode 
     A reference node set to restore mode instructs the structure walker 27 to save the current graphics state such as the current transformation matrix, current attribute settings, etc. on a stack before traversing the referenced substructure, then to restore that state when it has finished traversing the substructure. As a result, changes in the hierarchical graphics state made in a substructure do not affect the graphics state of higher structures. 
     No-Restore Mode 
     A reference node set to no-restore mode redirects the structure walker 27 but does not instruct the structure walker to save the hierarchical graphics-state and restore it upon returning to the reference node. This mode is useful in at leaset two situations: When you are sure that a referenced substructure will not change the graphics state and you want to optimize traversal performance, and when you want changes in graphics state at a lower hierarchical level to affect the traversal of an equal or higher level of the data structure. 
     Branch Mode 
     As with the restore and no-restore modes, a reference node set to branch mode redirects the structure walker traversal. However, when the structure walker 27 finishes traversing the referenced substructure, it does not return to the reference node; as a result, there is no need to save or restore the graphics state. Branch reference mode is usually used with conditional refercnce nodes which select among two or more substructures. It is similar to the &#34;GOTO&#34; statement in a programming language. 
     Reference nodes are of two types: conditional and unconditional. Both node types can perform restore, no-restore, and branch references. Conditional nodes select one among two or more alternate traversal paths depending on the value of one or two operands. For example, one type of conditional node compares whether operands are equal to, greater than, or less than each other. Unconditional nodes reference a single substructure with the option of returning to the higher-level structure when the structure walker 27 finishes traversing the referenced structure. FIGS. 14a-c give examples of various kinds of references. Note that an &#34;R&#34;, &#34;NR&#34;, or &#34;B&#34; in the right side of a reference node in FIGS. 14a-c indicates whether the reference is of the restore, no-restore, or branch variety; in addition, a circle is placed on the main reference pointer for no restore references as an additional visual clue, and nodes following a branch reference are shaded gray to show that the structure walker 27 never traverses these nodes. 
     FIG. 14a shows a data structure featuring a Call/Restore node which displays a red circle with a blue square. Because the reference node restores state, the red line-color attribute does not affect the line-color attribute set in the calling structure. 
     FIG. 14b shows a data structure featuring a conditional Test/No Restore node which displays either a blue or a red square, depending upon whether the operand tested by the Test/No Restore node is true or false. Because the reference node does not restore state, the line-color attribute set in the referenced structure does affect the color displayed by the calling structure. 
     FIG. 14c shows a data structure featuring a conditional Compare/Branch node which will display one of the three referenced substructures, depending on the values of the operands compared by the Compare/Branch node. Note that diagrams of substructures that cannot fit on the page are represented by labeled frames. 
     Assignment Nodes 
     The assignment nodes set up and manipulate the values (operands) that are tested by conditional reference nodes, permitting dynamic control of how a given conditional reference node selects the path of traversal. The nodes perform operations on data contained in structure memory locations. The operations include move, logical OR (set bits), logical AND NOT (clear bits) add, subtract, logical XOR. 
     Special Purpose Nodes 
     The special purpose nodes allow you to build custom nodes, use the same data at different places in the structure, and store unused data. This saves both structure memory space and editing time. Three special purpose nodes are provided; a data node, a generic node, and an indirect node. These nodes can provide increased flexibility by allowing the application to tailor a data structure for its own needs. 
     Data nodes are provided to contain application data in fields which are reserved for the application. The structure walker ignores data in the data node, and follows the next pointer. 
     The generic node contains commands and data that go to the pipeline. The structure walker 27 does not process information in a generic node, but passes this node to the graphics subsystem 27 without recording changes in the subsystem state. Generic nodes can change the state of the graphics subsystem, but the structure walker does not restore changes made this way. 
     The indirect node provides the ability to reference data in one node from another node in the data structure. For example, an application can define a node containing line color data and use indirect nodes to reference the information in the indirect node. This saves memory and allows changes to the color definitions without editing many nodes throughout the structure. Any primitive, attribute, and transformation operations can be done using indirect nodes. 
     Advanced graphic data structures are created by the routines shown in Table 1. 
     
                                           TABLE 1__________________________________________________________________________Advanced Graphic Data Structure RoutinesSGR   Parameter__________________________________________________________________________ 1.   SGR$BEGIN.sub.-- STRUCTURE               context 2.   SGR$END.sub.-- STRUCTURE               context, handle 3.   SGR$CALL         context, reference.sub.-- mode,               reference.sub.-- handle, handle 4.   SGR$TEST         context, reference.sub.-- mode, mode,               opspec, true.sub.-- handle, false               handle, handle 5.   SGR$TEST.sub.-- AND.sub.-- CLEAR               context, reference.sub.-- mode, mode,               opspec, true.sub.-- handle, false               handle, handle 6.   SGR$COMPARE      context, reference.sub.-- mode, mode1,               mode2, opspec2, less.sub.-- handle,               equal.sub.-- handle, greater.sub.-- handle,               handle 7.   SGR$CASE         context, reference.sub.-- mode, mode,               opspec, count, otherwise               handle, case.sub.-- handles, handle 8.   SGR$TEST.sub.-- SET               context, reference.sub.-- mode, mode1,               opspec1, mode2, opspec2, true               handle, false.sub.-- handle, handle 9.   SGR$TEST.sub.-- CLEAR               context, reference.sub.-- mode, mode1,               opspec1, mode2 opspec2, true               HANDLE, FALSE.sub.-- handle, handle10.   SGR$MOVE         context, mode1, opspec1, mode2,               opspec2, handle   SGR$MOVE.sub.-- BLOCK               context, size, mode1 , opspec1,               mode2, opspec2, handle   SGR$MOVE.sub.-- MASK               context, mask, mode1, opspec1,               mode2, opspec2, handle   SGR$SET.sub.-- BITS               context, mode1, opspec1, mode2,               opspec2, handle   SGR$CLEAR.sub.-- BITS               context, mode1, opspec1, mode2,               opspec2, handle   SGR$ADD          context, mode1, cpspec1, mode2,               opspec2, handle   SGR$SUB          context, mode1, cpspec1, mode2,               opspec2, handle   SGR$XOR          context, mode1, opspec1, mode2,               opspec2, handle   SGR$GENERIC      context, size, data, handle   SGR$INDIRECT     context, to.sub.-- handle, handle20.   SGR$INDIRECT     context, to.sub.-- handle, handle   SGR$DATA         context, size, data, handle__________________________________________________________________________ 
    
     The use of conditional nodes provide the user with greater flexibility in the creation of advanced data structures. Referring to Table 2 above, conditional nodes are created by calling routines 4-9 assignment nodes by the routines 10-17 and special purpose nodes by the routines 18-21. 
     Conditional Reference Nodes 
     Conditional reference nodes redirect the traversal path of the structure walker 27 based upon either a true/false test or a value comparison. Based on the outcome of the test, the conditional reference node instructs the structure walker 27 to follow a predetermined traversal path associated with the test result. 
     The test performed by the conditional reference nodes use values stored in one or two operands (depending on the node type) in the node. The value of these operands are set by the manipulations of the assignment nodes thus permitting dynamic control of how a given conditional reference node selects the path of traversal. These operands are retrieved by use of the four access modes described in Table 2 and are the subject of the present invention. 
     The access modes are specified by constants set in the mode, mode1 or mode2 parameters (depending on the node type) of the routine that creates the node. The access modes tell the system how to interpret the operational specifier (opspec) parameter argument of the routine. The mode1 parameter specifies the access of opspec1, and mode2 specifies the access of opspec2. 
     
                       TABLE 2______________________________________Operand Access ModesConstant         Mode Description______________________________________SGR$K.sub.-- IMMEDIATE            The operand is the current            value stored as the operand            specifier (opspec) a command            parameter in the node.SGR$K.sub.-- ABSOLUTE            The operand is contained in the            structure memory virtual            address stored as the operand            specifier in the node.SGR$K.sub.-- REGISTER            The operand is contained in one            of three registers numbered            (0-2). These registers are            special locations in structure            memory which can be saved and            restored as part of the            hierarchical graphics state.            All three registers can be used            to store an operand, but            register 0 must be reserved for            use as a base-address register            when displacement mode is used.SGR$K.sub.-- DISPLACEMENT            The operand is located in the            structure memory virtual            address obtained by adding the            value stored in the operand            specifier to the contents of            register 0.______________________________________ 
    
     The test performed by the conditional reference node uses the value of the operand at the time of traversal; this may be the operand passed to the node-building routine when it was called, or an assignment node may have changed the value of the operand as detailed below. 
     The Operand access modes are important in the use of assignment and reference nodes. By use of the access modes, assignment nodes can create additional data or general data in the structure memory. The reference nodes can then be made to branch according to the data created. The use of special purpose nodes allows the data to be sent to the graphics subsystem 17. In this way, the data structure can in effect write a &#34;subprogram&#34; and execute it during the traversal of the structure. This provides for a more general functionality as well as a more efficient use of memory resources than present methods whereby conditional branching takes place on a fixed location such as a condition register. 
     Examples of conditional reference and assignment nodes are as follows: 
     °TEST 
     °TEST --  AND --  CLEAR 
     °COMPARE 
     °CASE 
     °TEST --  SET 
     °TEST --  CLEAR 
     The test node is created by the routine: 
     SGR$TEST (context, reference --  mode, mode, opspec, true handle, false --  handle, handle) 
     This node performs a simple true/false test on an operand and directs the structure walker to traverse one of two substructures depending on whether the results of the test is true (nonzero) or false (zero). The value of the operand remains unchanged. 
     The test --  and --  clear Node is created by the routine: 
     SGR$TEST --  AND CLEAR (context, reference --  mode, mode, opspec, true --  handle, false --  handle, handle) 
     This node performs a true/false test similar to the test node. It first tests the value of an operand, then sets the value of the operand to zero (false). Because it clears the operand (that is, sets it to a false condition), on subsequent traversal this node would direct the structure walker 27 down the path associated with a true condition only if the operand were reset to true once again. 
     The compare node is created by routine: 
     SGR$COMPARE (context, reference --  mode, mode1, opspec1, mode2, opspec2, less --  handle, equal --  handle, greater handle, handle) 
     This node performs a test on two operands to determine which, if either, is greater, and directs the structure walker to traverse one of three substructures, depending on whether the first operand is less than, equal to, or greater than the second operand. The operands remain unchanged. 
     The case node is created by the routine: 
     SGR$CASE (context, reference --  mode, mode, opspec, count, otherwise --  handle, case --  handles, handle) 
     This node tests the value of an operand and directs the structure walker to traverse a substructure assigned to that value; if the value of the operand is not associated with substruture, then a defalt substruture is traversed. The operand remains unchanged. This node allows the selection of a number of traversal paths, depending on the value of the operand in the node. 
     The test --  set and test --  clear Nodes are created with the routines: 
     SGR$TEST --  SET (context, reference --  mode, mode1, ops.pec1, mode2, opspec2, true --  handle, false --  handle, handle) 
     SGR$TEST --  CLEAR (context, reference --  mode, mode1, opspec1, mode2, opspec2, true --  handle, false --  handle, handle) 
     These nodes allow the performance of mask-like tests to determine which parts of the graphics data structure will be traversed. The test --  set determines if the bits which are set in the first operand are also set in the second operand. If the test result is true (that is, if the logical AND of the two operands is equal to the first operand), then the first substructure is traversed; if false, the second substructure is traversed. 
     The test --  clear determines if the bits which are clear in the first operand are also clear in the second operand. If the test result is true (that is, if the logical AND of the two operands is equal to 0), then the first substructure is traversed; if false, the second structure is traversed. 
     For instance, a mask could be store in register 1 which represents whether certain features are &#34;enabled&#34; or &#34;disabled.&#34; A test --  set node could be used to test whether a feature was enabled and, if so, direct the structure walker to traverse the appropriate substructure. 
     Assignment Nodes 
     Assignment nodes provide additional flexibility in the use of conditional reference nodes by modifying their operands as a result of data structure traversal. In other words, the condition to be tested by the conditional reference nodes can be different at each traversal, depending on how assignment nodes are used to modify their operands. 
     Assignment nodes perform arithmetic or bit operations on the operands used by conditional reference nodes. The following are assignment nodes: 
     °MOVE 
     °MOVE --  BLOCK 
     °MOVE --  MASK 
     °SET --  BITS 
     °CLEAR --  BITS 
     °ADD 
     °SUB 
     °XOR 
     The move node is created by the routine: 
     SGR$MOVE (context, mode1, opspec1, mode2, opspec2 handle) 
     This node performs a longword move operation, from the location described by opspec1 to the location described by opspec2. 
     The move --  block node is created with the routine: 
     SGR$MOVE --  BLOCK (context, size, mode1, opspec1, mode2, opspec2, handle) 
     This node performs a move operation on a block of longwords indicated by the size parameter, from the location described by opspec1 to the location described by opspec2. 
     The move --  mask node is created with the routine: 
     SGR$MOVE --  MASK (context, mask, mode2, opspec2, handle) 
     The node sets the bits specified by the mask parameter to the same values in the second operand as their corresponding values in the first operand. 
     The set --  bits node is created with the routine: 
     SGR$SET --  BITS (context, mode1, opspec1, mode2, opspec2, handle) 
     This node performs a logical OR operation, setting all the bits in the second operand which are set in the first. 
     The clear --  bits node is created with the routine: 
     SGR$CLEAR --  BITS (context, mode1, opspec1, mode2 opspec2, handle) 
     This node performs a logical AND NOT operation, clearing all the bits in the second operand which are set in the first. 
     The add node is created with the routine: 
     SGR$ADD (context, mode1, opspec1, mode2, opspec2, handle) 
     This node performs a signed longword addition of operand 1 and operand 2. The result of the addition is stored in the second operand. 
     The sub node is created with the routine: 
     SGR$SUB (context, mode1, opspec1, mode2, opspec2, handle) 
     This node performs a signed longword subtraction, subtracting operand 1 from operand 2 and storing the result in the second operand. 
     The xor node is created with the routine: 
     SGR$XOR (context, mode1, opspec1, mode2, opspec2, handle) 
     This node performs a logical XOR operation using the two operands and storing the result in the second operand. Note that if all the bits in the second operand are set, a logical NOT is performed. 
     Examples of special purpose nodes are given below. 
     The routines that build special-purpose nodes increase the flexibility and efficiency of the graphics data structure. There are three nodes as follows: 
     °Generic 
     °Indirect 
     °Data 
     The generic node is created by the routine: 
     SGR$GENERIC (context, size, data, handle) 
     The generic node provides the means of sending commands or data, or both, through the graphics pipeline; in effect, creating a custom node. The commands that are used should not affect the hierarchical graphics state. 
     The indirect Node is created by the routine: 
     SGR$INDIRECT (context, to --  handle, handle) 
     The indirect node references data in another node. An application may insert indirect nodes that reference predefined data. The routine inserts the node type of the referenced node into the indirect node being created, as well as a pointer directing the structure walker to traverse the data contained in that node. This creates a node identical to the referenced node, but located in a different part of the graphics data structure. This routine is useful in building attribute tables. This saves memory, and limits the number of changes when editing. 
     The data Node is built by the routine: 
     SGR$DATA (context, size, data, handle) 
     The data node is used for storage, or to hold data to be used by the application program. During structure traversal, the structure walker 27 passes over data in this node, but follows the next pointer. 
     The primary function of the structure walker 27 is to accurately traverse the nodes of the data structures in the proper sequential order and to process each node type correctly. The processing function of the structure walker 27 involves execution of node commands relating to further traversal of the nodes of the structure or conditional branching to alternative node branches in the node structure and the sending of the data and command information contained in the traversed nodes to the graphics pipline processor 29 for processing, as described above. 
     Software Organization 
     Referring now to FIG. 3, there is illustrated a block diagram of the software organization of the graphics system of the invention. An application 100 contains requests relating to the building of graphics data structures. Many applications 100 are present in the host central processing unit 10 to build multiple graphics data structures for manipulation and display by the graphic subsystem 17. In the preferred embodiment, the X Window System is implemented to perform the windowing and bit map graphics requests contained in the application program 100. The X window system is fully described in publications published by the Massachusetts Institute of Technology such as Xlib - C Language X Interface Protocol Version 11 by Jim Gettys, Ron Newman and Robert W. Scheifler and X Window System Protocol, Version 11 Beta Test by Robert W. Scheifler. These publications are available to use, copy, modify and distribute for any purpose without fee. Information on the X Window System may be obtained from the Massachusetts Institute of Technology Laboratory for Computer Science, 545 Technology Square, Cambridge, Mass. 02139. 
     The X Window System is based upon a client--server model. The application 100 is the client which accomplishes its work by communicating its requests to a server process 101. The server 101 performs the requested function and returns a status to the client application 100. The major components of the X Window System are an X protocol 102, the server 101 and an XLib 103. 
     The X protocol 102 defines a model for communication between a server 101 and a client 100, and also defines the model for the graphics subsystem 17. The model consists of several objects which interact in specified ways. The most fundamental object is the window, a rectangular array of pixels which may or may not be (partially) visible on the monitor 38 at a given time. Windows are in a hierarchy: in other words, windows may have sub-windows. When a sub-window is displayed, it will be clipped against its parent. The monitor is the root of the hierarchy. Each window has a unique ID, an optional property list, and may be manipulated by a process 100 other than the creating process 100. The X protocol 102 neither imposes nor encourages limits on the number of windows in existence (i.e. windows are &#34;cheap&#34;). Other objects defined by the X protocol 102 include 
     Color Maps: associations between pixel values and colors 
     pixmaps: a rectangular array of pixels 
     tiles: a special kind of pixmap used to fill regions and define cursors 
     polylines: a set of related points which are displayed in a window according to specified criteria 
     (glyph) fonts: a set of bitmaps which correspond to alphanumeric characters (includes proportional fonts) 
     The X protocol 102 also defines a number of events. These events are detected by the server 101 as, e.g., inputs received from peripheral devices via the control processor 13 and peripheral repeater box 23 (see FIG. 3) and are passed on to clients 100. Examples of events are 
     Exposure events: part of a displayed window which was previously occluded has now been uncovered 
     Keyboard events: a key on the display has been pressed 
     Button Events: a button on a pointing device (e.g. mouse 20) has been depressed. 
     Clients 100 only receive notification of events in which they have explicitly expresed interest. Events are maintained in a time-ordered queue, and can be received by clients 100 either synchronously or asynchronously. 
     The X Server 101 mediates communication between client applications 100 and the graphic subsystem 17. Each client 100 establishes a connection to the server 101 via a communications protocol. A client 100 will send commands to a server 101 to perform functions such as drawing into a window, loading fonts, manipulating the color map, expressing interest in certain events, etc. The X Server 101 will then perform the requested functions, by, e.g., sending commands to the graphics subsystem 17 via a node in the structure memory 26. 
     A server 101 is always located on the same machine as the monitor 38. It is possible for there to be more than one server per machine, and for a server to control more than one monitor 38. Each monitor 38, however, may be controlled by at most one server. 
     The server 101 provides a device independent (DDI) program which interfaces with a device dependent (DDX) program for communication from the X Window system to the specific system of the invention upon which the windowing system is operating. With respect to the present invention, the most significant feature of the DDX is the three dimensional display context functions of the traversal control implemented through a display manager 106 in the windowing server 101 to connect a window defined by a client application 100 to the three dimentional graphics structure built by the client application 100 in the structure memory 26, as will appear. In this manner, a three dimensional functionality is merged into the X Window System. 
     Xlib 103 is the Client&#39;s interface to an X Server. It is a procedural interface which corresponds to the functions provided by the underlying X protocol 102. Thus, there are calls to create windows, draw into them, etc. Since Xlib is a procedural interface, it is designed to be called from higher-level languages. 
     A window manager 104 is an application which implements a human-workstation interface. It typically provides a user with the ability to create, move, resize, iconify, and destroy windows. These actions are indicated by using the mouse 20 as a pointing device, in conjunction with button clicks and keyboard hits. Although the X protocol 102 does not specify any one window manager, there are currently several from which to choose. X provides the necessary features for a customized window manager implementation. This means that a window manager is not necessary for X applications to run and it is possible to have multiple window managers (not at the same time on the same display, however). 
     A graphic package may be layered on top of the X Window System, as, for example, a GKS o/b package. In the present invention a graphics package is used for two dimentional displays through bit map graphics. Indeed, the X Window System was devloped for use in connection with bit map graphics systems. The bit map graphics contexts and command queues are processed by the rendering processor 36, as will appear. 
     Pursuant to the invention, three dimensional graphics data structures are built by the application clients 100 directly through structured graphics routines 105 (SGR) which are provided in the host subsystem. The applications 100 utilize the various structured graphics routines 105 as required to build specific graphics data structures. The structured graphics routines execute routine requests made by the application 100 and build appropriate linked nodes in the structure memory 26. 
     The following are several examples of structured graphics routines which may be provided in the host subsystem for implementation of graphics data structures. 
     EXAMPLE 1 
     SGR$BEGIN --  STRUCTURE 
     FORMAT 
     SGR$BEGIN --  STRUCTURE(context) 
     ARGUMENTS 
     context 
     The identifier the graphics context for this subroutine call. The context argument is the address of an unsigned integer that contains the identifier of the graphics context block. 
     PURPOSE 
     To begin a structure. 
     DESCRIPTION 
     A structure is a group of nodes linked together. After calling SGR$BEGIN --  STRUCTURE, all nodes created with the same context are added to the end of the structure. No nodes are created by SGR$BEGIN --  STRUCTURE. A structure is terminated by SGR$END --  STRUCTURE. 
     The information for linking nodes is stored in the graphics context referenced by the context argument, so it is possible to build multiple structures at the same time using multiple contexts. 
     Calling SGR$BEGIN --  STRUCTURE for a context which is not building a structure is an error. 
     It may be desireable to begin each structure with a node that does nothing, such as a data node or a disabled node. This permits the structure to be referenced by multiple nodes and still permits replacement of the first true node in the structure. 
     EXAMPLE 2 
     SGR$COLOR 
     FORMAT 
     SGR$COLOR(context, red, green, blue, color) ARGUMENTS 
     context 
     The identifier of the graphics context for this subroutine call. The context argument is the address of an unsigned integer that contains the identifier of the graphics context block. 
     red 
     The red intensity of the color. The red argument is the address of an unsigned longword in F --  floating format that contains the value for red intensity. This value is in the range 0.0 (no intensity) to 1.0 (full intensity). 
     green 
     The green intensity of the color. The green argument is the address of an unsigned longword in F --  floating format that contains the value for the green intensity. This value is in the range 0.0 (no intensity) to 1.0 (full intensity). 
     blue 
     The blue intensity of the color. The blue argument is the address of an unsigned longword in F --  floating format that contains the value for the blue intensity. This value is in the range 0.0 (no intensity) to 1.0 (full intensity). 
     color 
     The color longword returned by the routine. The color argument returns the address of an unsigned longword that returns the value for color. 
     PURPOSE 
     To create a color word. 
     DESCRIPTION 
     This routine creates a color composed of red, green, and blue intensities. The format of a color word is shown in following scale. 
     Color is passed as an argument to SGR$SET --  BACKGROUND, SGR$SET --  LINE --  COLOR, and SGR$STATUS. 
     RELATED ROUTINES 
     SGR$SET --  BACKGROUND 
     SGR$SET --  LINE --  COLOR 
     SGR$SET --  SURFACE --  COLOR 
     SGR$STATUS. 
     EXAMPLE 3 
     SGR$VECTOR 
     FORMAT 
     SGR$VECTOR (context, vertex --  format, edit --  flags, count, vertex --  array, handle) 
     AGRUMENTS 
     context 
     The identifier of the graphics context for this subroutine call. The context argument is the address of an unsigned integer that contains the identifier of the graphics context block. 
     vertex --  format 
     Flags declaring the format of the vertices passed by the vertex --  array argument. The vertex --  format argument is an unsigned longword that contains the following flags: 
     
         ______________________________________Flag              Description______________________________________SGR$M.sub.-- STATUS             When set, each vertex in             the array contains a             status word.SGR$M.sub.-- X.sub.--             When set, each vertex in             the array contains a             coordinate for x.SGR$M.sub.-- Y    When set, each vertex in             the array contains a             coordinate for y.SGR$M.sub.-- Z    When set, each vertex in             the array contains a             coordinate for Z.SGR$M.sub.-- W    When set, each vertex in             the array contains a             coordinate for w.______________________________________ 
    
     edit --  flags 
     Flags specifying how the routine will format the status words of itemized vertices as it stores them in the node. The edit --  flags argument is the address of an unsigned longword that contains the following flags: 
     
         ______________________________________Flags              Description______________________________________SGR$M.sub.-- EDIT.sub.-- POLYLINE              When set, creates default              status words for itemized              vertices with separate              draw mode.SGR$M.sub.-- EDIT.sub.-- SEPARATE              When set, creates default              status words for itemized              vertices with polyline              draw mode.______________________________________ 
    
     If neither DGR$M --  EDIT --  POLYLINE nor SGR$M --  EDIT --  SEPARATE is set in the edit --  flags argument, the status words of itemized vertices are not changed and the status word must be filled in properly for each vertex. The edit --  flags argument does not affect vertices without status words. 
     count 
     The number of vertices passed by the vertex --  array argument. The count argument is the address of an unsigned longword. 
     vertex --  array 
     The array of vertices defining the vectors to be drawn. The vertex --  array argument is the address of an array of longwords; this array must contain the number of longwords equal to the value passed by the count argument multiplied by the number of vertex components indicated by the number of flags set in vertex --  format. For example, if vertex --  format declares a 3D-with-status vertex format (by setting SGR$M --  STATUS, SGR$M --  X, SGR$M --  Y, and SGR$M --  Z in the vertex --  format argument) and the count argument declares that the number of vertices is 10, then the vertex array must contain 40 longwords. Vertex components must be in the order status, x, y, z, w. All coordinates must be of the default floating-point format set in the graphics context. 
     handle 
     The identifier of the node created by this routine. The handle argument returns the address of an unsigned longword that contains the identifier. 
     PURPOSE 
     To create a vector node. 
     DESCRIPTION 
     This routine creates a vector node. When this node is traversed by the structure walker 27, data is forwarded to the garphics subsystem 17 to draw the vectors to be displayed, as described above. In order to be visible the vectors must be properly transformed (for example, they must be within the clipping planes), have correct attributes (such as a color different from the background color), and must not be obscured by polygons. 
     Each vertex can have a status word and x,y, z, and w coordinates. The status word sets the draw mode and/or itemized vector color is enabled. 
     EXAMPLE 4 
     SGR$X --  ROTATE --  MATRIX 
     FORMAT 
     SGR$X --  ROTATE --  MATRIX(context, multiply --  control, angle, matrix) 
     ARGUMENTS 
     context 
     The identifier of the graphics context for this subroutine call. The context argument is the address of an unsigned integer that contains the identifier of the graphics context block. 
     Multiply --  control 
     Specifies how the matrix argument is to be interpreted. The multiply --  control argument is the address of an unsigned longword. Acceptable values are: 
     
         ______________________________________Constant          Function______________________________________SGR$K.sub.-- REPLACE             The matrix argument             returns the new matrix             produced by this routine:             Matrix new matrixSGR$ K-PREMUILTIPLY             The matrix argument             supplies a matrix to which             the new matrix produced by             this routine is             premultiplied. The matrix             argument then returns the             resulting matrix:             Matrix New.sub.-- matrix x             matrixSGR$ K-POSTMULTIPLY             The matrix argument             supplies a matrix to which             the new matrix produced by             this routine is             postmultiplied. The             matrix argument then             returns the resulting             matrix:             matrix matrix x             new.sub.-- matrix______________________________________ 
    
     angle 
     The angle of rotation in radians. The angle argument is the address of a longword in F --  floating format. 
     matrix 
     The x-rotation matrix created by this routine. The matrix argument returns the address of a 4×4 array of longwords in F --  floating format containing the result matrix. The matrix is in row major order. 
     PURPOSE 
     To create an x-rotation matrix. 
     DESCRIPTION 
     This routine computes a rotation matrix to rotate about the x axis. The resulting rotation is angle radians clockwise as viewed from the +x axis. The rotation matrix is returned in the matrix argument. 
     Any number of additional routines may be stored in the host subsystem to enable an application process 100 to build a graphics data linked node structure representative of a three dimensional image in color for storage in the structure memory 26 and eventual traversal by the structure walker 27. The following is an example of a complete structured graphics routine library with the routines listed by function: 
     
                       TABLE 1______________________________________SGR Primitive Routines______________________________________Primitive SGRs      Arguments______________________________________SGR$POLYGON         context, vertex.sub.-- format,               flags, plane.sub.-- equation,               count, vertex.sub.-- array,               handleSGR$STRING          context, vertex.sub.-- format,               vertex, flags, count,               string, handleSGR$VECTOR          context, vertex.sub.-- format,               edit.sub.-- flags, count,               vertex.sub.-- array handle______________________________________Primitive Utility SGRs               Arguments______________________________________SGR$PLANE.sub.-- EQUATION               context, vertex.sub.-- format,               negate, count,               vertex.sub.-- array,               plane.sub.-- equationSGR$STATUS          context, flags, color,               status______________________________________ 
    
     
                                           TABLE 2__________________________________________________________________________SGR Attribute Routines__________________________________________________________________________General Attribute SGRs                 Arguments__________________________________________________________________________SGR$SET.sub.-- BACKGROUND                 context, color, handleSGR$SET.sub.-- GEOMETRY.sub.-- MASK                 context, enable.sub.-- mask,                 disable.sub.-- mask, handleSGR$SET.sub.-- INTENSITY.sub.-- RANGE                 context, minimum, maximum,                 handleSGR$SET.sub.-- LINE.sub.-- COLOR                 context, color, handleSGR$SET.sub.-- LINE.sub.-- FILTER                 context, filter, handleSGR$SET.sub.-- LINE.sub.-- PATTERN                 context, flags, dash.sub.-- mask,                 dot.sub.-- mask, mask.sub.-- bits,                 pattern.sub.-- length,                 fill.sub.-- color, handleSGR$SET.sub.-- RENDERING.sub.-- MASK                 context, enable.sub.-- mask,                 disable.sub.-- mask, handle__________________________________________________________________________Vector Attribute SGRs Arguments__________________________________________________________________________SGR$SET.sub.-- MARKER.sub.-- TYPE                 context, glyph, handleSGR$SET.sub.-- VECTOR.sub.-- DRAW.sub.-- MODE                 context, draw.sub.-- mode, handle__________________________________________________________________________Polygon Attribute SGRs                 Arguments__________________________________________________________________________SGR$SET.sub.-- LIGHT  context, light.sub.-- id, light,                 handleSGR$SET.sub.-- LIGHTING.sub.-- STYLE                 context, style, handleSGR$SET.sub.-- LIGHT.sub.-- MASK                 context, enable.sub.-- mask,                 disable.sub.-- mask, handleSGR$SET.sub.-- SHADING.sub.-- STYLE                 context, style, handleSGR$SET.sub.-- SURFACE.sub.-- COLOR                 context, side, color,                 handleSGR$SET.sub.-- SURFACE.sub.-- PROPERTIES                 context, side, properties,                 handle__________________________________________________________________________String Attribute SGRs Arguments__________________________________________________________________________SGR$DO.sub.-- STRING.sub.-- CHARACTERS                 context, handleSGR$DO.sub.-- STRING.sub.-- MATRIX                 context, handleSGR$DO.sub.-- STRING.sub.-- POSITION                 context, handleSGR$SET.sub.-- STRING.sub.-- FONT                 context, flags,                 spacing.sub.-- handle,                 process.sub.-- handle,                 glyph.sub.-- handles, handleSGR$SET.sub.-- STRING.sub.-- SPACING                 context, spacing.sub.-- vector,                 handle__________________________________________________________________________Attribute Utility SGR Arguments__________________________________________________________________________SGR$COLOR             context, flags, red,                 green, blue, color__________________________________________________________________________ 
    
     
                       TABLE 3______________________________________SGR Rendering RoutinesRendering SGRs      Arguments______________________________________SGR$BEGIN RENDERING context, style, handleSGR$END.sub.-- RENDERING               context, handle______________________________________ 
    
     
                                           TABLE 4__________________________________________________________________________SGR Transformation Routines__________________________________________________________________________Matrix Composition SGRs                  Arguments__________________________________________________________________________SGR$CONCAT.sub.-- MATRIX                  context, flags, matrix,                  normal.sub.-- matrix, handleSGR$LOAD.sub.-- MATRIX context, flags, matrix,                  normal.sub.-- matrix, handleSGR$SUBSTITUEE.sub.-- MATRIX                  context, flags, matrix,                  normal.sub.-- matrix, handle__________________________________________________________________________Modeling SGRs          Arguments__________________________________________________________________________SGR$A.sub.-- ROTATE.sub.-- MATRIX                  context, multiply.sub.-- control,                  angle, point1, point2,                  matrixSGR$SCALE.sub.-- MATRIX                  context, multiply.sub.-- control,                  vector, matrixSGR$TRANSLATE.sub.-- MATRIX                  context, multiply.sub.-- control,                  vector, matrixSGR$ROTATE.sub.-- MATRIX                  context, multiply.sub.-- control,                  angle, matrixSGR$Y.sub.-- ROTATE.sub.-- MATRIX                  context, multiply.sub.-- control,                  angle, matrixSGR$Z.sub.-- ROTATE.sub.-- MATRIX                  context, mutiply.sub.-- control,                  angle, matrix__________________________________________________________________________Viewing SGRs           Arguments__________________________________________________________________________SGR$LOOK.sub.-- AT.sub.-- VIEW.sub.-- MATRIX                  context, multiply.sub.-- control,                  from, to, up, matrixSGR$POLAR.sub.-- VIEW.sub.-- MATRIX                  context, multiply.sub.-- control,                  view.sub.-- flag, point,                  distance, azimuth,                  incidence, twist, matrix__________________________________________________________________________Projection SGRs        Arguments__________________________________________________________________________SGR$ORTHOGRAPHIC.sub.-- PROJ.sub.-- MATRIX                  context, multiply.sub.-- control,                  height, aspect, front,                  back, matrixSGR$PERSPECTIVE.sub.-- PROJ.sub.-- MATRIX                  context, multiply.sub.-- control,                  angle, height, aspect,                  front, back, matrix__________________________________________________________________________String Matrix SGRs     Arguments__________________________________________________________________________SGR$SET.sub.-- STRING.sub.-- MATRIX                  context, matrix, handle__________________________________________________________________________General Matrix Utility SGRs                  Arguments__________________________________________________________________________SGR$COPY.sub.-- MATRIX context, from.sub.-- matrix,                  to.sub.-- matrixSGR$IDENTITY.sub.-- MATRIX                  context, matrixSGR$INVERSE.sub.-- MATRIX                  context, matrix,                  inverse.sub.-- matrixSGR$MULTIPLY.sub.-- MATRICES                  context, prematrix,                  postmatrix, result.sub.-- matrixSGR$NORMAL.sub.-- MATRIX                  context, prematrix                  normal.sub.-- matrix__________________________________________________________________________ 
    
     
                       TABLE 5______________________________________SGR Viewport RoutinesViewport SGRs        Arguments______________________________________SGR$CONCAT.sub.-- VIEWPORT                context, left.sub.-- bottom,                right.sub.-- top, handleSGR$LOAD.sub.-- VIEWPORT                context, left.sub.-- bottom,                right.sub.-- top, handleSGR$SUBSTITUTE.sub.-- VIEWPORT                context, left.sub.-- bottom,                right.sub.-- top, handle______________________________________ 
    
     
                       TABLE 6______________________________________SGR Structure Building RoutinesStructure Building SGRs                  Arguments______________________________________SGR$BEGIN.sub.-- STRUCTURE                  contextSGR$END.sub.-- STRUCTURE                  context, handle______________________________________ 
    
     
                       TABLE 7______________________________________SGR Reference Routines           Arguments______________________________________Unconditional Reference SGRSGR$CALL          context, reference.sub.-- mode,             reference.sub.-- handle, handleConditional Reference SGRsSGR$CASE          context, reference.sub.-- mode,             mode, opspec, count,             otherwise.sub.-- handle,             case.sub.-- handles, handleSGR$COMPARE       context, reference.sub.-- mode,             mode1, opspec1, mode2,             opspec2, less.sub.-- handle,             equal.sub.-- handle,             greater.sub.-- handle, handleSGR$TEST          context, reference.sub.-- mode,             mode, opspec, true.sub.-- handle,             false.sub.-- handle, handleSGR$$EST.sub.-- AND.sub.-- CLEAR             context, reference.sub.-- mode,             mode, opspec, true-handle,             false.sub.-- handle, handleSGR$TEST.sub.-- CLEAR             context, reference.sub.-- mode,             mode1, opspec1, mode2,             opspec2, true.sub.-- handle,             false.sub.-- handle, handleSGR$TEST.sub.-- SET             context, reference.sub.-- mode,             mode1, opspec1, mode2,             opspec2, true-handle,             false.sub.-- handle, handleArithmetic andAssignment SGRsSGR$ADD           context, mode1, opspec1,             mode2, opspec2, handleSGR$CLEAR.sub.-- BITS             context, mode1, opspec1,             mode2, opspec2, handleSGR$MOVE          context, mode1, opspec1,             mode2, opspec2, handleSGR$MOVE.sub.-- BLOCK             context, size, mode1,             opspec1, mode2, opspec2,             handleSGR$MOVE.sub.-- MASK             context, mask, mode1,             opspec1, mode2, opspec2,             handleSGR$SET.sub.-- BITS             context, mode1, opspec1,             mode2, opspec2, handleSGR$SUB           context, mode1, opspec1,             mode2, opspec2, handleSGR$XOR           context, mode1, opspec1,             mode2, opspec2, handle______________________________________ 
    
     
                       TABLE 8______________________________________SGR Graphics Context Routines______________________________________Graphics Context SGRs  Arguments______________________________________SGR$COPY.sub.-- CONTEXT                  from.sub.-- context,                  to.sub.-- contextSGR$CREATE.sub.-- CONTEXT                  display, context______________________________________Graphics Context Editing SGRs-Inquiry                Arguments______________________________________SGR$INQ.sub.-- DEF.sub.-- BASE.sub.-- GEOMETRY                  context, geometrySGR$INQ.sub.-- DEF.sub.-- BLINK.sub.-- PERIODS                  context, on, offSGR$INQ.sub.-- DEF.sub.-- BUFFERING.sub.-- MODE                  context, modeSGR$INQ.sub.-- DEF.sub.-- DRAWABLE                  context, drawableSGR$INQ.sub.-- DEF.sub.-- FIRST.sub.-- PICK                  context,                  pick-numberSGR$INQ.sub.-- DEF.sub.-- FP.sub.-- FORMAT                  context, fp.sub.-- format,                  fp.sub.-- block.sub.-- exponentSGR$INQ.sub.-- DEF.sub.-- HIT.sub.-- BOX.sub.--                  context,LOCATION               hit.sub.-- box.sub.-- locationSGR$INQ.sub.-- DEF.sub.-- HIT.sub.-- BOX.sub.-- SIZE                  context,                  hit.sub.-- box.sub.-- sizeSGR$INQ.sub.-- DEF.sub.-- LINE.sub.-- FILTER                  context,                  filter.sub.-- number,                  filter.sub.-- valuesSGR$INQ.sub.-- DEF.sub.-- PATH.sub. -- STACK                  context, path.sub.-- sizeSGR$INQ.sub.-- DEF.sub.-- PICK.sub.-- ID.sub.-- STACK                  context,                  pick.sub.-- id.sub.-- sizeSGR$INQ.sub.-- DEF.sub.-- PICK.sub.-- LIMIT                  context, pick.sub.-- limitSGR$INQ.sub.-- DEF.sub.-- PICK.sub.-- QUEUE                  context, pick.sub.-- size,                  path.sub.-- size,                  pick.sub.-- id.sub.-- sizeSGR$INQ.sub.-- DEF.sub.-- REPEAT.sub.-- PERIOD                  context, periodSGR$INQ.sub.-- DEF.sub.-- TRAVERSAL.sub.-- ID                  context,                  traversal.sub.-- idSGR$INQ.sub.-- DEF.sub.-- TRAVERSAL.sub.-- MODE                  context, modeflagsSGR$INQ.sub.-- DEF.sub.-- UPDATE.sub.-- MODE                  context,                  update.sub.-- modeSGR$INQ.sub.-- DEF.sub.-- VERTEX                  context, vertex.sub.-- 4dSGR$INQ.sub.-- DEF.sub.-- VIRTUAL.sub.-- ROOT                  context, handle______________________________________Graphics Context Editing SGRs-Setting                Arguments______________________________________SGR$SET.sub.-- DEF.sub.-- BASE.sub.-- GEOMETRY                  context, geometrySGR$SET.sub.-- DEF.sub.-- BLINK.sub.-- PERIODS                  context, on, offSGR$SET.sub.-- DEF.sub.-- BUFFERING.sub.-- MODE                  context, modeSGR$SET.sub.-- DEF.sub.-- DRAWABLE                  context, drawable,                  attach.sub.-- detachSGR$SET.sub.-- DEF.sub.-- FIRST.sub.-- PICK                  context,                  pick.sub.-- numberSGR$SET.sub.-- DEF.sub.-- FP.sub.-- FORMAT                  context, fp.sub.-- format,                  fp.sub.-- block.sub.-- exponentSGR$SET.sub.-- DEF.sub.-- HIT.sub.-- BOX.sub.--                  context,LOCATION               hit.sub.-- box.sub.-- locationSGR$SET.sub.-- DEF.sub.-- HIT.sub.-- BOX.sub.-- SIZE                  context,                  hit.sub.-- box.sub.-- sizeSGR$SET.sub.-- DEF.sub.-- LINE.sub.-- FILER                  drawable,                  filter.sub.-- number,                  filter.sub.-- valuesSGR$SET.sub.-- DEF.sub.-- PATH.sub.-- STACK                  context, path.sub.-- sizeSGR$SET.sub.-- DEF.sub.-- PICK.sub.-- ID.sub.-- STACK                  context,                  pick.sub.-- id.sub.-- sizeSGR$SET.sub.-- DEF.sub.-- PICK.sub.-- LIMIT                  context, pick.sub.-- limitSGR$SET.sub.-- DEF.sub.-- PICK.sub.-- QUEUE                  context, pick.sub.-- size,                  path.sub.-- size,                  pick.sub.-- id.sub.-- sizeSGR$SET.sub. -- DEF.sub.-- REPEAT.sub.-- PERIOD                  context, periodSGR$SET.sub.-- DEF.sub.-- TRAVERSAL.sub.-- ID                  context,                  traversal.sub.-- idSGR$SET.sub.-- DEF.sub.-- TRAVERSAL.sub.-- MODE                  context, modelglagsSGR$SET.sub.-- DEF.sub.-- UPDATE.sub.-- MODE                  context,                  update.sub.-- modeSGR$SET.sub.-- DEF.sub.-- VERTEX                  context, vertex.sub.-- 4dSGR$SET.sub.-- DEF.sub.-- VIRTUAL.sub.-- ROOT                  context, handle______________________________________ 
    
     
                       TABLE 9______________________________________SGR Traversal Control RoutinesTraversal Control SGRs                Arguments______________________________________SGR$$ADD.sub.-- TO.sub.-- QUEUE                context, queue.sub.-- handle,                first.sub.-- handle, last.sub.-- handleSGR$$QUEUE           context, reference.sub.--                mode, first.sub.-- handle,                current.sub.-- handle,                last.sub.-- handle, handleSGR$$REMOVE.sub.-- FROM.sub.-- QUEUE                context, queue.sub.-- handle,                first.sub.-- handle, last.sub.-- handleSGR$INQ.sub.-- TRAVERSAL.sub.-- STATE                context, traversal.sub.-- type,                waitflag, stateSGR$RELEASE.sub.-- UPDATES                contextSGR$REQUEST.sub.-- TRAVERSAL                context, traversal.sub.-- type______________________________________ 
    
     
                       TABLE 10______________________________________SGR Picking RoutinesPicking SGRs        Arguments______________________________________SGR$COMPUTE.sub.-- PICK.sub.-- POINT               context, node.sub.-- picked,               type, pick.sub.-- vector, vert-               geom.sub.-- mat, user.sub.-- vectorSGR$CONCAT.sub.-- PICK.sub.-- ID               context, identifier,               handleSGR$GET.sub.-- PICK context, max.sub.-- path.sub.-- pairs,               max.sub.-- pick.sub.-- ids, status,               node.sub.-- picked, type, index,               pick.sub.-- vector,               vert.sub.-- geom.sub.-- mat,               num.sub.-- pairs.sub.-- ret, path,               num.sub.-- ids.sub.-- ret, pick.sub.-- idsSGR$LOAD.sub.-- PICK.sub.-- ID               context, identifier,               handleSGR$PRINT.sub.-- PICK               context, max.sub.-- pathpairs,               max.sub.-- pick.sub.-- ids, status,               node.sub.-- picked, type, index,               pick.sub.-- vector,               vert.sub.-- geom.sub.-- mat,               num.sub.-- pairs.sub.-- ret, path,               num.sub.-- ids.sub.-- ret, pick.sub.-- idsSGR$SUBSTITUTE.sub.-- PICK.sub.-- ID               context, identifier,               handle______________________________________ 
    
     
                       TABLE 11______________________________________SGR Input Handling RoutinesInput Handling SGRs Arguments______________________________________SGR$ALLOCATE.sub.-- DEVICE               context, deviceSGR$CONNECT.sub.-- DEVICE.sub.--               context, device, handle,TO.sub.-- MAT       geometric.sub.-- operation,               axis, matrix.sub.-- operation,               value-usage.sub.-- flagSGR$DISCONNECT.sub.-- DEVICE.sub.--               context, device,FROM.sub.-- MAT     handleSGR$SISPATCH.sub.-- DEVICE.sub.--               context, eventEVENTSGR$FIND.sub.-- DEVICE               context, display, device-               type, unit, device.sub.-- id[,               nBins[, nDims]]SGR$FREE.sub.-- DEVICE               context, deviceSGR$GET.sub.-- DEVICE.sub.-- ATTR               context, device,               attrBlockSGRGET.sub.-- DEVICE.sub.-- CHARS               context, device, nBins,               nDims, ndevice,               nextdeviceSGR$GET.sub.-- DEVICE.sub.-- VALUE               context, device,               valueBlockSGR$SET.sub.-- DEVICE.sub.-- AST               context, device,               valueBlock, eventcode,               action, parameterSGR$SET.sub.-- DEVICE.sub.-- ATTR               context, device,               attrBlockSGR$SET.sub.-- DEVICE.sub.-- LABEL               context, device, label,               countSGR$SET.sub.-- DEVICE.sub.-- VALUE               context, device,               valueBlock______________________________________ 
    
     
                       TABLE 12______________________________________SGR Structure Editing Routines______________________________________Structure Topology SGRs               Arguments______________________________________SGR$INQUIRE.sub.-- LINKS               context, handle,               prev.sub.-- handle, next.sub.-- handleSGR$INQUIRE.sub.-- REFERENCE               context, handle, index,               reference.sub.-- handleSGR$POSTFIX.sub.-- NODE               context, handle,               new.sub.-- handleSGR$PREFIX.sub.-- NODE               context, handle,               new.sub.-- handleSGR$REPLACE.sub.-- INDIRECT               context, handle,               indirect.sub.-- handleSGR$PREPLACE.sub.-- NEXT               context, handle,               new.sub.-- next.sub.-- handleSGR$REPLACE.sub.-- NODE               context, handle,               new.sub.-- handleSGR$REPLACE.sub.-- REFERENCE               context, handle, index,               reference.sub.-- handle______________________________________Node Editing SGRs-Inquiry               Arguments______________________________________SGR$INQUIRE.sub.-- BITMASKS               context, handle,               enable.sub.-- bits, disable.sub.-- bitsSGR$INQUIRE.sub.-- CHARACTERS               context, handle,               first.sub.-- postition,               last.sub.-- postition,               string.sub.-- size, result.sub.-- count,               result.sub.-- stringSGR$INQUIRE.sub.-- COLOR               context, handle, colorSGRINQUIRE.sub.-- DEFAULT.sub.--               context, handle, vertex.sub.-- 4dVERTEXSGR$INQUIRE.sub.-- FP.sub.-- BLOCK.sub.--               context, handle,EXPONENT            fp.sub.-- block.sub. -- exponentSGR$INQUIRE.sub.-- INDIRECT               context, handle,               indirect.sub.-- handleSGR$INQUIRE.sub.-- INTENSITY.sub.--               context, handle, minimum,RANGE               maximumSGR$INQUIRE.sub.-- LINE.sub.-- FILTER               context, handle, filterSGR$INQUIRE.sub.-- MATRIX               context, handle, flags,               matrix, normal.sub.-- matrixSGR$INQUIRE.sub.-- NODE.sub.--               context, handle, onoffENABLESGR$INQUIRE.sub.-- NODE.sub.-- TYPE               context, handle, node.sub.-- typeSGR$INQUIRE.sub.-- OPSPEC               context, handle,               opspec.sub.-- id, opspecSGR$INQUIRE.sub.-- PICK.sub.-- ID               context, handle,               identifierSGR$INQUIRE.sub.-- PLANE.sub.--               context, handle,EQUATION            plane.sub.-- equationSGR$INQUIRE.sub.-- REF.sub.-- COUNT               context, handle,               result.sub.-- system.sub.-- count,               result.sub.-- user.sub.-- countSGR$INQUIRE.sub.-- STRING.sub.--               context, handle,SPACING             spacing.sub.-- vertexSGR$INQUIRE.sub.-- USER.sub.-- DATA               context, handle, user.sub.-- dataSGR$INQUIRE.sub.-- USER.sub.-- TYPE               context, handle, user.sub.-- typeSGR$INQUIRE.sub.-- USER.sub.-- TYPE               context, handle, user.sub.-- typeSGR$INQUIRE.sub.-- VERTICES               context, handle,               first.sub.-- position,               last.sub.-- position, array.sub.-- size,               result.sub.-- count,               result.sub.-- vertex.sub.-- arraySGR$INQUIRE.sub.-- VIEWPORT               context, handle,               left.sub.-- bottom, right.sub.-- top______________________________________Node Editing SGRs-Replacement               Arguments______________________________________SGR$REPLACE.sub.-- BITMASKS               context, handle,               enable.sub.-- bits, disable.sub.-- bitsSGR$REPLACE.sub.-- CHARACTERS               context, handle, position,               delete.sub.-- count,               insert.sub.-- count,               insert.sub.-- string,               result.sub.-- handleSGR$REPLACE.sub.-- COLOR               context, handle, colorSGR$REPLACE.sub.-- DEFAULT.sub.--               context, handle, vertex.sub.-- 4dVERTEXSGR$REPLACE.sub.-- FP.sub.-- BLOCK.sub.--               context, handle,EXPONENT            fp.sub.-- block.sub.-- exponentSGR$REPLACE.sub.-- INTENSITY.sub.--               context, handle, minimum,RANGE               maximumSGR$REPLACE.sub.-- LINE.sub.-- FILTER               context, handle, filterSGR$REPLACE.sub.-- MATRIX               context, handle, flags,               matrix, normal.sub.-- matrixSGR$REPLACE.sub.-- NODE.sub.--               context, handle, onoffENABLESGR$REPLACE.sub.-- OPSPEC               context, handle,               opspec.sub.-- id, opspecSGR$REPLACE.sub.-- PICK.sub.-- ID               context, handle,               identifierSGR$REPLACE.sub.-- PLANE.sub.--               context, handle,EQUATION            plane.sub.-- equationSGR$REPLACE.sub. -- STRING.sub.--               context, handle,SPACING             spacing.sub.-- vertexSGR$REPLACE.sub.-- USER.sub.-- DATA               context, handle, user.sub.-- dataSGR$REPLACE.sub.-- USER.sub.-- TYPE               context, handle, user.sub.-- typeSGR$REPLACE.sub.-- VERTICES               context, handle, position,               delete.sub.-- count,               insert.sub.-- count,               insert.sub.-- vertices,               result.sub.-- handleSGR$REPLACE.sub.-- VIEWPORT               context, handle,               left.sub.-- bottom, right.sub.-- top______________________________________ 
    
     
                       TABLE 13______________________________________SGR Structure Memory Management RoutinesStructure MemoryManagementSGRs          Arquments______________________________________SGR$DECREMENT.sub.-- REF.sub.-- COUNT                   contex, handleSGR$INCREMENT.sub.-- REF.sub.-- COUNT                   context, handle______________________________________ 
    
     
                       TABLE 14______________________________________SGR General Purpose RoutinesGeneral Purpose SGRs            Argument______________________________________SGR$DATA         context, size, data,            handleSGR$GENERIC      context, size, data,            handleSGR$INDIRECT     context, to.sub.-- handle, handle______________________________________ 
    
     Referring now to FIG. 4, the structure memory 26 is illustrated in block diagram form. The structure memory&#39;s main function is to store the &#34;working copy&#34; of the graphics data structure built by the application programs 100 residing in the host central processing unit 10 either through the structured graphics routines or the bit map graphics package layered on the X Window System. The memory is made up of an array of memory devices 200 which are implemented as 256K CMOS DRAMS, each with a minimum memory size of one megabyte. The array of memory devices 200 is arranged for a total of four megabytes of memory. A random access taken 200 ns and a static column mode is used to achieve sequential access of 100 ns per word. 
     A structure memory bus 201 interfaces the memory devices with an II32 Bus interface 202, a structure walker interface 203 and a rendering processor interface 204 to provide data flow between the memory devices 200 and the host central processing unit 10 via the control processor 13, the rendering processor 36 and the structure walker 27, respectively. The structure walker 27 is a special purpose, 32 bit bit-slice processor programmed to traverse the three dimensional graphics data structure nodes, as described above. For a more detailed description of the structure memory 26 and structure walker 27 components of the graphics subsystem 17 reference should be made to the Shadowfax Technical Manual published by the Evans &amp; Sutherland Computer Corporation. 
     Traversal Control 
     In accordance with a significant teaching of the invention, a traversal control function is partitioned among the components of the host and graphics subsystems to accept requests for graphics structure traversals made by the several, competing application programs 100 residing in the host control processing unit 10 and to subsequently schedule and dispatch such traversal requests. 
     The traversal control functions are embodied in node control structures built in the structure memory 26 which, when traversed, provide a traversal request mechanism and handle traversal scheduling, traversal monitoring and application synchronization. The control structures function to place the graphics subsystem 17 at the disposal of all the several applications programs 100 residing in the central processing unit 10 such that each program views the graphics subsystem 17 as its own. The traversal control structures therefor coordinate traversal requests from the competing application programs 100 with the asynchronous operation of the structure walker 27 to maximize the processing capability of the graphics subsystem 17 and enable a multiple of application programs to be processed. 
     Pursuant to the invention there are three basic traversal sturctures: a system control structure (SCS), three dimensional display contexts (3DDCs) and three dimensional graphics contexts (3DGCs). The system control structure is the top-level control for the structure walker 27 and acts as the structure walker 27 operating system. The display contexts define the mapping of three dimensional images within viewports on the monitor screen defined by windows. The graphics contexts provide all the graphics attributes and control information required to perform the traversals of graphics data structures including a connection to a complementary display context. 
     The control structures are interconnected by attaching a doubly-linked list of graphics contexts created by applications to the system control structure. Each of the graphics contexts in the list contains one display context root node used to link the graphic context to a display context and one virtual root node used as a link to a graphics data structure. (See FIG. 5) Display contexts may be shared among multiple graphics contexts allowing several graphics contexts to operate within a single window. Moreover, all or part of a graphics data structure may be shared among a number of graphics contexts. 
     SYSTEM CONTROL STRUCTURE 
     The System Control Structure (SCS) serves as the executive program for the structure walker 27 in that it performs the following functions: 
     ∘ Detects and accepts requests for 3DGC traversals. 
     ∘ Schedules and dispatches all 3DGC traversals. 
     ∘ Effects updates to 3DDCs. 
     ∘ Deactivates 3DGCs and 3DDCs as requested by the traversal control function in the server 101. 
     SCS CREATION AND CONTROL 
     As a part of the DDX startup procedure, the windowing server 101 will invoke a traversal control function to allocate and generate the graphics data structure nodes required for the SCS structure and to initiate its traversal. 
     Once started, the SCS continues running (i.e., being traversed) until all traversal requests have been satisfied. Once all requests have been serviced, the SCS will suspend itself by requesting the control processor 13 to resume its traversal at the next vertical retrace event, thus preventing excessive SCS request processing. Only under the following exceptional circumstances will SCS traversal be terminated, requiring restart by the server 101: 
     (a) The server 101 detects a traversal-timeout condition. 
     (b) An SCS-detected error condition is detected. 
     (c) The server 101 has terminated SCS traversal by issuing a &#34;Server Rundown&#34; request, as part of the server rundown procedure. 
     (d) The structure walker 27 encounters an error condition, at which time it will halt after notifying the control processor 13. 
     SCS DATA BLOCK 
     In order to perform its function ,the SCS structure maintains a group of control variables in the structure memory 26 known collectively as the &#34;SCS data block&#34;. The contents of this data block are described below. 
     ∘ SCS.State 
     This longword indicates the current state of SCS execution by taking on one of the following values: 
     SGR$$K --  STATE --  INITIAL--SCS has yet to complete its initial processing. 
     SGR$$K --  STATE --  UPDATE--SCS is performing SCS update processing. 
     SGR$$K --  STATE --  IDLE--SCS has suspended itslef after finding no traversal requests pending and expects to be resumed by the control processor 13 at the next vertical retrace event. 
     SGR$$K --  STATE --  REQ --  PHASE--SCS is performing request processing. 
     SGR$$K --  STATE --  EVENT--SCS has presented an event to the control processor 13 and expects to be resumed immediately. 
     SGR$$K --  STATE --  TRAV --  PHASE--SCS is performing traversal processing. 
     SGR$$K --  STATE --  RANDOWN--SCS has processed a &#34;Server Rundown&#34; request. 
     SGR$$K --  STATE --  TRAV --  UPDATE--SCS is performing SCS-deferred updates on the client&#39;s graphics display structure. 
     SGR$$K --  STATE --  TRAV --  CXT --  SETUP--SCS is performing 3DGC-setup processing. 
     SGR$$K --  STATE --  TRAV --  CXT --  CLEANUP--SCS is performing 3DGC-cleanup processing. 
     SGR$$K --  STATE --  TRAV --  3DDC--The 3DDC structure is being traversed. 
     SGR$$K --  STATE --  TRAV --  CLIENT--The client&#39;s 100 graphics display structure is being traversed. 
     SGR$$K --  STATE --  INT --  ERROR--SCS has suspended itself after detecting an internal error. 
     The structure walker 27 requires exclusive write access to this longword. 
     ∘ SCS.Frame --  Bank 
     This is a system-wide longword flag indicating which frame buffer bank is being displayed. 
     SGR$$K --  BANK --  A--Frame Buffer Bank &#34;A&#34; is currently being displayed. 
     SGR$$K --  BANK --  B--Frame Buffer Bank &#34;B&#34; is currently being displayed. 
     The structure walker 27 requires exclusive write access to this longword. 
     ∘ SCS.WLUT --  Bank 
     This is a system-side longword flag indicating which image bank of the window look up table (WLUT) is active. 
     SGR$$K --  SIDE --  A--Window Image Bank &#34;A&#34; is currently active. 
     SGR$$K --  SIDE --  B--Window Image Bank &#34;B&#34; is currently active. 
     The structure walker 27 requires exclusive write access to this longword. 
     ∘ SCS.Perform --  Traversal 
     This longword flag is used internally by the SCS to detect the absence of traversal requests at the end of request processing. The structure walker 27 requires exclusive write access to this longword. 
     ∘ SCS.Swap --  Bank --  Request 
     This longword flag is used internally by the SCS to remember that the frame buffer bank must be swapped at the end of traversal processing. It is set by 3DDCs of frame-bank double-buffered windows. The structure walker 27 requires exclusive write access to this longword. 
     ∘ SCS.Swap --  WLUT --  Request 
     This longword flag is used internally by the SCS to remember that the window image bank of the WLUT must be swapped at the end of traversal processing. It is set by 3DDCs of WLUT-bank double-buffered windows. The structure walker 27 requires exclusive write access to this longword. 
     ∘ SCS.Server --  Rundown 
     The windowing server 101 can set this flag non-zero to cause the structure walker 27 to terminate traversal of the SCS gracefully (at the completion of traversal phase processing). The structure walker 27 will clear it as its final action before suspending SCS traversal. 
     ∘ SCS.Num --  Passes 
     This longword contains a count of the passes made through the SCS main loop. The structure walker 27 requires exclusive write access to this longword. 
     ∘ SCS.Num --  Frames 
     This longword contains a count of times SCS traversal processing has been performed. The structure walker 27 requires exclusive write access to this longword. 
     ∘ SCS.Previous --  Time 
     At the start of each request/traversal loop of the SCS, this longword is loaded with a 60 Hz, control processor 13 maintained system time value. It is used to determined the SCS.Elapsed Time. 
     ∘ SCS.Elapsed --  Time 
     This longword is used to hold the interval of 60 Hz system time which elapses between request/traversal loops of the SCS. This value is used in blink and repeated traversal scheduling algorithms. 
     ∘ SCS.Watchdog --  Timer 
     The SCS will load this longword with a maximum processing interval at certain points in its execution. The traversal control function within the server 101 will periodically decrement this timer and perform timeout processing if the timer reaches zero. 
     ∘ SCS.Event --  Pointer 
     This longword contains the virtual address of a block of data attached to an event. The structure walker 27 requires exclusive write access to this longword. 
     ∘ SCS.Queue --  Node 
     This longword contains the handle of a queue node within the SCS --  Update --  Processing substructure. 
     ∘ SCS.Pick --  Id --  Stack 
     This longword contains the handle of a system-default Pick ID Stack node. 
     ∘ SCS.Pick --  Path --  Stack 
     This longword contains the handle of a system-default Pick Path Stack node. 
     ∘ SCS.Call --  Update --  Node 
     This longword contains the virtual address of the call node in SCS update processing. This node is required by the update mechanism to perform deferred updates to the SCS. The structure walker 27 requires exclusive write access to this longword. 
     ∘ SCS.Num --  GCs 
     This longword reflects the number of 3DGCs in the 3DGC list attached to the SCS. The structure walker 27 requires exclusive write access to this longword. 
     ∘ SCS.GC --  List --  Head 
     ∘ SCS.GC --  List --  Tail 
     These longwords describe the doubly-link list of 3DGCs attached to the SCS. They are pointers which contain the structure memory addresses of 3DGC data blocks, or are both &#34;null&#34;, indicating the absence of 3DGCs. The structure walker 27 requires exclusive write access to these longwords. 
     ∘ SCS.DC --  List --  Head 
     ∘ SCS.DC --  List --  Tail 
     These longwords describe the doubly-link list of 3DDCs attached to the SCS. They are pointers which contain the structure memory 26 addresses of 3DDCs. The structure walker 27 requires exclusive write access to these longwords. 
     ∘ SCS.Current --  GC --  Pointer 
     This longword is loaded with the structure memory 26 address of the 3DGC data block currently being processed by SCS traversal processing. The structure walker 27 requires exclusive write access to this longword. 
     ∘ SCS.Current --  DC --  Pointer 
     This longword is loaded with the structure memory 26 address of the 3DDC data block attached to the 3DGC currently being processed by SCS traversal processing. The structure walker 27 requires exclusive write access to this longword. 
     ∘ SCS.Current --  Client --  Pointer 
     This longword is loaded with the structure memory 26 address of the root of the client 100 graphics data structure attached to the 3DGC currently being processed by SCS traversal processing. The structure walker 27 requires exclusive write accesss to this longword. 
     ∘ SCS.Current --  GC --  ID 
     This longword is loaded with the graphics context indentification &#34;GC ID&#34; of the 3DGC being processed by SCS traversal processing. The client processes 100 may inspect this longword to determine which of the possibly several 3DGCs has requested its traversal 
     ∘ SCS.Current --  GC --  Start --  Time 
     ∘ SCS.Current --  GC --  End --  Time 
     These longwords are loaded with the control processor 13 maintained system time at which traversal of the 3DGC commenced and completed, respectively. The structure walker 27 requires exclusive write access to these longwords. 
     ∘ SCS.Current --  Traversal --  Type 
     The contents of this longword reflect the type of traversal currently being performed. The structure walker 27 requires exclusive write access to this longword. 
     SGR$$K --  DRAW --  TRAVERSAL 
     SGR$$K --  HITTEST --  TRAVERSAL 
     SCS ORGANIZATION 
     The organization of the SCS structure is illustrated below. 
     The SCS structure alternates between request and traversal processing modes. During the request mode, each 3DGC on 3DGC list attached to the SCS will be visited in sequence. If requests for traversals are outstanding and the current state of the 3DGC permits, flags in the 3DGC data block will be updated to cause the appropriate traversals in traversal processing. In addition, draw traversals will be performed on all those 3DGCs sensitive to either the frame buffer bank or window look-up table image bank if at least one draw traversal request has been made to 3DGC of that particular class. 
     Given that at least one valid traversal request was detected in request processing, the traversal processing mode will proceed to satisfy all requests accepted. This is done by visiting each 3DGC on the 3DGC list sequentially, and there performing hit-test and draw traversals (in that order), as required. Any grouping of the two types of traversals may be performed on a 3DGC each in a given traversal pass, provided that the corresponding requests were issued. If no traversal requests are outstanding, the SCS will be held suspended until the next vertical retrace event, at which point request processing will once again be performed. This is done to avoid an unnecessary load on the structure memory 26. 
     
         ______________________________________BEGIN SCS  Define state and matrix stack overflow areas;  IF (SCS State = &#34;Initial&#34;) THEN  3D.sub.-- Graphics.sub.-- Initialization;  ENDIF  Clear SCS.Perform.sub.-- Traversal;  WHILE (NOT SCS.Server.sub.-- Rundown) DO      Set SCS.Watchdog.sub.-- Timer;      SCS.sub.-- Update.sub.-- Processing;      Request.sub.-- Processing;      Traversal.sub.-- Processing;  END DO  Clear SCS.Server.sub.-- Rundown;  SCS.State = &#34;Randown&#34;;END SCSBEGIN 3D.sub.-- Graphics.sub.-- InitializationInitialize the SCS.Frame.sub.-- Bank to Bank &#34;A&#34; [beingdisplayed]Initialize the SCS.WLUT.sub.-- Bank to Bank &#34;A&#34; [active]&#39;Clear both valid planes;Initialize.sub.-- Hierarchial State&#39;END 3D.sub.-- Graphics.sub.-- Initialization______________________________________ 
    
     When SCS traversal commences, the SCS will immediately define the state and matrix stack overflow areas, initialize some internal flags, and proceed to enter its main processing loop. 
     SCS --  Update --  Processing 
     The first part of SCS loop is SCS Update Processing. This section performs deferred updates to the SCS through the use of the Update Mechanism 
     
         ______________________________________BEGIN SCS.sub.-- Update.sub.-- Processing  SCS.State = &#34;Update.sub.-- Phase&#34;;  Perform updates to SCS via call toSCS.Call.sub.-- Update.sub.-- Node;END SCS.sub.-- Update.sub.-- Processing______________________________________ 
    
     REQUEST PROCESSING 
     The request processing portion or mode of the SCS loop performs two functions. The first function is to effect modifications to the 3DDC data blocks. To do this, request processing will examine all 3DDCs known to the system and toggle the &#34;active half&#34; of those which have swap requests pending. This processing is performed here to assure consistent 3DDC data during request and traversal processing. 
     Secondly, request processing gathers traversal requests from 3D clients 100 and the display manager (from information contained in 3DDC data blocks). This processing is performed by traversing the 3DGC structures contained in the 3DGC list. Each 3DGC, after detecting the &#34;Request Phase&#34; SCS State, will respond to all outstanding traversal requests directed towards it. Results of this request processing are retained within the 3DGC. 
     In addition, if double-buffered 3DGCs are visited (those with 3DDCs sensitive to either the frame buffer bank or window look-up table image bank), a request to swap the particular bank will be recorded. This will be used to force draw traversal of all such 3DGCs, and cause the actual swapping commands to be delivered at the end of traversal processing. 
     If no traversal requests are detected after visiting each 3DGC, the SCS will put itself to sleep. The control processor 13 (ACP) will resume SCS traversal at the next vertical retrace event. 
     
         ______________________________________BEGIN Request.sub.-- ProcessingSCS.State = &#34;Request.sub.-- Phase&#34;;Clear SCS.Swap.sub.-- Bank.sub.-- Request;Clear SCS.Swap.sub.-- WLUT.sub.-- Request;DOIncrement SCS.Num.sub.-- Passes;SCS Elapse.sub.-- Time = System VR Count SCS Previous.sub.-- Time;SCS Previous.sub.-- Time = System VR Count;Traverse.sub.-- DC.sub.-- ListTraverse.sub.-- GC-ListIF (NOT SCS.Perform.sub.-- Traversal) THENSCS.State = &#34;Idle&#34;;Request ACP to resume SCS at next VR event;Suspend traversal;SCS.State = &#34;Request.sub.-- Phase&#34;;ENDIFUNTIL (SCS.Perform.sub.-- Traversal OR SCS.Server.sub.-- Rundown)END Requst.sub.-- ProcessingBEGIN Traverse.sub.-- GC.sub.-- ListRO = SCS.GC.sub.-- List.sub.-- Head;WHILE (RO [GC handle] NOT NULL) DOSave physical addr of 3DGC data block inSCS.Current.sub.-- GC.sub.-- Ptr;Generic.sub.-- 3DGC;RO = GC.Flink;ENDDOEND Traversal.sub.-- GC.sub.-- ListBEGIN Traverse.sub.-- DC.sub.-- ListRO = SCS.DC.sub.-- List.sub.-- Head;WHILE (RO [DC handle] NOT NULL) DOIF (3DDC.System.sub.-- Enabled) THENIF (3DDC.Kill) THENClear 3DDC.Kill;Clear 3DDC.System.sub.-- Enabled;Remove.sub.-- DC.sub.-- LinksSet 3DDC.Dead;ELSEIGNORE.sub.-- ATTENTION.sub.-- INTERRUPTS:IF (3DDC.Clear.sub.-- Request) THENClear 3DDC.Clear.sub.-- request;Send 3DDC.Clear Window generic node to clearwindow;IF (3DDC.Swap.sub.-- Request) THENToggle 3DDC.Active.sub.-- Half;Clear 3DDC.Swap.sub.-- Request;ENDIFALLOW.sub.-- ATTENTION.sub.-- INTERRUPTS:IF (3DDC.Clear.sub.-- Request) THENClear 3DDC.Clear.sub.-- Request;Send 3DDC.Clear Window generic node to clearwindow;ENDIFENDIFRO = 3DDC.Flink;ENDDOEND Traverse.sub.-- DC.sub.-- ListBEGIN Remove.sub.-- DC.sub.-- LinksRO = SCS.GC.sub.-- List.sub.-- Head;WHILE (RO [GC handle] NOT NULL) DOIF (3DGC.System.sub.-- Enabled) THENIF (3DGC.DC.sub.-- Data.sub.-- Ptr = 3DDC.sub.-- being.sub.-- deleted[R1])THEN3DGC.DC.sub.-- Data.sub.-- Ptr = NULL;ENDIFENDIFRO = 3DGC.Flink;ENDDOEND Remove.sub.-- DC.sub.-- Links______________________________________ 
    
     TRAVERSAL PROCESSING 
     The traversal processing portion or mode of the SCS loop visits each 3DGC described in the 3DGC list. This action will initiate traversals depending on results of request processing and mode information contained within each 3DGC. Certain hardware-specific operations bracket the actual context traversals. In addition, one or both bank flags may be toggled as a result of window-type detection performed in the previous request processing. 
     
         ______________________________________BEGIN Traversal.sub.-- ProcessingSCS.State = &#34;Traversal Phase&#34;;IF (SCS.Perform.sub.-- Traversal) THENClear SCS.Perform.sub.-- Traversal;Perform Traversal setup actions;Traverse.sub.-- GC.sub.-- List;IF (SCS.Swap.sub.-- Bank.sub.-- Request) THENToggle SCS.Frame.sub.-- Bank;Command RP to swap banks, clear valid plane;ENDIFIF (SCS.Swap.sub.-- WLUT.sub.-- Request) THENToggle SCS.WLUT.sub.-- Bank;Command RP to swap WLUT image banks;ENDIFPerform Traversal cleanup actions;Increment SCS.Num.sub.-- Frames;END Traversal.sub.-- Processing______________________________________ 
    
     GRAPHIC CONTEXTS 
     A 3D Graphics Context (3DGC) control structure contains the graphics attributes and control information required to request and perform all types of traversals of a client 100 graphics data structure. 
     Although &#34;3DGC&#34; is referred to as a unique instance of the 3DGC structure, the traversal control maintains but a single instance of the actual control structure, known as the &#34;generic&#34; 3DGC. This structure is passed a pointer to a &#34;3DGC data block&#34; which provides the information corresponding to a particular 3DGC instance. It is these 3DGC data blocks which are maintained on the 3DGC list. 
     3DGC CREATION AND CONTROL 
     A 3DGC is created by the server 101 whenever a client 100 calls SGR$CREATE --  CONTEXT. Once the 3DGC is allocated and generated, the server 101 will place it on tail of the 3DGC list. When the server 101 detects that a client 100 has terminated, all 3DGCs owned by that client will be deactivated. The corresponding 3DGC data blocks will not be unlinked and reused until request processing has acknowledged the deactivation request. 
     The client 100 may bind a 3DDC to a 3DGC by making the following SGR call: 
     SGR$SET --  DEF --  DRAWABLE gc, window --  id, flag 
     A client may bind a client 100 graphics data structure to a 3DGC by making the following SGR call: 
     SGR$SET --  DEF --  VIRTUAL --  ROOT gc, handle 
     3DGC DATA BLOCK 
     The generic 3DGC structure is passed a pointer to the &#34;3DGC data block&#34; corresponding to the 3DGC being traversed. This data block contains control information specific to the 3DGC and is defined below. 
     ∘ 3DGC.Flink 
     ∘ 3DGC.Blink 
     These longwords contain structure memory addresses which serve as links in the doubly-linked 3DGC list. The traversal control function in the server 101 requires exclusive write access to these longwords. 
     ∘ 3DGC.System Enabled 
     This longword flag is set by the SCS when the 3DGC is added to the 3DGC list. It is cleared by the server 101 when (1) a traversal timeout occurs while this 3DGC was being traversed, or (2) a deactivation request is detected by the SCS. When this flag is set, the 3DGC is effectively removed from the system. 
     ∘ 3DGC.Kill 
     This longword flag is set by the traversal control function in the server 101 when the owning client 100 dies. It is effectively a deactivation request and is cleared by the SCS as an acknowledgement that the 3DGC is no longer active. 
     ∘ 3DGC.Dead 
     This longword flag is set by the SCS when a kill request is detected. It is used to identify those 3DGC data blocks on the 3DGC list that may be unlinked and reused by the traversal control function in the server 101. 
     ∘ 3DGC.System --  Flags 
     This longword contains bit flags used by the SCS. The structure walker 27 requires exclusive write access to this longword. 
     Do --  DC --  Draw 
     Do --  Client --  Draw 
     Do --  Hit --  Test 
     These flags serve to record traversal requests accepted by SCS request processing. 
     Bank --  2B 
     WLUT --  2B 
     These flags are set/cleared by request processing to record the type of double-buffering indicated by the attached 3DDC (if any). Traversal processing will use these flags to determine whether a draw traversal must be performed on this 3DGC even in the absence of an explicit request. 
     ∘ 3DGC.Num --  Request --  Passes 
     ∘ 3DGC.Num --  Traversal --  Passes 
     These longwords reflect the number of times this particular 3DGC has been traversed and why. The structure walker 27 requires exclusive write access to these longwords. 
     ∘ 3DGC.Num --  Timeouts 
     This longword contains a count of the number of times a timeout occurred when this 3DGC was being traversed. 
     ∘ 3DGC.Num --  Update 
     This longword contains a count of the number of times an update queue node within this 3DGC has been traversed. 
     ∘ 3DGC.Blink --  On --  Timer 
     This longword is used to determine when a &#34;blink-on&#34; traversal is to be performed. 
     ∘ 3DGC.Blink --  Off --  Timer 
     This This longword is used to determine when a &#34;blink-off&#34; traversal is to be performed. 
     ∘ 3DGC.Repeat --  Timer 
     This longword is used to determine when a &#34;repeated&#34; traversal is to be performed. 
     ∘ 3DGC.TCID 
     This longword contains the X Window System resource number of the traversal context associated with this 3DGC. 
     ∘ 3DGC.Traversal --  Type 
     This longword contains a copy of SCS.Current Traversal --  Type which is made available to the client structure to allow traversal type-specific processing. 
     ∘ 3DGC.Num --  Draw Traversals 
     ∘ 3DGC.Num --  Hit --  Test --  Traversals 
     These longwords contain counts of the number of traversals. The structure walker 27 requires exclusive write access to these longwords. 
     ∘ 3DGC.Blink State 
     This longword contains the current blink state: 
     SGR$K --  BLINK --  ON 
     SGR$K --  BLINK --  OFF 
     ∘ 3DGC.Blink --  Mask 
     This longword contains a copy of the SCS.Blink --  Mask made available to the client structure for aperiodic blink operations. 
     ∘ 3DGC.VR --  Count 
     This longword contains a copy of the 60 Hz system time. 
     ∘ 3DGC.GC ID 
     This longword contains a 3DGC identifier assigned by the server 101, which may be modified by the client 100 as required. The SCS uses the address of the 3DGC data block to distinguish 3DGCs, so this ID need not be unique. 
     ∘ 3DGC.DC --  Data --  Pointer 
     This longword contains the structure memory address of the 3DDC data block attached to this 3DGC, or zero if one is not attached. The traversal control function in the windowing server 101 requires exclusive write access to this longword. 
     ∘ 3DGC.Client --  Root 
     This longword contains the structure memory address of the client display structure attached to this 3DGC, or zero if one is not attached. The client process 100 owning the 3DGC requires exclusive write access to this longword. 
     ∘ 3DGC.Call --  Update --  Node 
     This longword contains the virtual address of a Call node which will be traversed prior to any draw traversal. This node is required by the update mechanism to perform deferred updates to the attached client structure. The structure walker 27 requires exclusive write access to this longword. 
     ∘ 3DGC.Client --  Flags 
     This longword contains traversal mode bits controlled by the client 100 through the following SGR call: 
     SGR$SET --  DEF --  TRAVERSAL --  MODE gc, modeflags 
     Automatic--When set and the attached 3DDC is a &#34;double-buffered&#34; window, the SCS is able to retraverse this 3DGC whenever the system display buffers are swapped. 
     Redisplay--When set, the display manager within the server 101 is allowed to request draw traversals of this 3DGC as required to maintain a correct image on the display. 
     Repeated--When set, draw traversals of this 3DGC will be performed at a periodic rate, as determined by 3DGC. Repeat --  Period. 
     Blink--When set, draw traversals of this 3DGC will be performed at a dual-periodic rate, as determined by 3DGC. Blink --  On --  Period and 3DGC.Blink --  Off --  Period. 
     ∘ 3DGC.Blink --  On --  Period 
     ∘ 3DGC.Blink --  Off --  Period 
     ∘ 3DGC.Repeat --  Period 
     These longwords contain time intervals which determine the periodicity of draw traversals when repeated or blink traversals mode is in effect. 
     ∘ Client --  Draw --  Request 
     This longword flag is set non-zero by the client in order to request a draw traversal via the following SGR call: 
     traversal --  type=SGR$K --  DRAW --  TRAVERSAL SGR$REQUEST --  TRAVERSAL display, gc, traversal --  type 
     The SCS will clear the flag after the request is detected. 
     ∘ Client --  Draw --  Pending 
     This longword flag is set non-zero by the SCS to indicate that a client draw request has been seen. The SCS will clear the flag after the traversal has completed. 
     Notify --  on --  Draw 
     This longword flag is set non-zero by the windowing server 101 when the client 100 requests notification of draw traversal completion. The SCS will clear the flag after the traversal is complete, just prior to passing the event to the control processor 13. 
     ∘ Draw --  Sequence Number 
     The contents of this longword are included in the notification event delivered as a result of a completed draw traversal. The traversal control function in the server 101 requires exclusive write access to this longword. 
     ∘ Client Hittest --  Request 
     ∘ Client --  Hittest --  Pending 
     ∘ Notify --  on --  Hittest 
     ∘ Hittest Sequence --  Number 
     These These longwords are used for hittest traversals in a fashion similar to the draw traversal variables mentioned above. 
     ∘ Sync --  Request 
     ∘ Sync --  Pending 
     ∘ Notify --  on --  Sync 
     ∘ Sync --  Sequence --  Number 
     These longwords are used by the server 101 in order to synchronize with the SCS. 
     3DGC ORGANIZATION 
     The 3DGC is split into request processing and traversal processing, depending upon the content of the SCS State variable. 
     The request processing requires that the 3DGC be enabled by both the system and the client 100 before any traversal request processing is performed. If this condition is met, requests for service traversals will be accepted. Then, if a &#34;visible&#34; 3DDC has been bound to the 3DGC, draw traversal requests will be accepted. If the client 100 has disabled this 3DGC and requested acknowledgement, the client 100 will be notified. 
     Traversal processing performs hit-test and draw traversals (in that order) if corresponding requests are outstanding. Acknowledging &#34;notification events&#34; will be posted if requested by the client 100. 
     Deactivation processing will be performed regardless of the SCS State. If the 3DGC is system-enabled and a &#34;kill&#34; request is pending, the 3DGC will be tagged as &#34;dead&#34; and made system-disabled. Although still linked to the 3DGC list, the 3DGC data block will then be available for unlinking and reuse. 
     
         ______________________________________BEGIN Generic.sub.- 3DGCIF (3DGC.System.sub.- Enabled) THENDO CASE (SCS.State)CASE Request.sub.- Phase:Clear 3DGC.System.sub.- FlagIF (3DGC.Kill) THENClear 3DGC.KillClear 3DGC.System Enabled;Set 3DGC.Dead;Event.sub.- Notify (opcode=SCS.sub.- EVENT.sub.- GC.sub.- DEATH,header=3DGC, num=0,reason=GC.sub.- DEATH,status=OK);SCS.State = &#34;Request Phase&#34;;ELSEIF (3DGC.Sync.sub.- Request) THENClear 3DGC.Sync.sub.- Request;IF (3DGC.Notify on.sub.- Sync) THENClear 3DGC.Notify on.sub.- Sync;Event.sub.- Notify (opcode=SCS EVENT.sub.- SYNC,header=3DGC,num=3DGC.Sync.sub.- Seq,reason=SYNC,status=OK;SCS.State = &#34;Request.sub.- Phase&#34;;ENDIFELSEUpdate.sub.- Request Processing;Hittest.sub.- Request.sub.- Processing;Draw Request.sub.- Processing;ENDIFIncrement 3DGC.Num.sub.- Request.sub.- Passes;CASE Traversal.sub.- Phase:Do.sub.- Hittest.sub.- Processing;Do.sub.- Draw.sub.- Processing;Increment 3DGC.Num.sub.- traversal.sub.- Passes;  ENDCASE ENDIFEND Generic.sub.- 3DGCBEGIN Update.sub.- Request.sub.- ProcessingDGC.Client.sub.- Update.sub.- Pending = 3DGC.Client.sub.- UpdateRequest;Clear 3DGC.Client.sub.- Update.sub.- request;SCS.State = &#34;Traversing Client Update List&#34;Traverse 3DGC.Update.sub.- List to peform deferred updates;Increment 3DGC.Num.sub.- Update;SCS.State = &#34;Request.sub.- Phase&#34;Clear 3DGC.Client Update.sub.- Pending;IF (3DGC.Notify.sub.- on.sub.- Update) THENClear 3DGC.Notify.sub.- on.sub.- Update;Event.sub.- Notify (opcode = SCS.sub.- EVENT.sub.- UPDATE,header=3DGC, num=3DGC.Update Seq,reason=UPDATE,status=OK);SCS.State = &#34;Request Phase&#34;ENDIFEND Update.sub.- Request.sub.- ProcessingBEGIN Draw.sub.- Request.sub.- ProcessingIF (3DGC.DC.sub.- Data.sub.- Ptr !=NULL) THENIF (3DGC.Visible) THENR1 = 3DDC(R0).Draw.sub.- RequestR2 = 3DDC(R0).FormatR0 = SCS.Current.sub.- GC Ptr3DGC.CLIENT.sub.- Draw.sub.- Pending = 3DGC.Client.sub.- DrawRequest;If (3DGC.Client.sub.- Draw.sub.- Pending) THENClear 3DGC.Client.sub.- Draw.sub.- Request;Set 3DGC.Do.sub.- Client.sub.- Draw;Set SCS.Perform.sub.- Traversal;ENDIFIF (3DGC.Client.sub.- Flags.Repeated)THEN CALL Repeat.sub.- Mode.sub.- Processing;ENDIFIF (3DGC.Client.sub.- Flags.Blink) THENCALL Blink.sub.- Mode.sub.- Processing;ENDIFIF (3DGC.Client.sub.- Flags.Redisplay) THENIF (3DGC.Draw.sub.- Request) THENSet 3DGC.Do.sub.- DC.sub.- Draw;Set SCS.Perform.sub.- Traversal;ENDIFENDIFIF (3DGC.Format indicates Bank 2B) THENSet 3DGC.Bank.sub.- 2B;IF (3DGC.Do.sub.- Client.sub.- Draw OR 3DGC Do..sub.- DC.sub.- Draw)THENSet SCS.Swap.sub.- Bank.sub.- Request;ENDIFELSEIF (3DDC.FormatINDICATES WLUT 2B) THENSet 3DGC.WLUT.sub.- 2B;IF (3DGC.Do.sub.- Client.sub.- Draw OR 3DGC.Do.sub.- DG.sub.- Draw)Then Set SCS.Swap.sub.- WLUT.sub.- Request;ENDIFENDIFENDIF VisibleENDIF Attached to windowEND Draw.sub.- Request.sub.- ProcessingBEGIN Repeat.sub.- Mode.sub.- ProcessingIF (3DGC.Repeat.sub.- Timer &lt;= SCS.Elapsed.sub.- Time) THENSet 3DGC.System Flags.Do.sub.- Client.sub.- Draw,Do.sub.- RepeatedSet SCS.Perform.sub.- Traversal;3DGC.Repeat.sub.- Timer = 3DGC.Repeat.sub.- Period;ELSEDecrement 3DGC.Repeat.sub.- Timer by SCS.Elapsed.sub.- Time; ENDIFEND Repeat Mode.sub.- ProcessingBEGIN Blink.sub.- Mode.sub.- ProcessingIF (3DGC.Blink.sub.- State = &#34;Off&#34;) THENIF (3DGC.Blink Off.sub.- Timer &lt;= SCS.Elapsed.sub.- Time) THENSet 3DGC.System.sub.- Flags.Do.sub.- Client.sub.- Draw,Do.sub.- BlinkSet SCS.Perform.sub.- Traversal;3DGC.Blink.sub.- State = &#34;On&#34;;3DGC.Blink Off.sub.- Timer = 3DGC.Blink.sub.- Off Period;ELSEDecrement 3DGC.Blink.sub.- Off.sub.- Timer by SCS.Elapsed Time;ELSEIF (3DGC.Blink.sub.- On Timer &lt;= SCS.Elapsed.sub.- Time) THENSet 3DGC.System.sub.- Flags.Do.sub.- Client.sub.- Draw,Do.sub.- BlinkSet SCS.Perform.sub.- Traversal;3DGC.Blink.sub.- State = &#34;Off&#34;;3DGC.Blink.sub.- On.sub.- Timer = 3DGC.Blink.sub.- On.sub.- Period;ELSEDecrement 3DGC.Blink.sub.- On.sub.- Timer by SCS.Elapsed Time;ENDIFENDIFEND Blink.sub.- Mode.sub.- ProcessingBEGIN Do.sub.- Draw.sub.- ProcessingIF (3DGC.Do.sub.- Client.sub.- Draw) THENClear 3DGC.Do.sub.- Client.sub.- Draw;SCS.Current Traversal.sub.- Type - &#34;Draw&#34;;Draw.sub.- Traversal;Clear 3DGC.Client.sub.- Draw.sub.- Pending;IF (3DGC.Notify.sub.- on.sub.- Draw) THENClear 3DGC.Notify.sub.- on.sub.- Draw;Send &#34;Begin.sub.- 3D.sub.- Context&#34; to RP to allow BM processing;Send Event.sub.- Notify (opcode=SCS.sub.- EVENT/DRAW,header-3DGC,num=3DGC.Draw.sub.- Seq,reason=DRAW,status=OK);SCS.State = &#34;Traversal.sub.- Phase&#34;ENDIFELSE IF (3DGC.Do.sub.- DC.sub.- Draw) THENClear 3DGC.Do.sub.- DC-Draw:SCS.Current.sub.- Traversal.sub.- Type = &#34;Draw&#34;;Draw.sub.- Traversal;Clear 3DDC.Draw.sub.- request;ELSE IF (SCS.Swap.sub.- Bank.sub.- Reqeuest) AND (3DGC.Bank.sub.- 2BOR (SCS.Swap.sub.- WLUT.sub.- Request) AND (3DGC.WLUT.sub.- 2B)IF (3DGC.Client.sub.- Flags.Automatic) THENSCS.Current.sub.- Traversal.sub.- Type = &#34;Draw&#34;;Draw.sub.- Traversal;ENDIFENDIFEND Do-Draw ProcessingBEGIN Draw.sub.- TraversalSCS.State = &#34;Traversing Update List&#34;Process client updates via 3DGC.Call Update.sub.- Node;Increment 3DGC.Num.sub.- Update;SCS.State = &#34;Traversing Context Setup&#34;Perform 3D Context setup actions;SCS.Current.sub.- DC.sub.- Ptr = 3DGC.DC.sub.- Data.sub.- Ptr;SCS.State = &#34;Traversing 3DDC&#34;Traverse (generic) 3DDC to set-up rendering(window) environment;(Restore R0 = (SM) address of current 3DGC);SCS.Current.sub.- Client Ptr = 3DGC.Client.sub.- Root;SCS.Current.sub.- GC.sub.- ID = 3DGC.GC.sub.- ID;3DGC.Current.sub.- Traversal Type = &#34;Draw&#34;3DGC.Blink Mask = System Blink Mask (ala ACP);3DGC.VR.sub.- Count = System VR Count (ala ACP);SCS.Current.sub.- GC.sub.- Start.sub.- Time = System VR Count (alaACP);SCS.State = &#34;Traversing Client&#34;Traverse Client Structure to draw client&#39;s image;SCS.Current.sub.- GC.sub.- End.sub.- Time = System VR Count (alaACP);Restore R0 = (SM) address of current 3DGC;SCS.State = &#34;Traversing Context Setup&#34;Perform 3D Context cleanup actions;Increment 3DGC.Draw.sub.- Count;SCS.State = &#34;Traversal Phase&#34;END Draw.sub.- TraversalBEGIN Hittest.sub.- Request.sub.- Processing3DGC.Client.sub.- Hittest Pending = 3DGC.Client HittestRequest;IF (3DGC.Client.sub.- Hittest.sub.- Pending) THENClear 3DGC.Client.sub.- Hittest.sub.- Request;Set 3DGC.Do.sub.- Hittest;Set SCS.Perform.sub.- Traversal;ENDIFEND Hittest.sub.- Request.sub.- ProcessingBEGIN Do.sub.- Hittest.sub.- ProcessingIF (3DGC.Do.sub.- Hittest) THENClear 3DGC.Do.sub.- Hittest;SCS.Current.sub.- Traversal.sub.- Type = &#34;Hittest&#34;;Hittest.sub.- Traversal;Clear 3DGC.Client.sub.- Hittest.sub.- Pending;IF (3DGC.Notify.sub.- on.sub.- Hittest) THENClear 3DGC.Notify.sub.- on.sub.- Hittest;Send &#34;Begin.sub.- 3D Context&#34; to RP to allow BMprocessing;Event.sub.- Notify (opcode=SCS.sub.- EVENT/HITTEST,header=3DGC,num=3DGC.Hittest.sub.- Seq,reason=HITTEST,status=OK);  SCS.State = &#34;Traversal.sub.- Phase&#34;ENDIFENDIFEND Do.sub.- Hittest.sub.- ProcessingBEGIN Hittest.sub.- TraversalSCS.State = &#34;Traversing Context Setup&#34;Perform 3D Context setup actions;SCS.Current.sub.- Client.sub.- Ptr = 3DGC.Client.sub.- Root;SCS.Current.sub.- GC.sub.- ID = 3DGC.GC.sub.- ID;3DGC.Current Traversal.sub.- Type = &#34;Hittest&#34;3DGC.Blink.sub.- Mask = System Blink Mask (ala ACP);3DGC.VR.sub.- Count - System VR Count (ala ACP);SCS.Current.sub.- GC.sub.- Start.sub.- Time = System VR Count (alaACP);SCS.State = &#34;Traversing Client&#34;Traverse Client Structure to hittest client&#39;s image;SCS.Current.sub.- GC.sub.- End.sub.- Time = System VR Count (alaACP);Restore R0 = (SM) address of current 3DGC;SCS.State = &#34;Traversing Context Setup&#34;Perform 3D Context cleanup actions;Increment 3DGC.Hittest Count;SCS.State = &#34;Traversal Phase&#34;END Hittest-Traversal______________________________________ 
    
     DISPLAY CONTEXTS 
     A 3D Display Context (3DDC) control structure determines the mapping of client-generated images onto a rectangular area of the screen. When called from the 3DGC, the 3DDC loads subsystem state related to the associated display manager window (the rendering enviroment). The 3DDC is passed an indication of which bank is currently being display. This is used to set up bank-sensitive attributes, such as write masks, etc. 
     The rendering environment includes: 
     ∘ Window Number 
     ∘ Window Mask 
     ∘ Foreground Color 
     ∘ Background Color 
     ∘ Base Matrix 
     ∘ Base Viewport 
     ∘ Pixel Format 
     ∘ Default Line Filter 
     ∘ Pixel Processor setting 
     ∘ Filter Rounding Enable/Disable 
     ∘ Use Valid Plane on FB Read 
     ∘ Frame Buffer Write Mask 
     ∘ Pipeline Enable Mask 
     Although a &#34;3DDC&#34; is referred to as a unique instance of the 3DDC structure, the traversal control maintains but a single instance of the actual control structure, known as the &#34;generic&#34; 3DDC. This structure is passed a pointer to a &#34;3DDC data block&#34; which provides the information corresponding to a particular 3DDC instance. 
     3DDC CREATION AND CONTROL 
     A client process 100 creates a window by making the appropriate call to the windowing system 101,102,103. As a result of this action, the Display Manager passes a description of the window (in a &#34;3DDC descriptor&#34;) to the traversal control function in the server 101. This routine will allocate a 3DDC data block and format it with information extracted from the 3DDC descriptor. If the client 100 desires to attach this window to a 3DGC (or later detach it), it will make the following SGR call. This routine, depending on the flag parameter, will either enter or remove the address of the 3DDC data block in the corresponding 3DGC data block. 
     SGR$SET --  DEF --  DRAWABLE gc, window --  id, flag 
     The display manger is able to modify the 3DDC data block in response to changes to the window attributes. A draw traversal request will be issued for all 3DGCs attached to this 3DDC if the 3DDC retains visibility after modification. 
     3DDC DATA BLOCK 
     ∘ 3DDC.Flink 
     ∘ 3DDC.Blink 
     These longwords contain structure memory 26 addreses which serve as links in the doubly-linked 3DDC list. The structure walker 27 requires exclusive write access to these longwords. 
     ∘ 3DDC.System --  Enabled 
     This longword flag is set by the SCS when the 3DDC is added to the 3DDC list. It is cleared by the SCS as a result of a deactivation request. 
     ∘ 3DDC.Kill 
     This longword flag is set by the traversal control function in the server 101 when the owning client 100 dies. It is effectively a deactivation request and is cleared by the SCS request processing as an acknowledgement that the 3DDC is no longer active. 
     ∘ 3DDC.Dead 
     This longword flag is set by the SCS when a kill request is detected. It is used to identify those 3DDC data blocks on the 3DDC list that may be unlinked and reused by the traversal control function in the server 101. 
     ∘ 3DDC.Swap --  Request 
     This longword is used to synchronize structure walker 27 and server 101 access to the 3DDC data block. When the traversal control function in the server 101 finds this flag clear, it is immediately allowed access to the &#34;inactive&#34; half of 3DDC data block. At this point it can update the inactive half and set this longword non-zero. When the SCS finds this flag set, it will swap active and inactive halves and clear this flag. 
     If the traversal control function in the server 101 finds this flag set (indicating the SCS has yet to see a previous swap request), it has two options; 
     (a) It can wait until the SCS clears this flag. This will assure that the previously updated half is seen at least once. 
     (b) It can clear the flag itself, wait a short period of time, and then update the &#34;inactive&#34; half at that point. Note, however, that the previous swap request will most likely be ignored. The wait is required in case the SCS is currently processing the previous request. (Attention interrupts will be disabled by the SCS during this period (for 3 nodes), so this critical region is well bounded). 
     ∘ 3DDC.Active --  Half 
     This longword indicates which of the &#34;halves&#34; of this 3DDC data block is currently being used by SCS request and traversal processing. If zero, the first half is active, otherwise the second half is active. 
     The 3DDC data block contains consecutive copies (halves) of the following group of items. 
     ∘ 3DDC.Visible 
     When this longword flag is non-zero, the window represented is (at least partially) visible on the screen. If zero, the window is either totally obscured or iconized, in which case draw traversals are not attempted. 
     ∘ 3DDC.Draw --  Request 
     This longword flag is set non-zero at the behest of data manager in order to request draw traversals for all 3DGCs bound to this 3DDC. This action may be required, for example, when a window incurs an exposure event or resize operation. The SCS will clear this flag following the first draw traversal of a 3DGC bound to this 3DDC. 
     ∘ 3DDC.Window --  Number 
     This longword contains the window number, in a format suitable for entry into a Generic node. 
     ∘ 3DDC.Window --  Mask 
     This longword contains the window mask, in a format suitable for entry into a Generic node. 
     ∘ 3DDC.Pixel --  Format 
     This longword contains the pixel format of this window. 
     1B, 4 bit Mapped 
     1B, 4 bit Gray Scale 
     1B, 8 bit Mapped 
     1B, 8 bit Gray Scale 
     1B, 12 bit RGB 
     1B, 24 bit RGB 
     WLUT 2B, 4 bit Mapped 
     WLUT 2B, 4 bit Gray Scale 
     WLUT 2B, 8 bit Mapped 
     WLUT 2B, 8 bit Gray Scale 
     WLUT 2B, 12 bit RGB 
     Bank 2B, 4 bit Mapped 
     Bank 2B, 4 bit Gray Scale 
     Bank 2B, 8 bit Mapped 
     Bank 2B, 8 bit Gray Scale 
     Bank 2B, 12 bit RGB 
     Bank 2B, 24 bit RGB 
     ∘ 3DDC.Background --  Color 
     This longword contains the window background color in a format suitable for entry into a Set Background node. 
     ∘ 3DDC.Foreground --  Color 
     This longword contains the virtual address of the Base Matrix X3 node which is traversed to load the base matrix. 
     ∘ 3DDC.Base --  Matrix --  SGR 
     This longword contains the virtual address of the Base Matrix X3 node which is traversed to load the base matrix. 
     ∘ 3DDC.Base --  Matrix --  GDS 
     This longword contains the physical address of the Base Matrix graphics display structure node which is traversed to load the base matrix. 
     ∘ 3DDC.Base --  Viewport --  SGR 
     This longword contains the virtual address of the Base Viewport X3 node which is traversed to load the base viewport. 
     ∘ 3DDC.Base --  Viewport --  GDS 
     This longword contains the physical address of the Base Viewport graphics data structure node which is traversed to load the base viewport. 
     3DDC ORGANIZATION 
     
         ______________________________________BEGIN Generic.sub.-- 3DDC;Use 3DDC.Active.sub.-- Half to setup indirect addressing;Load Base Matrix;Load Base Normal Matrix;Load Base Viewport;Load Window Number;Load Window Mask;Load Foreground (Line) Color;Load Background Color;Format.sub.-- Dependent.sub.-- Setup;Clear 3DDC.Draw.sub.-- Request;END Generic.sub.-- 3DDC;BEGIN Format Dependent SetupIF (DDC.Format.Buffering = &#34;WLUT.sub.-- Bank.sub.-- DoubleBuffered&#34;)IF (SCS.WLUT.sub.-- Bank = &#34;A&#34;) THEN Plane Mask = 3DDC.Plane Mast.sub.-- B;ELSEPlane Mask = 3DDC.Plane.sub.-- Mask.sub.-- A;ENDIFClear (input-side) window to the background colorELSEPlane Mask = 3DDC.Plane.sub.-- Mask.sub.-- A;ENDITIF (3DDC.Format.Buffering = &#34;Frame.sub.-- Bank.sub.--Double.sub.-- Buffered&#34;)THENIF (SCS.Frame Bank = &#34;A&#34;) THEN (A being displayed)Source Bank = &#34;B&#34;;Destination Bank = &#34;B only;Enable valid plane when reading pixels;ELSESource Bank = &#34;A&#34;;Destination Bank = &#34;A only&#34;;Enable valid plane when reading pixels;ENDIFELSE (&#34;Single Buffered&#34;, &#34;WLUT.sub.-- Bank.sub.-- Double.sub.-- Buffered&#34;)Source Bank = &#34;A&#34;;Destination Bank = &#34;A and B&#34;;Disable valid plane when reading pixels;ENDIFIF (3DDC.Format.Class = &#34;Mapped&#34;) THENLoad Pixel Proc ALU mode = &#34;Store&#34;;Disable rounding in PPA;Disable additive blending on line crossings;ELSE (&#34;RGB&#34;, &#34;GrayScale&#34;)Load Pixel Proc ALU mode = &#34;Add with Ceiling&#34;;Enable rounding in PPA;Enable additive blending on line crossings;ENDIFCASE 3DDC.Format.Depth&#34;4 bits&#34;:Enable 4-bit ALU mode;&#34;8 bits&#34;:Disable 4-bit ALU mode;&#34;12 bits&#34;:Enable 4-bit ALU mode;&#34;24 bits&#34;:Disable 4-bit ALU mode;ENDCASEEND Format.sub.-- Dependent.sub.-- Setup______________________________________ 
    
     The following is a summary of the various routines at the disposal of the clients 100 and server 101 to enable them to interface with the traversal control structures. 
     SGR$CREATE --  CONTEXT display, gc 
     display 
     This is the X Window System display variable which specifies a particular connection to a server 101. 
     This is the identifier of the 3DGC created. 
     A client process 100 will call this rountine to create a graphics context (3DGC). 
     SGR$SET --  DEF --  DRAWABLE gc, window --  id, flag 
     gc 
     This is the &#34;3DGC ID&#34; of the 3DGC to be attached. 
     window --  id 
     This longword contains an identification of the window which is to be attached to, or detached from, the 3DGC. 
     flag 
     If this longword is set non-zero, the window will be attached. If it is zero, the window will be detached. 
     A client process 100 will call this routine to attach or detach a window (3DDC) to or from a graphics context (3DGC). 
     SGR$SET --  DEF --  VIRTUAL --  ROOT gc, handle 
     gc 
     This is the &#34;3DGC ID&#34; of the 3DGC to be attached. 
     handle 
     This longword contains the virtual address of the node which is to be entered as the root node of the 3DGC&#39;s client structure. 
     A client process 100 will call this routine to attach a graphic data structure (client structure) to a graphics context (3DGC). 
     SGR$SET --  DEF --  TRAVERSAL --  MODE gc, modeflags 
     gc 
     This is the &#34;3DGC ID&#34; of the 3DGC to receive new traversal modes. 
     modeflags 
     This longword specifies the traversal modes as described with respect to the 3DGC. Client --  Flages on p. 69. 
     A client process 100 will call this routine to set-up the appropriate traversals modes of a 3DGC. These modes affect subsequent traversals of the 3DGC. 
     SGR$REQUEST --  TRAVERSAL gc, traversal --  type 
     gc 
     This is the 3DGC to be traversed. 
     traversal --  type 
     This specifies the type of traversal desired: 
     * SGR$K --  DRAW --  TRAVERSAL--for a draw traversal 
     * SGR$K --  HITTEST --  TRAVERSAL--for a hit-test traversal 
     A client process 100 will call this routine to request that a particular type of traversal be performed on the 3DGC. 
     SGR$INQ --  TRAVERSAL --  STATE gc, traversal --  type, waitflag, state 
     gc 
     This is the 3DGC in question. 
     traversal --  type 
     This longword is used to specify the type of traversal in question. 
     * SGR$K --  DRAW --  TRAVERSAL--for draw traversal completion 
     * SGR$K --  HITTEST --  TRAVERSAL--for a hit-test traversal completion 
     waitflag 
     If this longword flag is non-zero, this routine will not return until the specified event has occurred. Otherwise the status of the event is returned immediately. 
     A client process 100 will call this routine in order to obtain status or notification of a particular traversal completion. 
     SGR$STARTUP 
     The server 101 will call this routine to initialize the traversal control function operating in the server process 101. This action includes the creation of all control structures and the commencement of SCS traversal. 
     SGR$CREATE --  3DGC gc, 3dgc --  db 
     gc 
     This is the identifier of the 3DGC to be created. 
     3dgc --  db 
     The virtual address of the 3DGC data block associated with the new 3DGC is returned in this longword. 
     The server 101 will call this routine to create a new 3DGC structure in response to a client 100 invoking SGR$CREATE --  CONTEXT. 
     SGR$CREATE --  3DDC --  descriptor, 3ddc --  db 3ddc --  descriptor 
     A structure of longwords, passed by reference, which contains an initial description of the window. 
     3ddc --  db 
     The virtual address of the 3DDC data block created, returned by reference. 
     The server 101 will call this routine to create the 3DDC structure to be associated with a newly-defined window. The address of the 3DDC data block returned can subsequently be used to link this window to any number of 3DGCs. 
     SGR$UPDATE --  3DDC 3ddc --  descriptor, 3ddc --  db 
     3ddc --  descriptor 
     A structure of longwords, passed by reference, which contains an updated description of the window. 
     3ddc --  cb 
     The virtual address of the 3DDC data block to be updated, passed by reference. 
     The server 101 will call this routine to update the 3DDC structure associated with a newly redifined/modified window. This routine may request a draw traversal of all 3DGCs attached to this window, given that the window is visible and the 3DGCs are properly enabled. 
     SGR$RUNDOWN 
     The server 101 will call this routine to gracefully terminate traversal of the SCS. 
     From the above description of the traversal control functions it should be understood that the three dimensional graphics contexts (3DGC&#39;s) tie all of the traversal control functions together. The structure walker 27 traversal of each 3DGC through the request processing and traversal processing modes of the SCS provides the structure walker 27 with the graphics attributes and control information necessary to perform all traversals of a graphics data structure. As illustrated in FIG. 5. Each client 100 is provided with calls and routines to attach a graphics data structure (GDS) to a 3DGC through a 3D virtual root and to control traversal request flags in the attached 3DGC. The client 100 may also make a call to bind a 3DGC to the 3DDC created by the display manager to merge a three dimensional functionality into the X Window system. In this manner, the asynchronous traversal of the structure memory 26 is controlled by means of the traversal request mechanism available to the multiple clients 100 and through the request and traversal processing modes to systematically create a node traversal sequence for ordered flow of graphics data and commands to the graphics pipeline processor 29 through the line 30. The ordered flow of graphics data and commands assures maximum efficiency in the utilization of the resources of the graphics subsystem 17 to efficiently process a multiple of application programs by organizing traversal requests and related graphics data structures and window information through the 3DGCs and connected 3DDCs for the continuing asynchronous, traversal operation of the structure walker 27. 
     RENDERING PROCESSOR CONTROL AND BITMAPS GRAPHICS INTERFACE 
     The graphics subsystem 17 of the invention provides two types of graphics environments to the user: 3-D graphics, as described above, and bitmap (2-D) graphics. The bitmap environment is similar to its 3-D environment, though somewhat simpler. As with 3-D, a bitmap application communicates with the graphics subsystem 17 through the use of data structures stored in shared memory (structure memory 26). These data structures, the bitmap graphical data structures, are traversed and processed by the rendering processor 36. 
     The rendering processor 36 performs multiple tasks in the system: 3-D rendition, bitmap rendition, bitmap graphical data structure traversal, and video subsystem control. The term &#34;rendition&#34; in computer graphics refers to techniques used such as coloring, shading and lighting to realistically draw an object. The rendering processor 36 also regulates the scheduling of Bitmap and 3-D graphical operations. In addition to traversal and rendition, the rendering processor 36 also provides an interface for video subsystem (Color Lookup Table, Window Lookup Table, and Cursor Management). 
     The rendering processor 36 is a shared resource in the context of bitmap graphics. The graphics provides two levels of interface. The first interface provides primitive access to hardware/microcode facilities with little added abstraction. The second interface is a model level interface that provides the functionality and semantics expected by the standard Digital windowing systems (X or UIS). The interface between the rendering processor 36 and the rest of the graphics system was designed to optimize the sharing of the rendering processor 36 among bitmap graphics and 3-D graphics applications. 
     GRAPHICS CONTEXT 
     The rendering processor 36 and drawing hardware maintains state that is used or modified when graphics commands are executed. The total of all such state comprises a context in which drawing commands are executed. This context, the hardware context, is managed solely through the use of commands executed by the rendering processor 36. 
     A multitasking graphics environment is obtained by sharing the one hardware context among multiple graphics context. A graphics context represents a thread of execution and the state needed for the execution of commands in that thread. Multitasking is done much the same way that multiple process contexts share a hardware context in a timesharing system: scheduling and execution. Graphics contexts are traversed by the rendering processor and those marked are scheduled for execution. 
     In addition to multitasking, each graphics context provides state and a mechanism to dynamically load that state into the graphics hardware at any time during the execution of graphics commands. In this way, the thread of execution is decoupled from the state needed for execution. 
     Execution of a graphics context occurs in two phases: loading phase and update phase. During the loading phase the hardware context is brought to a state consistent with the graphics context being loaded. The loading phase for a bitmap graphics context typically sets up drawing state in the hardware context, but rarely performs drawing. The loading phase for a 3-D graphics context typically sets up state in the hardware context, but also draws an image containing a view of a world. 
     During the update phase, commands are consumed that change the description of a world. The description of a bitmap world is contained in a bitmap data structure so that an update to the description requires editing a bitmap (rasterization). 
     The description of a 3-D world is contained in a more complex data structure. This data structure is usually traversed during the loading phase so that an update to the description requires editing part of that data structure. In both the 3-D and bitmap case a data structure is edited with the only difference being in the data types and operations used. 
     The rendering processor 36 loads a bitmap graphics context by executing a list of commands that update the hardware context; this list is referred to as the initialization list. The initialization list is used to obtain consistency of the hardware context before any drawing commands are executed. Each time a graphics context is loaded all the commands in the initialization list are executed, though not consumed. The initialization list is modified either by direct memory access from the host and control processors, or through commands executed by the rendering processor 36. Thus, the client determines the kind and amount of state required for a bitmap graphics context through the use of its initialization list. 
     A bitmap graphics context presents a processing environment similar to that of general purpose load/store architecture. In this environment each graphics context has a current set of general purpose registers--32 registers in all. The content of the general purpose registers are guaranteed to be consistent throughout the lifetime of the graphics context. In comparison, the hardware context is not guaranteed to remain consistent between one execution of a graphics context and another and as a result the hardware context must be made consistent when a graphics context is loaded. 
     Normally, a register is used by the rendering processor 36 as explicitly instructed by a command. The rendering processor 36 does, however, require access to some data while it loads and executes a graphics context. This data is implicitly accessed during the execution of a graphics context and is statically assigned to certain registers. The initialization list pointer is an example of data that the rendering processor 36 uses while loading a graphics context and the rendering processor 36 can assume that it will find this pointer in register 2, though register 2 is a general purpose register in all other respects. 
     TRAVERSAL 
     Graphics contexts are stored in data structures that are traversed by the structure walker for 3-D and the rendering processor 36 for bitmap. This implies that the rendering processor 36 plays two roles: raster engine and bitmap graphical data structure traverser. All bitmap graphics context data structures are linked to a bitmap data structure root (bitmap root) and all 3-D graphics context data structures are linked to a 3-D data structure root (3-D root). Pointers to both the bitmap and 3-D roots reside in reserved structure memory 26. 
     Traversal is the term used for the way a class of graphics contexts are selected for execution. A list of graphics contexts is traversed by stepping through the list and visiting each context in a serial fashion. During each visit, it is determined whether or not a graphics context requires execution and if so the context is loaded and executed. 
     There may be up to three traversals in progress at any given time: low priority 3-D traversal, low priority bitmap traversal, and high priority bitmap traversal, though only one of the three may be executing at any given time. A traversal is either inactive, active, or suspended. A traversal is initially inactive and is activated through use of a signal mechanism. When activated, the first graphics context in the list is visited. A traversal may be suspended when another traversal needs to be activated or resumed. When a suspended traversal is resumed the current graphics context in that traversal is visited. A traversal becomes inactive after all graphics contexts have been visited and no signals to that traversal are pending. 
     When a graphics context is visited, two bits, local to the graphics context, are used to determine if the graphics context requires execution. The first bit indicates that the graphics context requires execution at low priority. The second bit indicates that the graphics context requires execution at high priority. The traverser checks and clears (interlocked) the appropriate bit(s) as the first step of a visit. These bits are located in the two low order bits of register 1 in a graphics context. Refer to FIG. 8 which illustrates graphics context and traversal model. 
     A bitmap traversal is signaled to activate through the use of two bits (low priority run bit and high priority run bit) in the bitmap root and through the use of the rendering processor 36 control status register (CSR). It is through the CSR that the host controls the rendering processor 36. To activate a low priority bitmap traversal the low priority run bit is set. This bit is checked and cleared (interlocked) by the rendering processor 36 on a time basis or in response to CSR attention. Signaling for a high priority traversal is done much the same way, though using the high priority run bit in the bitmap root. 
     A transaction is a series of commands that comprise an operation or program. Commands in a transaction execute synchronously with respect to one another, but may execute asynchronously with commands in other transactions. Multiple transactions execute synchronously within a graphics context, or asynchronously in multiple graphics contexts. A transaction may be terminated explicitly by using the end-transaction command. A bitmap transaction is terminated implicitly when the command queue is exhausted. 
     A transaction may lock the rendering processor 36 for some period of time, normally to maintain some sort of data consistency. This is accomplished through use of lock and unlocked commands. While the rendering processor 36 is locked the current traversal may not be suspended and the current graphics context continues to execute until an unlock command is encountered. 
     The rendering processor 36 alternates between executing commands from bitmap graphics contexts and executing commands from 3-D graphics contexts. 3-D commands are taken from the geometry pipeline. In general, low priority 3-D and low priority Bitmap graphics contexts are equal in priority. The following rules are used to establish a scheduling policy that insures fairness between 3-D and bitmap graphics execution. 
     A bitmap traversal becomes pending whenever either of the run bits in the bitmap root is set. 
     A pending high priority bitmap traversal is initiated as soon as possible: any time during a 3-D transaction or between any two low priority bitmap transactions. 
     A high priority bitmap traversal traverses all the bitmap graphics contexts from first to last without interruption. 
     A pending low priority bitmap traversal is initiated after a 3-D end-of-frame command is received or immediately after the current 3-D transaction terminates following a VSYNC. 
     A low priority bitmap traversal traverses all the bitmap graphics contexts from first to last, but may be suspended and resumed multiple times. Traversal is suspended and returned to the pending state following VSYNC. During this suspension, execution of pending 3-D transactions is initiated. 
     A bitmap graphics context becomes pending when either its low or high run bits is set. 
     A pending high priority bitmap graphics context is executed whenever it is traversed. 
     A pending low priority bitmap graphics context is executed only when traversed at low priority. 
     If the number of commands executed in a single visit to a graphics context exceeds a limit specified in the bitmap root, the graphics context is suspended and made pending (rescheduled). Traversal then proceeds to the next graphics context. 
     Execution of a bitmap graphics context is terminated when the command queue is exhausted. 
     If the rendering processor 36 is locked by a graphics context all scheduling is deferred until an unlock command is encountered. If the command queue is exhausted, the rendering processor 36 continues to retry the command queue until an unlock command is encountered. On every retry, the rendering processor 36 waits 5 us to avoid bus deadlock. 
     The following is an example of a scheduling algorithm used by the rendering processor 36. This algorithm implements the scheduling policy set out above. 
     
         ______________________________________rp.sub.-- idle.sub.-- loop( )BEGIN..IF (rp.sub.-- attention)BEGINIF (TestAndClear(resmem.bmroot.status.hi))do.sub.-- hi.sub.-- bm.sub.-- traversal( )ENDIF ((rp.sub.-- attention) OR (vsync.sub.-- occured)) AND (NOT3d.sub.-- transaction)BEGINIF (TestAndClear(resmem.bmroot.status.hi))do.sub.-- hi.sub.-- bm.sub.-- traversal( )IF (TestAndClear(resmem.bmroot.status.lo))do.sub.-- low.sub.-- bm.sub.-- traversal( )END...ENDdo.sub.-- hi.sub.-- bm.sub.-- traversal( )BEGINFORALL gc IN resmem.bmroot.gclist IF (TestAndClear(gc.status.hi)) BEGIN load.sub.-- base.sub.-- register(gc) FORALL cmd IN gc.iniq execute.sub.-- command(gc,cmd) FORALL cmd IN gc.exeq consume.sub.-- command(gc,cmd)END ENDdo.sub.-- low.sub.-- bm.sub.-- traversal( )BEGINstarting.sub.-- gc = resmem.bmroot.gclist.current;FOREVERBEGINgc = resmem.bmroot.gclist.current;IF (resmem.bmroot.gclist.current.next EQL nil)resmem.bmroot.gclist.current =resmem.bmroot.gclist.first;ELSEresmem.bmroot.gclist.current =resmem.bmroot.gclist.current.next;IF (TestAndClear(gc.status.lo))BEGINload.sub.-- base.sub.-- register(gc)FORALL cmd IN gc.iniqexecute.sub.-- command(gc,cmd)FORALL cmd IN gc.exeqBEGIN  IF (TestAndClear(resmem.bmroot.  status.hi))   do.sub.-- hi.sub.-- bm.sub.-- traversal( )   consume.sub.-- command(gc,cmd)IF ((vsynch.sub.-- occured) OR  (reschedule.sub.-- requested) OR (command.sub.--  count &gt; resmem.bmroot.command.sub.-- limit))  AND (NOT rp.sub.-- locked) break;ENDEND IF ((NOT resmem.bmroot.status) AND (starting.sub.-- gc EQL resmem.bmroot.gclist.current)) OR (vsynch.sub.-- occured) break;ENDEND______________________________________ 
    
     Rescheduling defers the execution of commands in a graphics context until the next traversal. A reschecule requires that both the graphics context run bit and the global run bit be set. After setting these bits traversal proceeds on to the next graphics context. 
     The rendering processor 36 will maintain a traversal count in the bitmap root. The traversal count is incremented whenever a low priority bitmap traversal is completed. Clients can use this count to determine whether a low priority bitmap traversal has taken place or not. It cannot be used as a guarantee that the rendering processor 36 has serviced a given graphics context, but it can be used to guarantee that the rendering processor 36 is not currently accessing a structure that has been unlinked from access. Thus, a client could use the traversal count to date unlinked packets for future garbage collection. 
     FIG. 9 illustrates the bitmap root data structure. (Note that traversal is assumed to be in the inactive state.) Listed below are descriptions of the contents of the data structures. 
     
         ______________________________________Status - 32 bit field that contains bits usedfor bitmap traversal. The table below containsdefinitions for bits in this field.Bit        Description0          Low Priority Run Bit1          High Priority Run Bit2-31       Reserved and zeroedCurrent - a pointer to the previously executed lowpriority bitmap graphics context. When lowpriority bitmap traversal is inactive it points to First.First - a pointer to the first bitmap graphics context.Last - a pointer to the last bitmap graphics context.Command-Limit - an unsigned integer which specifiesthe maximum number of commands that may be executedin a graphics context during any given scheduling cycle.Count - an unsigned integer count of the low prioritybitmap traversals that have taken place.______________________________________ 
    
     The bitmap graphics context is a data structure. FIG. 10 illustrates the bitmap graphics context data structure. (Note that none of the commands in the command queue depicted have been executed.) 
     
         ______________________________________Next - A pointer to the next bitmap graphics context.Status - A bit field that contains bits used for bitmaptraversal. The table below contains definitions foreach of the bits in this field.Bit       Description0         Low Priority Run Bit1         High Priority Run Bit2-31      reserved - and zeroedInit - A pointer to a list of commands that make up theinitialization list.Current - A pointer to the previously executed bitmapgraphics command. When low priority bitmap traversalis inactive it points to First.First - A pointer to the first bitmap graphics command.Last - A pointer to the last bitmap graphics command.Base register is a pointer to 32 general purpose registers.______________________________________ 
    
     Bitmap data format pertains to how bitmap data is organized in memory. There are multiple ways that a bitmap may be organized in memory. The rendering processor 36 microcode manages four formats: 
     Cell Array 
     Planar 
     Unpacked Byte 
     Unpacked Longword 
     In cell array format a 2×4×4 array of pixel data is contained in a longword: 2 bits from 16 pixels, 4 rows of 4 pixels. Adjacent longwords contain cells adjacent in the X dimension. FIG. 11 illustrates how bits in a cell correspond to bits in a longword. 
     The following describes the convention used to describe bit storage: 
     
         ______________________________________  Longword      32    bits  Word          16    bits  byte          8     bits______________________________________ 
    
     Planar format is most commonly used in existing DEC workstations. In planar format one bit from 32 pixels (the same bit in each pixel) is stored in a longword. Bits 0-31 are from adjacent pixels that run from left to right in the bitmap. Bits from consecutive pixels on a scanline (left to right) are contained in consecutive longwords of memory. The memory used to store a scanline of pixels is longword padded. Adjacent planes of scanlines are stored in adjacent memory regions. This deviates from the standard planar bitmap; data in scanlines are normally word padded. When data is copied from system memory to structure memory or from structure memory to system memory the host must compensate for this difference. Structure memory is byte addressable from the host, but only longword addressable by the rendering processor 36. 
     In unpacked byte format a bitmap contains pixels that are 8 or fewer bits deep and each pixel is contained, aligned to bit zero, in a byte of memory; a byte contains exactly one pixel. Consecutive pixels on a scanline (left to right) are contained in consecutive bytes of memory. The memory used to store a scanline of pixels is longword padded. 
     In unpacked longword format, a bitmap contains pixels that are 32 or fewer bits deep and each pixel is contained, aligned to bit zero, in a longword of memory; a longword contains exactly one pixel. Consecutive pixels on a scanline (left to right) are contained in consecutive longwords of memory. 
     A pitch is a value that specifies the relative memory location of data for pixels that are geometrically adjacent. Pixel data may be adjacent in X, Y, or Z. Pixel data adjacent in X is stored in adjacent memory locations, but pixel data adjacent in the other dimensions are in remote memory locations by the amount specified by either the Y-pitch or Z-pitch. Pitch values may be calculated from bitmap dimensions and format. Pitch values are normally an artifact in the implementation of a particular command. For the system of invention, a pitch is often calculated by host software and used by the rendering processor 36 to execute a lower level command. This frees the rendering processor 36 from having knowledge of complicated bitmap data structures. 
     In all bitmap formats, except cell array, the Y-pitch specifies how to move from one scanline to the next. In planar format the Z-pitch specifies how to move from one plane to the next. For cell array format the Y-pitch specifies how to move from one scanline of cells (four scan lines of the bitmap) to the next and the Z-pitch specifies how to move from one plane of cells (two planes of the bitmap)to the next. 
     A display context defines how a rectangular region, display region, is projected upon one or more bitmaps. Each time a display region appears in a bitmap is considered to be a display instance. A display instance specifies the bitmap in which the display region appears, the offset of the display region in the bitmap, how the display region is clipped (rectangles and/or window planes), and what pixel format is used. The display context data structure is illustrated in FIG. 12 and described below. 
     
         ______________________________________Destination Data StructureINSTANCES - a longword that contains the address of thedisplay instance list. A value of 0 (Null value) implies thatthe display context does not currently appear in any bitmap.WIDTH - a word that contains the width of the display region.HEIGHT - a word that contains the height of the display region.Destination Instance Data StructureNEXT - a longword that contains the address of the next displayinstance. An address of 0 (Null value) indicates the end of thedisplay instance list.BITMAP - a longword that contains the address of a bitmapdescriptor. A zero value implies the frame buffer bitmap and isthe only value the rendering processor 36 will accept. If a non-zero value is detected the rendering processor 36 ignores thedestination instance.XOFF - a word that contains the x offset of the display regionfrom the origin of the bitmap.YOFF - a word that contains the y offset of the display regionfrom the origin of the bitmap.BANK - a bit field that specifies what frame buffer banks thedisplay instance is displayed in.Bit     Description0       Bank A enable1       Bank B enable2-15    reserved and zeroedZE - an unsigned word that contains the pixel extent of the displaypixel. Currently, this value is restricted to be a multiple of 4 or 8.ZO - a signed word that contains the pixel offset of the displaypixel in the bitmap pixel. Currently, this value is restricted to bea multiple of 4 for displays with extents of 4 and a multiple of 8for display of extents of 8.ZF - an unsigned word that contains the display pixel format.Currently, a value of 0 specifies mapped color format and a valueof 1 specifies full color format.PMSK - a longword that contains a bit field used to mask displaypixel data as it&#39;s written.WV - an unsigned word that contains the hardware windownumber used to mask drawing operations.WM - an unsigned word that contains the hardware windowmask that indicates what bits in the window number are used.RCOUNT - a word that contains the number of clippingrectangles in the display instance.RECTS - an array of rectangle data structures, as defined below,that are used to clip drawing operations for this display instance.Each rectangle is relative to the origin of the display region. Arectangle specifies where drawing is to be performed. An emptyrectangle list specifies that no drawing is to be performed.Rectangle Data StructureX - a word that specifies the x offset of the upper left cornerof a clipping rectangle.Y - a word that specifies the y offset of the upper left cornerof a clipping rectangle.W - a word that specifies the width of a clipping retangle.H - a word that specifies the height of a clipping rectangle.______________________________________ 
    
     The above described preferred embodiment of the invention is meant to be representative only, as certain changes may be made therein without departing from the clear teachings of the invention. Accordingly, reference should be made to the following claims which alone define the invention.