Convert figure images to markdown
This commit is contained in:
parent
307b59584f
commit
77a95ec319
115 changed files with 218 additions and 403 deletions
10
66-03.md
10
66-03.md
|
|
@ -52,9 +52,8 @@ polygons, and that cuts the work involved in sorting, clipping, and
|
|||
rasterizing edges nearly in half, while also shrinking the world
|
||||
database quite a bit due to the sharing.
|
||||
|
||||
\
|
||||
**Figure 66.3** *Activating a polygon when a leading edge is
|
||||
encountered in the AEL.*
|
||||

|
||||
|
||||
One final advantage of edge-sorting is that it makes no distinction
|
||||
between convex and concave polygons. That's not an important
|
||||
|
|
@ -65,9 +64,8 @@ down, and concave polygons help a lot in that regard. While it's
|
|||
possible to handle concave polygons with span-sorting, that can involve
|
||||
significant performance penalties.
|
||||
|
||||
\
|
||||
**Figure 66.4** *Deactivating a polygon when a trailing edge is
|
||||
encountered in the AEL.*
|
||||

|
||||
|
||||
Nonetheless, there's no cut-and-dried answer as to which approach is
|
||||
better. In the end, span-sorting and edge-sorting amount to the same
|
||||
|
|
|
|||
Loading…
Reference in a new issue