Use markdown style lists
This commit is contained in:
parent
2091516544
commit
307b59584f
17 changed files with 120 additions and 120 deletions
28
40-02.md
28
40-02.md
|
|
@ -41,25 +41,25 @@ Y coordinates, error terms and error term adjustments, lengths, and
|
|||
directions of X movement for each edge. Once the GET is built, we'll do
|
||||
the following:
|
||||
|
||||
**1.** Set the current Y coordinate to the Y coordinate of the first
|
||||
edge in the GET.
|
||||
1. Set the current Y coordinate to the Y coordinate of the first
|
||||
edge in the GET.
|
||||
|
||||
**2.** Move all edges with the current Y coordinate from the GET to the
|
||||
AET, removing them from the GET and maintaining the X-sorted order of
|
||||
the AET.
|
||||
2. Move all edges with the current Y coordinate from the GET to the
|
||||
AET, removing them from the GET and maintaining the X-sorted order of
|
||||
the AET.
|
||||
|
||||
**3.** Draw all odd-to-even spans in the AET at the current Y
|
||||
coordinate.
|
||||
3. Draw all odd-to-even spans in the AET at the current Y
|
||||
coordinate.
|
||||
|
||||
**4.** Count down the lengths of all edges in the AET, removing any
|
||||
edges that are done, and advancing the X coordinates of all remaining
|
||||
edges in the AET by one scan line.
|
||||
4. Count down the lengths of all edges in the AET, removing any
|
||||
edges that are done, and advancing the X coordinates of all remaining
|
||||
edges in the AET by one scan line.
|
||||
|
||||
**5.** Sort the AET in order of ascending X coordinate.
|
||||
5. Sort the AET in order of ascending X coordinate.
|
||||
|
||||
**6.** Advance the current Y coordinate by one scan line.
|
||||
|
||||
**7.** If either the AET or GET isn't empty, go to step 2.
|
||||
6. Advance the current Y coordinate by one scan line.
|
||||
|
||||
7. If either the AET or GET isn't empty, go to step 2.
|
||||
|
||||
\
|
||||
**Figure 40.3** *The global and active edge tables as linked lists.*
|
||||
|
|
|
|||
Loading…
Reference in a new issue