Index: hid_render_comp.html =================================================================== --- hid_render_comp.html (revision 10747) +++ hid_render_comp.html (revision 10748) @@ -2,7 +2,7 @@

HID: rendering vs. composite layers

-All rendering is driven by the core. The core undrestands the PCB stackup, +All rendering is driven by the core. The core understands the PCB stackup, layers, layer groups, compositions within the layer groups, extra labels, layer visibility, etc. The HID is a slave device that takes drawing instructions and blindly executes them. @@ -20,7 +20,7 @@ pixels are erased from the sketch canvas, making the affected pixels transparent again. Drawing on a layer group (either positively or negatively) should overwrite pixels on the same layer group. In other words, there's -no transluency between two overlapping objects drawm on the same layer +no translucency between two overlapping objects drawn on the same layer group.

@@ -31,7 +31,7 @@ The following steps are taken by the core in a burst:

1. call to the render_burst hook with start -
2. set_layer_group is called for the next layer; depending on the return value, the core will skip to stpe 7. +
2. set_layer_group is called for the next layer; depending on the return value, the core will skip to step 7.
3. set_drawing_mode is called with reset
3. set_drawing_mode is called with positive or negative to set draw or erase
4. objects are drawn @@ -74,10 +74,10 @@
Note: this concept is orthogonal to the above canvas based drawing. Regardless of which GC is used, the object being drawn always ends up -making modificatios to the currently active (sketch) canvas. +making modifications to the currently active (sketch) canvas.
A GC can be initialized only after render_burst / start -and all GCs will be uninitialzed before render_burst / end. +and all GCs will be uninitialized before render_burst / end.