diff options
Diffstat (limited to 'source/blender/gpencil_modifiers/intern/lineart/lineart_cpu.c')
-rw-r--r-- | source/blender/gpencil_modifiers/intern/lineart/lineart_cpu.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/source/blender/gpencil_modifiers/intern/lineart/lineart_cpu.c b/source/blender/gpencil_modifiers/intern/lineart/lineart_cpu.c index 3773af70498..1b31d672e3b 100644 --- a/source/blender/gpencil_modifiers/intern/lineart/lineart_cpu.c +++ b/source/blender/gpencil_modifiers/intern/lineart/lineart_cpu.c @@ -2332,9 +2332,9 @@ static bool lineart_edge_from_triangle(const LineartTriangle *tri, * if returns true, then from/to will carry the occluded segments * in ratio from `e->v1` to `e->v2`. The line is later cut with these two values. * - * TODO: (Yiming) This function uses a convoluted method that needs to be redesigned. + * TODO(@Yiming): This function uses a convoluted method that needs to be redesigned. * - * 1) The lineart_intersect_seg_seg() and lineart_point_triangle_relation() are separate calls, + * 1) The #lineart_intersect_seg_seg() and #lineart_point_triangle_relation() are separate calls, * which would potentially return results that doesn't agree, especially when it's an edge * extruding from one of the triangle's point. To get the information using one math process can * solve this problem. @@ -2346,7 +2346,7 @@ static bool lineart_edge_from_triangle(const LineartTriangle *tri, * I keep this function as-is because it's still fast, and more importantly the output value * threshold is already in tune with the cutting function in the next stage. * While current "edge aligned" fix isn't ideal, it does solve most of the precision issue - * especially in ortho camera mode. + * especially in orthographic camera mode. */ static bool lineart_triangle_edge_image_space_occlusion(SpinLock *UNUSED(spl), const LineartTriangle *tri, |